Workspace, brands, and roles
A workspace is one customer. Brands live inside it. Almost every row belongs to that workspace, and brand-owned rows also belong to one brand. A missing row and a row in another workspace look the same: not found.
The header brand menu is the brand you are working on. Home, the composer, the calendar, analytics, and accounts follow that choice. Accounts can also list brands grouped so an owner can move between them.
Brands
Section titled “Brands”Owners and admins open Brands to add a brand, rename it, or archive it. Everyone else sees the brands they are allowed to use. The header menu is still how you switch.
| Plan | Brands included |
|---|---|
| Tier 1 | 1 |
| Tier 2 | 5 |
| Tier 3 | 10 |
| Custom | More than 10, set for that account |
A new workspace starts on Tier 1. Connected accounts on each brand stay unlimited on every plan. A channel can still be connected to only one brand in the same workspace.
You cannot change the plan yourself. The person who runs the server sets the tier, or a custom cap, for the account. There is no payment screen for this.
When the account is already using every brand the plan includes, adding another says so and points you to upgrade or archive. On Tier 3 the message asks about a custom plan, which is not a self-serve upgrade.
Archiving a brand hides it from the header and frees a slot. The brand is not deleted. Posts, comments, and connected accounts stay stored. You can unarchive it when a slot is free. An archived brand is not the one you are working on until then.
If the plan is lowered while the account still has more brands than the new limit, those brands keep working. Nothing is deleted or disconnected. You cannot add another until you archive brands down to the limit, or the person who runs the server raises the cap. The Brands page explains that in a banner.
Accounts on a brand
Section titled “Accounts on a brand”A brand can hold more than one account on the same network. A channel can be connected to one brand inside the workspace. Connecting that same channel to a second brand in the workspace is refused. Disconnect it from the first brand first.
Practice accounts from a local install use a stand-in network called mock. They let you click through the screens. A real channel posts only after that network’s developer app is configured and you connect the channel.
The server checks the role on every action. The screen hides buttons you cannot use. Hiding a button is not the permission.
| Role | Can |
|---|---|
| Owner, admin | Everything below, plus connect accounts, invite people, create an AI client, and add, rename, or archive brands. |
| Approver | Draft, schedule, and approve. |
| Editor | Draft and schedule. |
| Scheduler | Set a time. Does not draft or approve. |
| Viewer | Look. |
An invitation can cover the whole workspace, one brand, or one account. See Approvals and team.
What each screen is for
Section titled “What each screen is for”| Screen | Use it to |
|---|---|
| Home | See what needs a person next, with a next step on each row. |
| Calendar | See scheduled, published, uncertain, and handed-off posts. |
| Campaigns | Group related posts. |
| Composer | Write the source and the per-account versions. |
| Analytics | Read metrics, link-in-bio clicks, and download a CSV. |
| Link in bio | Edit the public page for this brand, or look if you cannot draft. |
| Accounts | Connect, refresh, or disconnect a channel. There is no cap on how many accounts a brand can hold. |
| Brands | Add, rename, or archive a brand, up to the plan. Owners and admins. |
| Team | Invite people and set the approval rule. |
| Settings | Connect channels for the current brand, connect an assistant, open the blog destination, and, for an owner or admin, read the activity log. |
| Security | Authenticator, sessions, and sign-in history. |
Voice notes, default hashtags, and caption presets can be stored on a brand. An assistant with Setup can read and update them. A presets screen in the product is coming soon.