> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/enterprise-it-setup/browser-extension-installation-and-configuration/browser-extension-configuration-policy/extension-logo-configuration.md).

# Extension Logo Configuration

This page describes how to force a Team Logo to be shown / hidden in the PixieBrix Sidebar for a subset of users via a Chrome Policy.

### Hiding/Showing Logo in Sidebar

This policy overrides the *Show Sidebar logo* toggle in Team Theme (set in the Admin Console, under Settings > Theme):

1. Users for whom this policy is set to `true` will see the associated logo in the Sidebar.
2. Users for whom this policy is set to `false` will not see a logo in the Sidebar, it will be blank.

### Configuring the Extension Policy

In Chrome's `chrome://policy/` screen, under PixieBrix, set:

| Name            | Type       | Data   |
| --------------- | ---------- | ------ |
| showSidebarLogo | REG\_DWORD | 1 or 0 |

*If the policy is not created, then the logo behavior defaults to the Team Theme.*

The table below captures the resulting logo behavior per possible combinations of the `showSidebarLogo` policy and Team Themes (specified in the Admin Console, under Settings > Theme):

| `showSidebarLogo` policy         | Team Theme "Show Sidebar Logo" value | Logo State in Sidebar |
| -------------------------------- | ------------------------------------ | --------------------- |
| 1                                | 1 (purple)                           | Shown                 |
| 1                                | 0 (grey)                             | Shown                 |
| 0                                | 1 (purple)                           | Hidden                |
| 0                                | 0 (grey)                             | Hidden                |
| undefined (policy isn't created) | 1 (purple)                           | Shown                 |
| undefined (policy isn't created) | 0 (grey)                             | Hidden                |


---

# 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.pixiebrix.com/enterprise-it-setup/browser-extension-installation-and-configuration/browser-extension-configuration-policy/extension-logo-configuration.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.