> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adopt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Org settings

> Organization-wide configuration that applies across all clients and agents.

Org settings hold the configuration that applies across your whole Studio workspace — not to a single client or agent. In the Builder, this lives under **Settings**, with two areas: **Secrets** and **Branding**.

## Secrets

Secrets are the credentials and sensitive configuration your agents and connectors need — API keys and the like — organized into **secret groups** and shared with specific collaborators.

<Frame>
  <img src="https://mintcdn.com/adoptai-0ccbafe4/e2oYi85duHN1wflQ/images/acct-org-settings.png?fit=max&auto=format&n=e2oYi85duHN1wflQ&q=85&s=6cc1833ae96741e4e7e3a58d6de43c07" alt="Acct Org Settings" width="1504" height="817" data-path="images/acct-org-settings.png" />
</Frame>

Each group lists its secrets (e.g. an API key) and the collaborators granted access. Keep secrets in the narrowest group that the work needs, and review collaborators periodically alongside your [access review](/admin/managing-members).

## Branding

Branding sets your organization's identity across Studio — the logo, the public-facing name, and the org-wide accent colour.

<Frame>
  <img src="https://mintcdn.com/adoptai-0ccbafe4/baSPGzarREDH1-vx/images/acct-branding.png?fit=max&auto=format&n=baSPGzarREDH1-vx&q=85&s=b8f4a194ba00a4460df1c1954031582b" alt="Acct Branding" width="1495" height="812" data-path="images/acct-branding.png" />
</Frame>

* **Organization logo** — shown on the Studio sidebar and navigation.
* **Organization name** — the public-facing name for your workspace.
* **Brand identity** — sets the org-wide accent colour for every Studio user, with a live light/dark preview so you can see how it lands before saving.

## Other org-wide configuration

Depending on your plan, other organization-wide controls — default access and retention policies, the roles that exist, model configuration (including BYOK and self-hosted options), and notification integrations — may be managed here or in a dedicated admin area. Confirm what's available in your workspace and update this article to match.

<Tip>
  Set sensible org **defaults** so new clients and engagements inherit safe settings automatically, and keep notification integrations connected at the org level so end users can just pick a channel.
</Tip>

## Next steps

1. [Managing members](/admin/managing-members)
2. [Data handling and compliance](/security-access/data-handling-and-compliance)
3. [Notifications](/end-user-guide/notifications)