Teams
Invite teammates, set roles, scope brand access, delegate billing, and manage seats.
A team shares one subscription, one brand portfolio, and one access model. Members inherit the owner's effective plan, and a role plus optional per-brand grants decide what each person can do with it.
Manage it at Settings: Team. Team access needs a paid plan; without one the tab offers an upgrade instead of a roster.
Invite a teammate
Select Invite on the People card. Paste one address or several, pick Admin or Viewer, and send. The email invites them to join your team by name.
Two optional controls sit in the same modal. Allow billing access appears for Admins only. Brand access appears once the team has more than one brand and lets you scope the invite to named brands rather than all of them.
Pending invites stay in the People list with a "Pending" marker so you can resend or revoke them. A pending invite holds a seat, so revoke the ones you no longer need.
A user belongs to one team at a time. The invite flow flags an address that already belongs to another team or needs attention before it can be linked.
Roles
There are three roles. The owner is fixed; the other two are what you choose when inviting, and can be changed later from the member's menu.
| Role | Who it fits | What it can do |
|---|---|---|
| Owner | The person responsible for the account | Everything, including billing, seats, brand access, and team 2FA |
| Admin | Day-to-day operator | Edit every brand they can reach, invite and remove members, change roles, manage groups |
| Viewer | A stakeholder who reads the data | Read-only. Cannot create a brand |
The owner cannot be removed, cannot have their role changed, and cannot be restricted to specific brands. Ownership cannot be reassigned from Settings, so contact support if the owner has to change.
Two things sit outside the role ladder. Billing is a separate grant, described below. Configuring another member's brand access is owner-only, even though Admins can otherwise manage people.
Scope access by brand
By default a member reaches every brand the team owns: Owner and Admin as editors, Viewer as a reader. To narrow that, open the member's menu and choose Brand access.
The modal has one switch. Full access is the default. Restricted access reveals the brand list, and you grant each brand explicitly.
| Control | Effect |
|---|---|
| View off | The member cannot see the brand at all |
| View on | The member can read the brand |
| Edit on | The member can change the brand. Offered for Admins only |
Restriction overrides the team role inside the granted brands, and it does not preserve Admin powers. A restricted Admin acts as an editor on the brands where Edit is on and a reader everywhere else. A restricted member also cannot create a new brand or manage brand groups, because both are team-wide actions.
Use this for account managers, contractors, regional teams, and business units. Do not use a brand group as a stand-in: groups are a portal boundary, not an internal one.
Billing access
The team owner manages billing. Nobody else does unless the owner turns on Billing access in that member's menu, and the grant is recorded per person rather than inherited from the Admin role.
A member without the grant still gets every feature the plan includes. They see a notice naming the owner, the inherited plan, and the brand limit, but no payment or subscription controls.
Canceling and pausing stay with the owner even after a grant. A billing admin can change the plan, the card, and the add-ons; the cancel row tells everyone else who to contact.
Seats
A seat is any member of the team, the owner included. Pending invites hold one.
| Plan | Seats included |
|---|---|
| Growth | 3, plus any extra seats bought |
| Scale | Unlimited |
Extra seats cost $20 per seat per month, prorated by Stripe when you add or remove one. The owner and any billing admin can change the count from the seat control on the People card, or add exactly the seats an invite needs from inside the invite modal.
Removing a seat is symmetric with adding one, and the backend refuses to cut below what the team is actually using, so nobody is ever removed by a billing change.
If a team grows past its cap (an expired Scale trial is the usual cause), nobody loses access. New invites pause until you buy the seats to cover everyone or move up a plan.
Two-factor for the team
The owner can require two-factor authentication for everyone from Settings → Security → Team security. It applies at sign-in, so members do not have to set anything up first: they get an emailed code when they sign in on a device they have not used in the last seven days.
Members who turned on two-factor for themselves keep it whether or not the team rule is on. While the team rule is on, they cannot turn their own off.
Teammates and clients
A teammate works in the Trakkr app and takes a seat. A white-label client signs in to a read-only portal, keeps a separate client identity, and takes no seat.
Invite staff and operators from Settings → Team. Invite customers from Settings → White-Label → Clients. A team seat hands a client far more product surface and permission than the portal is designed to give them. Agencies can read the same ground from the agency side in Team.
Leaving and removing
Removing a member ends their team access. Brands, prompts, reports, and history belong to the team and stay put.
Anyone who is not the owner can leave from Leave team at the bottom of the tab. The owner cannot leave, and needs support for a transition.
Before you remove someone, check what was personal to them: their MCP connect token stops working, and any report or alert routed to their address needs a new recipient.
Common questions
Can one user join several teams?
No. A user belongs to one team at a time, so use a second email address if you need a separate team context.
Why can an Admin not see every brand?
Their brand access is restricted. Open Brand access on their row to see which brands are granted and whether Edit is on.
Why can an Admin not manage billing?
Because the role does not include it. The owner has to turn on Billing access for that person, and canceling or pausing still stays with the owner.
Do clients count toward the seat limit?
No. Only internal team members and pending invites take a seat. Portal clients do not.
What happens if the owner downgrades?
Everyone inherits the new plan immediately. Data stays, but anything outside the new entitlement stops: brands beyond the limit pause, prompts above the limit pause, and Automations and scheduled work outside the plan stop running.