> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/access-control/setting-tenant-topbar-color.md). # Setting Tenant Topbar Color Customize the Tenant Topbar color in the DuploCloud Portal You can customize the Topbar color for individual Tenants in the DuploCloud Portal. This visual cue helps distinguish between environments and reduces the risk of accidental changes. It's especially helpful when managing multiple Tenants, such as development, staging, and production. ## Setting a Custom Topbar Color for a Tenant 1. Go to **Administrator** -> **Tenants**. 2. Click the name of the Tenant you want to modify in the **NAME** column. 3. Select the **Settings** tab. 4. Click **Add**. The **Add Tenant Feature** pane displays.

Add Tenant Feature pane

5. In the **Select Feature** list box, select **Tenant Header Color**. 6. In the **Select Header Color** list box, choose a color from the available options. 7. Click **Add** to apply the color. The Topbar in the DuploCloud Portal will display in the selected color when the Tenant is selected, making it easier to distinguish that Tenant from others.

The Demo Tenant detail page showing the teal-colored Topbar

--- # 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.duplocloud.com/docs/automation-platform/access-control/setting-tenant-topbar-color.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.