> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/portal-quick-setup/theming-your-portal.md).

# Theming your portal

The theme settings allow you to adjust the visual appearance of your portal. Here you can change the header color and add your company logo, so the interface matches the environment your team is familiar with.

Theming does not affect how equipme works — it simply defines how the portal looks. You can make these adjustments at any time, and you can always revert or update your changes later.

{% @arcade/embed flowId="QyBA2iPjzLcDoGVOeTTV" url="<https://app.arcade.software/share/QyBA2iPjzLcDoGVOeTTV>" %}

Go to **Settings → Theme**.\
Here you can adjust everything from the favicon in the browser tab to the colors of the buttons inside the portal.

![](https://media1-production-mightynetworks.imgix.net/asset/dc265d61-dc62-4c62-a832-7c7f949bfa23/1758161624757.png?ixlib=rails-4.3.1\&fm=jpg\&q=75\&auto=format\&w=1400\&h=1400\&fit=max\&impolicy=ResizeCrop\&constraint=downsize\&aspect=fit)


---

# 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://hub.equipme.io/classes/portal-quick-setup/theming-your-portal.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.