> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/product-tour/smart-grids-in-utility-bar.md).

# Utility Bar

Add GridMate grids to a Lightning app utility bar or an Experience Cloud site.

GridMate can be used from a utility bar in two ways:

* **Utility Bar Grid**: add a GridMate grid as an item of the standard utility bar of a **Lightning app**.
* **Utility Bar Component**: add **GM - Utility Bar** to an **Experience Cloud site**, where the standard utility bar is not available.

## Utility Bar Grid

**GM - FieldSet Grid**, **GM - ListView Grid** and **GM - RelatedList Grid** can be embedded as a utility bar item. Below is a quick demo on how to configure an Open Task utility bar using **GM - FieldSet Grid**.

{% embed url="<https://youtu.be/yc2u0FQUcgE>" %}
Gridmate - Utility Bar Grid Setup
{% endembed %}

### Utility Item Properties

In our example, we configured the utility bar item properties (Label, Icon, Width and Height).

![](https://4046919449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEsSbGy_U_OhthKUpxu%2Fuploads%2FuqXY8UitZBt5QEoUSgI7%2FScreenshot%202021-12-12%20at%2018.57.08.png?alt=media\&token=62f1290c-bfdc-4d42-aacf-8c47638d4aff)

### Grid Configuration

We configured the **GM - FieldSet Grid** properties the same way as on the Lightning App Builder. We added a custom field **Marker** on the Task object to highlight the task based on the priority.

The column style is set to make the marker field short. The tasks are filtered to show only open ones and sorted by due date. We configured an autolaunched flow action to mark tasks as completed.

```json
[
   {
      "name": "markcomplete",
      "label": "Mark as Complete",
      "icon": "utility:check",
      "component": "gmpkg:DataGridCallFlowComponent",
      "attributes": {
         "flowName": "Complete_Task",
         "idListParam": "idList",
         "autolaunched": true
      }
   }
]
```

Finally, we set the coloring configuration based on the priority.

```json
{
   "Marker__c": [
      {
         "color": "#F08D8D",
         "exp": {
            "Priority": {
               "operator": "in",
               "value": [
                  "High"
               ]
            }
         }
      },
      {
         "color": "#FF9C25",
         "exp": {
            "Priority": {
               "operator": "in",
               "value": [
                  "Normal"
               ]
            }
         }
      },
      {
         "color": "#B0FD9F",
         "exp": {
            "Priority": {
               "operator": "in",
               "value": [
                  "Low"
               ]
            }
         }
      }
   ]
}
```

{% hint style="success" %}
We recommend using the **Config Wiz** to configure the utility bar grid.
{% endhint %}

### Utility Bar Grid Demo

Below is a quick demo of the final version of our utility bar where users can see their open tasks and mark them as completed in a few clicks!

{% embed url="<https://youtu.be/r_lwMRaK0Jc>" %}
GM - Utility Bar Grid Demo
{% endembed %}

## Utility Bar Component

**GM - Utility Bar** brings the utility bar to **Experience Cloud sites**. The standard Salesforce utility bar can't be exposed in Experience Cloud, and this component closes that gap. The bar is docked at the bottom of the page with one button per item; clicking a button opens the item in a flyout panel.

You control who sees the utility bar using visibility criteria in Experience Builder.

### Choose a Version

The component comes in two versions. Pick the one that matches your org.

<table><thead><tr><th width="220">Version</th><th>Use when</th></tr></thead><tbody><tr><td>GM - Utility Bar (LWC)</td><td>Lightning Web Security (LWS) is enabled and all utility items are LWC components.</td></tr><tr><td>GM - Utility Bar (Aura)</td><td>LWS is not enabled in the org, or one of the utility items is an Aura component.</td></tr></tbody></table>

### Add the Component to Your Site

{% stepper %}
{% step %}

#### Open Setup

Click the gear icon and select **Setup**.
{% endstep %}

{% step %}

#### Find your site

In the Quick Find box, search for **All Sites** and select it.
{% endstep %}

{% step %}

#### Open Experience Builder

Next to your site, click **Builder** to open Experience Builder.
{% endstep %}

{% step %}

#### Find the component

In the Components panel, search for **GM - Utility Bar (LWC)** or **GM - Utility Bar (Aura)**, depending on your org.
{% endstep %}

{% step %}

#### Add the component

Drag and drop the component onto the page.
{% endstep %}

{% step %}

#### Paste the configuration

In the **Utility Bar JSON Config** property, paste your configuration. See [Utility Bar JSON Config](#utility-bar-json-config) below.
{% endstep %}
{% endstepper %}

### Utility Bar JSON Config

The **Utility Bar JSON Config** is a JSON array of utility items. Each item supports the following keys:

<table><thead><tr><th width="220">Key</th><th>Description</th></tr></thead><tbody><tr><td>name</td><td>Unique name of the item.</td></tr><tr><td>label</td><td>Label of the item button.</td></tr><tr><td>iconName</td><td>Icon of the item button. All lightning icons are supported.</td></tr><tr><td>component</td><td>The component to display, as <code>namespace/componentName</code>.</td></tr><tr><td>attributes</td><td>JSON object of the component properties.</td></tr><tr><td>width</td><td>Panel width, in px or any CSS unit. The default value is 400px.</td></tr><tr><td>height</td><td>Panel height, in px or any CSS unit. The default value is 450px.</td></tr><tr><td>startAutomatically</td><td>Set to true to create the component at page load instead of the first time the item is opened.</td></tr></tbody></table>

{% hint style="info" %}
An item without **label** and **iconName** is headless: no button is displayed. Combined with **startAutomatically**, it is useful to run a background component like the Interaction Monitor.
{% endhint %}

{% hint style="info" %}
With **GM - Utility Bar (LWC)**, the GridMate monitors are referenced as `c/bulkActionMonitorLWC`, `c/dataImportMonitorLWC` and `c/interactionMonitorLWC`. Any other component is loaded dynamically from the **component** value.
{% endhint %}

All the keys are described in [GM - Utility Bar](https://docs.gridmate.io/package-reference/components-library/utilities-and-monitoring/gm-utility-bar.md).

### Example

Below is the configuration used in this demo. It defines four utility items:

* `InteractionLogger` runs in the background: its label is an invisible character, it has no icon, and its panel is `0px` wide and high.
* `dataImportMonitor` and `bulkActionMonitor` open the GridMate monitors. Both start automatically, so they track the jobs started before their panel is opened.
* `diagnosticTesterSlot` opens a custom LWC component and passes it its properties through **attributes**.

{% code expandable="true" %}

```json
[
    {
        "name": "InteractionLogger",
        "label": "‎ ",
        "iconName": "",
        "component": "c/interactionMonitorLWC",
        "startAutomatically": true,
        "width": "0px",
        "height": "0px",
        "attributes": {}
    },
    {
        "name": "dataImportMonitor",
        "label": "GM - Import Monitor",
        "iconName": "utility:upload",
        "component": "c/dataImportMonitorLWC",
        "startAutomatically": true,
        "width": "400px",
        "height": "400px",
        "attributes": {}
    },
    {
        "name": "bulkActionMonitor",
        "label": "GM - Bulk Action Monitor",
        "iconName": "utility:multi_select_checkbox",
        "component": "c/bulkActionMonitorLWC",
        "startAutomatically": true,
        "width": "400px",
        "height": "400px",
        "attributes": {
            "cleanupDelay": 60
        }
    },
    {
        "name": "diagnosticTesterSlot",
        "label": "LWC Dynamic Test Slot",
        "iconName": "utility:bug",
        "component": "c/dummyUtilityTesterLWC",
        "startAutomatically": false,
        "width": "400px",
        "height": "400px",
        "attributes": {
            "title": "Custom Org Dashboard",
            "itemLimit": 12,
            "showAlertBanner": true,
            "bannerMessage": "Success! The parameters bypass mechanism is fully operational."
        }
    }
]
```

{% endcode %}

### Utility Bar Demo

Below is a step-by-step guide on how to configure and use **GM - Utility Bar** in Experience Cloud.

{% embed url="<https://youtu.be/yhSyz3dCBTI>" %}

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>GM - Utility Bar</strong></td><td>Every property of the component.</td><td><a href="https://docs.gridmate.io/package-reference/components-library/utilities-and-monitoring/gm-utility-bar.md">GM - Utility Bar</a></td></tr><tr><td><strong>Field Set Grid</strong></td><td>Build a grid from a field set, including parent fields.</td><td><a href="https://docs.gridmate.io/product-tour/grids/field-set-grid.md">Field Set Grid</a></td></tr><tr><td><strong>Record App Switcher</strong></td><td>Switch between Lightning apps from a utility bar item in two clicks.</td><td><a href="https://docs.gridmate.io/product-tour/records/app-switcher-in-action.md">Record App Switcher</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gridmate.io/product-tour/smart-grids-in-utility-bar.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
