> ## 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. # Agencies and teams > Running several brands from one account — what's separate, what's shared, and who can see which. Most LinkedIn tools treat a second client as a second account. Depost AI treats it as a second **brand** inside the same workspace: its own voice, its own strategy, its own LinkedIn account and its own numbers, run by a team whose access you control brand by brand. This section is for anyone doing that — an agency with clients, an in-house team with several spokespeople, or a consultant running a personal brand alongside a company one. Adding, switching, and what belongs to a brand rather than to you. Invites, roles, and per-brand access. Every brand on one screen — schedule, numbers, shared material. The operating rhythm: onboarding, the week, reporting. ## The three layers Your agency or your company. It holds the people, the billing, the labels, and shared reference material. One per client, or per spokesperson. A brand is an identity you publish as. Someone's role and the brands they can reach are **two separate things**. A freelancer can be an Editor on one client and have no idea the others exist. ## What's separate, and what isn't This is the table to read before you set anything up, because it answers most of the questions that follow. | Separate per brand | Shared across the workspace | | - | - | | [Strategy](/settings/strategy) — audience, topics, offer | People and their roles | | [Writing style](/settings/writing-style) | Billing and plan limits | | The connected LinkedIn account | Labels | | Posts, drafts, calendar and analytics | The invite link and verified domains | | The content library for that brand | Workspace-level library material | | [Looks](/visuals/style) and the brand kit | | | AI response language | | **Nothing bleeds between brands.** A client's posts, numbers and reference material are only ever read for that client's content. That isn't a setting you switch on — it's how brands are scoped. ## Why a client brand sounds like the client The thing agencies usually fight is output that sounds like the agency rather than the client. Depost AI avoids that by construction: **every brand runs its own setup**. When you add a brand, it walks the same flow your own account went through — read that person's LinkedIn profile and posts, measure them, draft a strategy, learn how they write. See [set up your account](/started/set-up). So a second brand doesn't start blank and it doesn't inherit the first one. It starts knowing its own audience and its own voice, from that person's own history. Spend the setup minutes per client rather than afterwards. Correcting a strategy once at the start is cheaper than correcting every draft it produces — and a client notices "sounds nothing like me" faster than anything else you could get wrong. ## One workspace or several Usually one, with several brands in it. Use a **second workspace** only when billing or team membership genuinely have to be separate — a client paying their own subscription, or two teams that must not see each other at all. Everything else is better handled with brand access, which already lets someone hold one brand and see none of the others. The cost of extra workspaces is that nothing is shared across them: not people, not billing, not the cross-brand calendar or analytics. ## Plan limits worth checking first Plans differ on **how many brands and how many team members** a workspace can hold, which makes those two the numbers to check before you promise a client a start date. Both are on **Billing → Usage & Limits**, which splits account ceilings from per-brand monthly allowances. See [billing](/settings/billing). ## Related Sign-off before anything reaches a client's audience. Name, timezone, invite link, verified domains. One brand's own identity and connected account. One key per brand, or one across every brand. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.