> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/getting-started/settings.md).

# Settings

To configure settings for your organisation, choose from one of the below options.

{% hint style="info" %}
Settings can be overridden at building or device level where applicable.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Regional settings</strong></mark></td><td>Configure localisation settings for your company or building.</td><td></td><td><a href="/uma-knowledgebase/getting-started/settings/regional-settings.md">Regional settings</a></td></tr><tr><td><mark style="color:blue;"><strong>Branding and appearance</strong></mark></td><td>Customise the appearance of UMA for your employees.</td><td></td><td><a href="/uma-knowledgebase/getting-started/settings/branding-and-appearance.md">Branding and appearance</a></td></tr><tr><td><mark style="color:blue;"><strong>User settings</strong></mark></td><td>Configure user sync here.</td><td></td><td><a href="/uma-knowledgebase/getting-started/settings/user-settings.md">User settings</a></td></tr><tr><td><mark style="color:blue;"><strong>Visitor settings</strong></mark></td><td>Configure visitor management policies.</td><td></td><td><a href="/uma-knowledgebase/getting-started/settings/visitor-settings.md">Visitor settings</a></td></tr><tr><td><mark style="color:blue;"><strong>Support details</strong></mark></td><td>Enter support information to display on devices in your office.</td><td></td><td><a href="/uma-knowledgebase/getting-started/settings/support-details.md">Support details</a></td></tr><tr><td><mark style="color:blue;"><strong>Auto book / release</strong></mark></td><td>Automatically schedule / cancel meetings using occupancy sensors</td><td></td><td><a href="/uma-knowledgebase/getting-started/settings/auto-book-release.md">Auto book / release</a></td></tr><tr><td><mark style="color:blue;"><strong>Meeting settings</strong></mark></td><td>Configure meeting types and buffer times</td><td></td><td><a href="/uma-knowledgebase/getting-started/settings/meeting-settings.md">Meeting settings</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://support.meetuma.ai/uma-knowledgebase/getting-started/settings.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.