> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/workspace/company-theme.md).
# Customize your company theme
Add your company logo and branding to Siit communications from Settings, Account details, Company Information and Branding, an action reserved to the owner and Super Admins
Content is more engaging when it is personalized. In Siit you can personalize the look of the communication you send out to fit your company brand by adding your logo.
🛠**Note: Only Siit owner and Super Admins can upload a logo. For information on permissions, see** [**Siit permissions**](/guides/workspace/manage-permissions.md)
1. On the right side of your screen, select **Settings**
2. Choose the **Account details**
3. Personalize **Company Information + Branding**
---
# 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.siit.io/guides/workspace/company-theme.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.
