Team
The agency side of team setup: who is a teammate, who is a client, and how to scope an account manager to their own clients.
A solo operator can keep an agency in their head. Add a second person and two questions arrive at once: which clients should they see, and are they even a teammate?
This page is the agency-shaped half of that. Roles, invites, seats, and billing access are the same across Trakkr and live in Teams. What follows is what changes when your brands belong to other companies.
Teammate or client
Get this right at invite time. It is the distinction the rest of agency mode is built on.
An employee at your agency is a teammate. The marketing director at a client is a portal user. Sending the wrong invite is awkward to undo, so choose deliberately.
The exception runs one way. If you invite an address that is already a portal client on one of your brands, accepting the team invite promotes them to a teammate cleanly, and the invite modal warns you before it happens. There is no equivalent demotion.
Portal mechanics, including what each client can reach, live in Client access.
Scoping an account manager
The default is that a teammate sees every brand on the team. That suits an in-house team. It rarely suits an agency, where a contractor or a pod lead should see two accounts and not the other thirty.
Open the member's row in Settings → Team, choose Brand access, and switch Full access to Restricted access. Then grant each brand individually: View for read, and for admins a separate Edit toggle on top of it. Edit cannot be granted without View.
Restrictions are enforced where the data is read, not just hidden in the menu, so a restricted member cannot reach a brand by guessing a URL. Team owners always keep full access to every brand.
What restricting also closes
This is the part agencies trip over. Restricted brand access is not only a filter on the brand list. Two agency surfaces treat it as a role signal:
- Pitches is closed. Opening
/agency/pitcheswith restricted access shows "Pitch access is restricted" regardless of role, because a pitch is a new prospect rather than an assigned client. - The Clients roster turns read-only. No selection, no bulk actions, no adding or removing clients, and the operator columns (Work, Client sees, Group, Added by) are hidden.
Report schedules follow role instead: any owner or admin can manage them, restricted or not, and a viewer can read History but not change delivery.
So a restricted admin is the right shape for an account manager who runs their own clients day to day. A pod lead who also pitches new business needs unrestricted access.
Choosing a role for agency work
Admin is the working default for operators. Pair it with restricted brand access when they should only touch their own accounts.
Viewer suits a stakeholder who reads but does not act: a services director, a partner agency lead, an investor.
Owner is one person, and it is the billing subject for the whole team. A paying teammate does not change that.
The full matrix of what each role can do is in Teams.
Common questions
Can one person be on two agency teams?
No. A user belongs to one team at a time, so moving someone means leaving one team and accepting an invite to the other. Client portal access is separate and does not follow them.
Do client portal users count against my seats?
No. Portal access is governed by the white-label entitlement, not the team seat limit. You can have many more clients than teammates.
What happens to brand restrictions if I promote someone to admin?
They stay. Role and brand access are separate controls, so a restricted admin still only reaches the brands you granted, and still cannot open Pitches.
A teammate can see a client they should not. What did I miss?
Check whether Restricted access is actually on for that member rather than assumed, then review each granted brand. Also check whether they have portal access to a group, which can widen what they reach from the client side.
Why can an account manager see the Clients page but change nothing on it?
That is restricted brand access working as designed. The roster stays readable so they can see their own clients in context, but every operator control is withheld. Remove the restriction if they need to run the portfolio.