> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/organization-administration/organization-branding.md).

# Organization branding

Organization branding sets the logo and link preview image used for your organization. Upload suitable images and check that they remain clear at the displayed size.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FTdHIRv8HL5SPMwlH4kTO%2FG098.mp4?alt=media&token=dbc94d45-f4d2-4f66-a09a-662ce0ca43be>" %}

## Before you start

Prepare the approved logo and link-preview image, and confirm the active organization. For the appearance of a specific assistant or interface, use [Interface branding and feedback](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-branding-and-feedback.md); organization branding and interface branding are separate settings.

You need permission to change organization branding.

## Update the organization logo

Open Settings → Branding and inspect the current Logo and Link Preview Image.

![Organization Logo and Link Preview Image settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/JpLPoTph7rmq5IMUDG0z/assets/g098-g098-01-settings.png)

Check which organization you are editing before replacing an asset.

Use the logo control to select the required image.

![Logo upload control and preview](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/S6ybMziMoNTZrczGBhT7/assets/g098-g098-02-logo.png)

Follow the displayed format and size requirements and inspect the completed preview.

Check the logo in the organization selector or list.

![Logo in the organization selector](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/2JoVUxvKqr3fFLi4rLEc/assets/g098-g098-03-organization.png)

Confirm that it appears beside the intended organization and remains legible at that size.

## Update the link preview image

Use Update Image for Link Preview Image and select the required asset.

![Link Preview Image upload](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/hQkRM1QsJLmjLIgA7mAx/assets/g098-g098-04-preview.png)

Review the resulting preview before keeping the change.

Review both branding assets after saving.

![Saved organization branding assets](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/qQoadvKP307HUy2PYNtz/assets/g098-g098-05-restore.png)

Replace any unintended image and confirm the final logo and link-preview appearance.

## Important behavior

These settings control organization branding. Review agent or interface appearance settings separately when you need to customize a specific user interface.


---

# 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.stackai.com/guides-and-quickstarts/organization-administration/organization-branding.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.
