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

# Brand settings

> A brand's identity, response language, connected accounts, and who can work on it.

Under **Settings → Personal brand**. Everything here belongs to one brand — switch brand
first if you're managing several.

## General

<Frame>
  <img src="https://statics.depost.ai/docs/settings/brand-general.png?v=2" alt="Brand settings showing avatar, name fields, AI response language and delete brand" />
</Frame>

| Setting | Notes |
| - | - |
| **Avatar** | Appears in post previews |
| **First name** / **Last name** | The person this brand publishes as |
| **AI response language** | The language Depost AI writes in for this brand |

**AI response language** is per brand, which is what lets one workspace run an English brand
and a German one without either drifting.

**Delete brand** removes the brand and its content. Like deleting a workspace, there's no
undo.

## Social accounts

<Frame>
  <img src="https://statics.depost.ai/docs/settings/brand-accounts.png?v=2" alt="The social accounts screen showing connected LinkedIn accounts" />
</Frame>

The LinkedIn account this brand publishes through, and the extension's connection status.

Check here first when a post lands in **Failed** or analytics look stale — an expired
connection is the usual cause of both. See
[troubleshooting](/help/troubleshooting).

## Access

**Access** controls who can work on this brand. It's separate from a person's workspace role:
an Editor is only an Editor on the brands they've been granted.

<Frame>
  <img src="https://statics.depost.ai/docs/settings/brand-access.png?v=2" alt="The Brand access screen listing workspace members with access to this brand, each with their access level, when they joined and whether they are active" />
</Frame>

Each row shows the access level, when they joined, and whether they're still active. The
list is only workspace members — granting brand access doesn't invite anyone, so add them to
the workspace first. See [invite your team](/workspace/people).

That separation is what makes client work practical — see
[running client work](/workflows/agency).

## Related

<CardGroup cols={2}>
  <Card title="Workspaces and brands" icon="building" href="/workspace/overview">
    How brands sit inside a workspace.
  </Card>

  <Card title="Invite your team" icon="users" href="/workspace/people">
    Roles, and granting brand access.
  </Card>

  <Card title="Settings" icon="settings" href="/settings/overview">
    Which of account, workspace or brand holds what.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/help/troubleshooting">
    When a connection has lapsed.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.