Trakkr Docs

Teams

AI visibility doesn't stay in one person's head for long. The growth lead spots the gap, the writer fixes the page, the CEO reads the dashboard. Trakkr's team layer is built around that fact: invite everyone you need, give them the role that fits, and your plan covers them automatically.

The model has two sides. A team role controls what a person can do at the team level. A brand role, optional and per-brand, controls what they can do once they're inside a specific brand. Most teams only use the first. Agencies and any team with sensitive cross-client setups use both.

For the bigger picture of how teams sit between users and brands, read the Account overview.

Inviting people

Invites live on Settings โ†’ Team. Click Invite Member, enter the email, pick the team role, and send. The person receives an email with a one-click link that's valid for 14 days. If they already have a Trakkr account on that email, they're added straight to the team; if not, they sign up first and land on your team afterward.

Pending invites stay on the same page until the person joins or you revoke them. You can also resend the email if the original got buried.

Roles and what they do

There are three team roles. They cascade: anything a Viewer can do, an Admin can do, and so on.

PermissionOwnerAdminViewer
View every brand in the teamYesYesYes
Create new brandsYesYesNo
Edit prompts, citations, contentYesYesNo
Invite, remove, or re-role membersYesYesNo
Manage billingYesYes if grantedNo
Delete the teamYesNoNo

A few rules worth knowing:

When to use which

RoleBest for
OwnerExactly one person, usually whoever owns the relationship with Trakkr and the bill.
AdminDay-to-day operators. Marketing lead, head of content, agency client services lead.
ViewerStakeholders who watch but don't touch. Executives, board members, client side-of-house.

Start a new teammate as Viewer and bump them up once they've been around long enough to know what edits matter. It's a lot easier than rolling back changes from someone who didn't realize what a button did.

Per-brand access

Default behavior is generous: every team member can view every brand, and Admins can edit every brand. That works fine for small in-house teams and falls apart the moment you're tracking competitors' clients in the same account.

To scope a member to specific brands, edit them from Settings โ†’ Team and toggle Restrict brand access. You'll see every brand the team holds; check the ones this person should see, and pick View only or Can edit per brand.

Role givenViewEdit contentChange settingsDelete
OwnerYesYesYesYes
AdminYesYesYesNo
EditorYesYesNoNo
ViewerYesNoNoNo

Brand-level access overrides the team default. A team Admin with restricted access only sees and edits the brands you checked. A team Viewer with Can edit on one brand can edit that brand and only that brand. The two layers stack.

Restricted access is what agencies use to give a client visibility into their own brand and nothing else. Pair it with the white-label portal and the client sees a fully branded surface without ever knowing your other clients exist.

Billing delegation

By default, only the Owner can change the plan, update payment, or download invoices. If you'd rather have your COO or finance lead handle billing without giving them the full Owner keys, grant them the Can manage billing flag from their member row in Settings โ†’ Team.

Once flagged, they can run checkout, change tier, add or remove add-ons, manage payment methods, and access Stripe's portal. They still cannot remove the Owner or delete the team.

Removing and changing roles

To change someone's role, click the role dropdown on their row and pick the new one. Changes apply immediately, and they'll see the new permissions the next time they refresh.

To remove a member, click the remove icon on their row and confirm. They lose access right away. Anything they created, prompts, workflows, reports, stays in the account and continues to work; only their ability to log in and act is revoked.

Two-factor authentication

2FA is set up per user from the Security tab in Settings. The Owner can also require 2FA for everyone on the team. When required, every member has to enable an authenticator app before they can access account data.

Trakkr supports time-based one-time passwords (TOTP) from any standard authenticator: 1Password, Authy, Google Authenticator. There is no SSO option today; if you need SAML or OIDC for an enterprise rollout, contact us.

Plan inheritance

When you're on a team, you inherit the Owner's plan and feature set. If the Owner is on Scale, every member gets Scale features even though they don't have their own subscription. If the Owner downgrades, everyone loses the higher-tier features at the same time.

This is invisible most of the time, which is the point. The only place it shows up is debugging: if a teammate sees an upgrade prompt they shouldn't, the inheritance lookup is the first thing to check. Sign them out and back in to refresh.

Common questions

How many seats does my plan include?

Scale teams have unlimited seats. Free and Growth are single-user, no team layer. If you're on Free or Growth and need to bring someone in, you'll need to upgrade. See Plans and billing.

Can a team member be on multiple teams?

No, one team per user. If someone needs to be on two distinct teams (for example, working at an agency and consulting on the side), they need a second email and a second Trakkr account.

What does "restricted brand access" actually hide?

Everything outside the brands you checked: prompts, citations, competitors, dashboards, reports, search results. From the restricted member's perspective, the brands you didn't check don't exist.

Can a Viewer trigger a research run?

No. Research runs cost compute and count toward plan limits, so they're an Editor-level action. Viewers can read the results once a run completes.

Who can delete a brand?

Only the brand's direct Owner. Team Admins can edit and reassign but not delete. See Brands for the full rules.

Does removing someone break the workflows they built?

No. Workflows, reports, shared dashboards, and saved views stay attached to the team and continue to run. You just lose that person's edit access.