> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/build/elements/actionbar.md).
# Actionbar
## What is an Actionbar?
Actionbar is a set of collapsible buttons that can be added to any experience.
{% hint style="info" %}
Actionbar element doesn't work when in [VR Mode](/guidelines-compatibility/limitations/vr-mode-support.md)
{% endhint %}
What is an Actionbar
### Step 1: Add an Actionbar
You can add an Actionbar by clicking on the '**+**' icon in the left bar and selecting ‘Actionbar’ under the 'User Interface' section.
Adding an Actionbar
### Step 2: Customize the Actionbar
You have the option to tailor the actionbar to your preferences. The right-hand panel offers various choices, such as the position of the actionbar (top, right, left, or bottom), labelling, changing the color, and adding buttons that can link to your desired destination URL. You can also name the buttons, add images, and more.
Right panel of Actionbar
You can add various call-to-action buttons/ info buttons and more to your experience.
{% hint style="info" %}
You can add multiple actionbars in your experience.
{% endhint %}
### Step 3: Linking Actionbar items
Actionbar items (the individual buttons) can be linked using rules. The rules applied in the above experience are shown below:
Rules 1 - Actionbar
Rules 2- Actionbar
## Example Experience
Example actionbar in an experience:
{% embed url="" %}
Actionbar - Example
{% endembed %}
---
# 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.gmetri.com/metaverse/build/elements/actionbar.md?ask=&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.
