> ## 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.

# Running client work

> One brand per client, separate access, and reporting that doesn't mix them up.

Depost AI separates the workspace from the brands inside it, which is what makes client work
practical rather than a matter of being careful.

## The structure

<CardGroup cols={2}>
  <Card title="One workspace" icon="building">
    Your agency. Billing, people, and shared library material live here.
  </Card>

  <Card title="One brand per client" icon="users">
    Each with its own voice, its own LinkedIn account, its own content.
  </Card>
</CardGroup>

Use separate *workspaces* only when billing or team membership genuinely need to be
isolated — a client who pays their own subscription, for instance. Otherwise one workspace
with several brands is easier to run and to report on.

## Setting it up

<Steps>
  <Step title="Create a brand per client">
    Give each its own voice and connected account. Content, analytics and publishing all
    scope to the brand automatically.
  </Step>

  <Step title="Add people with the access they need">
    Role and brand access are separate axes. A freelancer can be an Editor on one client
    and have no visibility of the rest. See [invite your team](/workspace/people).
  </Step>

  <Step title="Set each brand's voice properly">
    This is where client work is won or lost. A brand voice that hasn't been set up produces
    content that could belong to anyone, which is exactly what a client will notice.
  </Step>

  <Step title="Use review before publishing">
    Assign a reviewer so nothing reaches a client's audience unapproved. See
    [review and approval](/posts/review).
  </Step>
</Steps>

## Working day to day

* **Switch brand** before creating anything — content is scoped to whichever brand you're in
* Use **campaigns** to keep each client's chats together. See
  [organize chats](/chat/organize)
* Use **labels** to mark work by stage or client-side owner
* Keep client-specific material in that brand's library, and only genuinely shared
  reference at workspace level

<Warning>
  Check which brand is selected before a batch of work — in the dashboard and in the
  extension. Content created against the wrong brand is tedious to move, and a bookmark
  saved to the wrong client is worse.
</Warning>

## Reporting

Analytics can be read per brand or across all of them, so a client report and an agency
overview come from the same place. **Export CSV** for anything that needs to leave Depost AI.
See [analytics](/analytics/overview).

## Related

<CardGroup cols={2}>
  <Card title="Workspaces and brands" icon="building" href="/workspace/overview">
    How the two layers relate.
  </Card>

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

  <Card title="Review and approval" icon="check" href="/posts/review">
    Sign-off before anything goes out.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/analytics/overview">
    Per-brand and cross-brand reporting.
  </Card>
</CardGroup>