Documentation overview

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:

  1. Organization role – what kind of teammate someone is. Set on the Team page when you invite them, changeable any time.
  2. 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

RoleSeesCan do
OwnerEvery brandEverything – including billing, the plan, and buying credits
AdminEvery brandManage clients and the team, set per-brand credit budgets. No billing
ManagerEvery brandOperate every client and manage the team. No budgets, no billing
Creative DirectorAssigned brandsOversee creative output on their assignments
StrategistAssigned brandsPlan campaigns and strategy on their assignments
EditorAssigned brandsCreate and edit content on their assignments
MemberAssigned brandsWork their assigned clients
ViewerAssigned brandsRead-only
SupportThe HelpdeskA confined seat – lives in Helpdesk, nothing else
Data EngineerThe Data hubA confined seat – lives in Data, nothing else

What "sees" means. Everything made for a brand – campaigns, e-mails, social posts, the calendar, surveys, audiences, competitor analyses, AI CRO reports, library items – is visible to everyone who can open that brand. A link a colleague shares opens for you if the brand is yours to open. Only the person who made something can change or delete it, and when they delete it, it is gone for everyone.

"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. How many the pool holds depends on that plan; your plan page carries the number. 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 counted against the owner's plan the same way brands are, and the plan page carries that number too.

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.

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.

Sharing a sending identity between brands

A verified sending domain, email provider, SMS sender or WhatsApp number belongs to one brand. When another brand of yours needs the same one, you don't set it up twice:

  • Before the second brand has one, its setup dialog (Connections → the email, SMS or WhatsApp card) opens with Use an existing setup: the verified identities on your other brands, one click to link. For email you pick this brand's own from name and address on the shared domain. Nothing to verify, nothing to add to DNS.
  • From the brand that already has one, the same card shows Also use this … for… with the brands that don't have one yet, and a line saying which brands already use it.

Two things to know. Only people who can open both brands can link them, and a brand that already has a verified identity is never overwritten. And a shared identity shares its sending reputation: a bad send from one brand affects deliverability for every brand on that domain or number. Marketing and service (transactional) identities stay separate.

Connections to other platforms – HubSpot, Shopify, ad accounts – are still connected per brand.

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.