> For the complete documentation index, see [llms.txt](https://docs.arcware.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcware.cloud/arcware-cloud-platform/getting-started-with-arcware-cloud/creating-and-managing-your-projects/project-dashboard/project-settings/frontend-buttons-positioning.md).

# Frontend Buttons Positioning

As part of our commitment to full interface flexibility, we have introduced Frontend Buttons Positioning. This feature allows you to customize the placement and layout of the default control buttons (such as the Info, Fullscreen, Audio, Mic toggles), ensuring they don't interfere with your application's unique UI design.

### Styling Customization&#x20;

You can find the settings under **Project Settings\ WebSDK** tab by scrolling to the Styling Customization section.

<figure><img src="https://451842398-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxeRHVvCMHTEw8OnxbYIg%2Fuploads%2FC7AhtzZBI79ZKzW3xZZl%2Fimage.png?alt=media&amp;token=f70b383f-4ec6-4ad6-a0b6-2c20d9ca73e7" alt=""><figcaption></figcaption></figure>

1. **Default vs. Custom Toggle.** By default, the interface uses our standard predefined values. To unlock manual control, switch the toggle from Default to Custom.

{% hint style="info" %}
\[!NOTE] Switching back to 'Default' at any time will instantly revert the buttons to their original factory positions.
{% endhint %}

2. **Buttons Position Select exactly where the control overlay should sit on the user's screen. Available options in the dropdown include:**
   1. Bottom-Right (Default)
   2. Bottom-Left
   3. Top-Left
   4. Top-Right

3. **Buttons Orientation Define the flow of the button group to match your menu style:**
   * Horizontal: Buttons are placed side-by-side.
   * Vertical: Buttons are stacked on top of one another. (Default)<br>

4. **Reverse Order Enable this toggle to flip the sequence of the buttons.** This is particularly useful for maintaining UI symmetry when moving the buttons from the left side of the screen to the right.

***

### Use Case Example&#x20;

If your Unreal Engine project features a custom navigation menu at the top of the screen, you can use these settings to move the Arcware system buttons to the Bottom-Right and set them to Vertical orientation. This prevents UI overlapping and provides a cleaner, more integrated look for your end-users.


---

# 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.arcware.cloud/arcware-cloud-platform/getting-started-with-arcware-cloud/creating-and-managing-your-projects/project-dashboard/project-settings/frontend-buttons-positioning.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.