Team Management

A solo operator running an agency on Trakkr fits in their own head. The second person you bring on doesn't. Within a week, the question becomes "what should this teammate be able to see, edit, and do?" — and the moment that question goes unanswered, somebody breaks something they shouldn't have had access to.

Team Management exists to draw those lines. It handles invitations, roles, brand-scoped access, and (the part that matters most in agency mode) the difference between an agency teammate and a client portal user. Mixing those two up costs you a billing conversation or a client-trust conversation, both bad.

This is the agency-flavored read. For the shared cross-Trakkr team model, Account → Teams has the full role permission matrix.

Two kinds of person

The load-bearing distinction in agency mode. Get this right and most of the rest of the page is mechanics.

A teammate is someone on your team who works on client accounts. A client portal user is a client you've given a window into one of their own brands.

Practically: an employee at your agency is a teammate. The marketing director at a client is a client portal user. Sending the wrong kind of invite is hard to reverse cleanly, so pick correctly the first time.

The client portal user mechanics live in White-Label → Permissions. The rest of this page is about teammates.

Roles

Three teammate roles, cascading: anything a Viewer can do, an Admin can do; anything an Admin can do, the Owner can do.

Owner is exactly one person, usually whoever owns the relationship with Trakkr and the bill. Owner is permanent in the UI; to reassign, contact support.

Admin is the right default for operators who work on accounts. They can invite teammates, create brands, and edit anything they have access to. Most agency teammates should be Admins.

Viewer is for stakeholders who watch but don't touch — your head of services who wants to read but not edit, a partner agency lead, a board member.

For the full role permission matrix (who can do what), Account → Teams has the table.

Inviting a teammate

Hit Invite team member on Settings → Team. Bulk-paste emails or add one at a time, pick a role, and (optionally) scope brand access at invite time. Each invite is good for 14 days. Pending invites stay on the page with Resend and Revoke controls.

Two mechanics worth knowing. The modal quietly checks whether each email already has a Trakkr account or sits on another team, so you get an inline warning before you send anything surprising. And if an invitee already has a Trakkr account but never accepted, the Force add action on the pending invite directly links them — useful when somebody signs up, forgets the invite, and is now confused about why they're not on your team.

If you invite an email that's already a client portal user on one of your brands, accepting the team invite promotes them from client to teammate (the transition is clean on the backend). The modal shows a hint when this is about to happen.

Per-brand access scoping

The default is "see everything." That's correct for an in-house team running its own product. For an agency, it's almost never what you want — a contractor brought on for two specific accounts shouldn't see the other thirteen, and the senior teammate handling enterprise clients probably shouldn't have read access to the SMB book.

From the team page, edit a member and toggle Restrict brand access. You'll see every brand on the team; for each one, mark View only, Can edit, or leave it off (no access). A restricted member also can't create new brands — the create flow is hidden.

Restrictions are enforced by row-level security, not just the UI. A restricted member can't reach a brand they don't have access to even by typing the URL.

Day-to-day operations

The team page handles the things that come up: change a member's role (owner only), remove a member, revoke a pending invite, leave the team (non-owners). Every change writes to an activity log so you have an audit trail when something's contested.

Billing access is a separate flag (off by default) that the owner can grant to any Admin. It controls whether they can see the billing page and update payment methods. Useful when finance owns the card.

Plan access

Common questions

Can a single account be on multiple teams?

No. A user is on one team at a time. To move someone, they leave the current team and accept an invite to the new one. The same person can be a client portal user across many brands on different teams — that's a separate identity.

Do client portal users count against my seat count?

No. Client portal users are governed by the white-label entitlement, not the team seat limit. You typically run far more clients than teammates.

What happens to a member's brand restrictions when I promote them to Admin?

The restrictions stay. Role and brand-access scoping are independent levers — an Admin with restricted access is still restricted to the brands you granted, just with Admin powers within them.

How do I make someone a billing manager without making them Owner?

Promote them to Admin first, then flip the "Manage billing" toggle on their member row. Admins don't get billing access by default — it's an explicit grant.

A teammate sees brands they shouldn't. What did I miss?

Three things to check, in order: (1) is "Restrict brand access" actually toggled on for them? Without that flag, they see everything. (2) Are the unexpected brands on a different team? They can't be — team membership is the outer boundary. (3) Were they also invited to a client portal group containing those brands? Group access is additive.