Account

:::summarybox learn The three-layer hierarchy that Trakkr is built on What lives at the user, team, and brand level The two role systems and how they combine Three setups: solo, in-house team, agency Where to go for the deep dive on each layer

note

Most people don't come to this page out of curiosity. They land here because something didn't line up: a teammate couldn't see a brand they expected to see, the bill came under a name they didn't recognise, an invite landed in the wrong inbox. The model underneath all three of those is the same, and once it's loaded the answers are usually obvious.

Trakkr is structured around three things: you, your team, and the brands you track. Permissions flow down that hierarchy. So does billing. The rest of the Account docs read straight in plain English once this picture is in your head, so it's worth ten minutes here before clicking deeper.

The hierarchy

Here's the picture. Most of the confusion goes away once this shape is in your head.

You (a user account)
└─ Your team (one per user; you own the one you created)
   ├─ Plan and billing (one subscription per team)
   └─ Brands (one or many; each tracked independently)
      └─ Members (per-brand access for the people on your team)

A few rules that make this work:

Every user has exactly one team. You own the team you created, and ownership is permanent.
A team has one billing owner. Their plan covers everyone on the team.
A team can hold many brands. Each brand has its own prompts, citations, competitors, and visibility scores. Nothing leaks between them.
Access to a brand is granted per-member, with a role: owner, admin, editor, or viewer.

That last point is the one most people miss. Being on a team doesn't automatically give you full access to every brand. You can scope a member to a single brand, with the role you choose.

Why it works this way

Most SaaS gives you a flat account with one user, one workspace, one bill. That breaks the moment you do anything interesting.

An agency with twelve clients wants twelve brands under one bill, but each account manager should only see their own client.
A growth team wants the brand owner to control prompts, the content lead to edit, and the CEO to read dashboards without being able to break anything.
A startup with two products wants both brands on one plan, not two subscriptions to manage.

The user, team, and brand split is what makes all three possible without forcing anyone into separate accounts.

The two role systems

There are two layers of roles, and they do different jobs.

The team role decides what you can do at the team level: who you can invite, whether you can touch billing, whether you can create brands.

Team role	What it lets you do
Owner	Permanent. Full control. Pays the bill. There is exactly one per team.
Admin	Manage the team, create brands, run anything. Can manage billing if the owner grants it.
Viewer	Read-only across every brand. Cannot create, edit, or invite.

The brand role then says, for any specific brand, what each member can do once they're inside it.

Brand role	View	Edit content	Change settings	Delete brand
Owner	Yes	Yes	Yes	Yes
Admin	Yes	Yes	Yes	No
Editor	Yes	Yes	No	No
Viewer	Yes	No	No	No

By default, every team member gets read access to every brand in the team. Team admins automatically get edit-level access to every brand. If you need to scope someone tighter, the brand role does it. See Teams for how to set this up.

What lives where

It helps to be precise about what's attached to what.

Lives on	What	Why
The user	Profile, email, password, 2FA, personal notifications	These are personal preferences and follow you, not the team.
The team	Plan, payment method, invoices, add-ons, agency settings	One bill per team, even if it holds ten brands.
The brand	Prompts, citations, competitors, sentiment, history, reports	Each brand is tracked independently.
The brand member	Role and per-brand access for one user on one brand	This is the join that decides who sees what.

When you upgrade your plan, every brand and every team member gets the new features. When you invite a teammate, they inherit your plan automatically. When you delete a brand, you lose its history but everything else stays put.

Three common setups

Most accounts look like one of these.

Solo: one user, one brand

You signed up, you track your brand, you pay the bill. The team layer exists, you just never think about it. No invites, no role decisions.

In-house team: one company, one brand, several people

You invite your marketing lead as Admin, two contributors as Editor on the brand, and the CEO as Viewer. The owner stays with whoever holds the subscription. Nobody else needs to think about billing.

Agency: one shop, many client brands, scoped access

You add a brand per client. Each client's account manager gets Admin on their brand and nothing else. Your operations lead is team Admin, so they see everything. Clients themselves can be invited as Viewer on their own brand only, with no exposure to other clients' data.

Where to go next

Three pages cover the rest in depth. Read them in order if you're setting up for the first time.

Common questions

Can I be on more than one team?

No. Every user account belongs to exactly one team. If you need to keep two organizations apart, use two email addresses.

What happens if the team owner leaves the company?

The owner is permanent on a live team, so the only clean path is to delete the team and have a new person create a fresh one. Email support if you need help migrating brands across, since there's no self-serve transfer flow today.

How do I let a teammate manage billing without making them the owner?

Grant them the can_manage_billing flag from Settings → Team. They'll see the billing portal, change plans, and update payment without being able to remove the owner.

Where do I configure all of this?

Most of it lives in Settings. Brands sit on the Brands tab, team on Team, plan on Billing. The Account overview is the same idea in a different format.