Teams, roles and access
One rule holds this page together: brands belong to the organization, people hold roles against them. When anyone on your team creates a business profile, it lands in the organization – visible to the people whose role covers it, billed to the owner's plan, and listed in the admin portal with who created it and when. Nobody's work lives in a personal silo.
The two layers of access
Access is decided in two layers, and it helps to keep them apart:
- Organization role – what kind of teammate someone is. Set on the Team page when you invite them, changeable any time.
- Client access – which brands a scoped teammate is assigned to. Set per member on the Team page ("Update role and client access").
Management roles see everything, so client access only matters for the work roles below.
Roles at a glance
| Role | Sees | Can do |
|---|---|---|
| Owner | Every brand | Everything – including billing, the plan, and buying credits |
| Admin | Every brand | Manage clients and the team, set per-brand credit budgets. No billing |
| Manager | Every brand | Operate every client and manage the team. No budgets, no billing |
| Creative Director | Assigned brands | Oversee creative output on their assignments |
| Strategist | Assigned brands | Plan campaigns and strategy on their assignments |
| Editor | Assigned brands | Create and edit content on their assignments |
| Member | Assigned brands | Work their assigned clients |
| Viewer | Assigned brands | Read-only |
| Support | The Helpdesk | A confined seat – lives in Helpdesk, nothing else |
| Data Engineer | The Data hub | A confined seat – lives in Data, nothing else |
"Assigned brands" means the brands ticked for that member under client access – plus any brand the member created themselves. A scoped teammate with one assignment sees exactly one brand in their switcher, on Home, and everywhere else. The platform enforces this at the database and the API alike; it is not cosmetic.
Who can do what
Create a business profile – any teammate except the confined seats. The new brand automatically belongs to the organization: the owner and managers see it immediately, it appears in the admin portal's Business Profiles list with "Added by" and the date, and it uses one of the plan's brand slots.
Brand slots – brands are counted against the owner's plan, no matter who creates them: Starter includes 3, Growth 10, Business 25, Enterprise as many as you need (entry-level plans include 1). When the pool is full, every add-brand button routes to an upgrade instead of a creation flow that would fail.
Invite and manage the team – Owner, Admin, and Manager. Invites are sent by email; the invitee joins by signing up with the invited address. Team seats are also counted against the owner's plan (same ladder: 3 / 10 / 25 / unlimited).
Set per-brand credit budgets – Owner and Admin only. Budgets draw on the owner's credit balance: the platform refuses any allocation the owner's balance cannot cover, and tells you the real numbers when it does. Managers and work roles can see budgets, not set them.
Billing, plan changes, buying credits – the Owner only. There is one wallet per organization – the owner's – and every teammate's work draws on it. Admins and Managers can read the billing summary in the admin portal without being able to change anything.
Journeys – Owner, Admin, and Manager can operate any journey; scoped teammates can operate journeys on their assigned brands. A journey always runs as the organization – sending domains, segments and audiences are the organization's, not the operator's.
Recommended setups
Solo founder. You are the Owner; hire no one until the work demands it. Everything above collapses into one person and stays out of your way.
In-house team. The budget holder is the Owner. Give your head of marketing Admin – they can run clients, the team, and budgets without touching the plan. Everyone producing work gets a work role (Editor, Strategist, Creative Director) with all brands assigned if your company runs one estate.
Agency. The principal is the Owner. Operations leads get Admin, account leads get Manager. Every account team member gets a work role scoped to exactly their clients – a designer on two accounts sees two brands and nothing else. When a client relationship ends, remove the assignment and their access ends with it; when a teammate leaves, remove the member and every brand they created stays with the organization.
One caution: Admin and Manager see every brand by design. If a teammate should ever see less than everything, give them a work role and assignments – don't hand out Admin because the invite form suggests it first.
Common questions
A teammate created a brand – whose is it? The organization's. It counts against the owner's brand slots, the owner and admins can budget it, and it shows in the admin portal with the creator's name and date.
Why does my teammate see brands they weren't assigned? Their role is Owner, Admin, or Manager – those see everything. Scoping applies to the work roles.
Can I limit what an Admin sees? No – Admin means the whole estate. Use Manager if the difference you need is budgets, or a work role with assignments if the difference is which brands.
We removed someone – what happens to their work? Their brands and content belong to the organization and remain exactly where they were. Only their access ends.