> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/integrations/chrome-extension/settings.md).

# Extension settings

Open the side panel, then **More options → Settings**.

**Appearance** offers **System**, **Light**, and **Dark**. System follows your operating system. The inbox `di/` picker keeps its light purple appearance in either theme.

**Meeting timezone** chooses whether the meeting list uses your browser timezone or your Distro account timezone. This changes the displayed times and date grouping; it doesn't move meetings. Add a timezone in your Distro profile if account time isn't available.

**Meeting visibility** controls which meeting statuses appear in the side panel. If a meeting seems missing, check these choices as well as the selected timezone.

**Keyword detection** controls `di/` in supported apps. Use the main switch or choose apps individually.

**Calendar event buttons** adds **View in Distro** and no-show controls to matching Distro meetings in Google Calendar. This setting is separate from keyword detection in event descriptions.

The **Account** section identifies the connected user. **Log out** disconnects the extension and your Distro website session. Sign in again when you want to reconnect.


---

# 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://help.distro.so/integrations/chrome-extension/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.