01 — The shape of it
What a team is
A team is a set of people who sign in to your account as themselves. They are not sharing your login. Each one has their own email and password, their own two-factor code, their own API keys and their own line in the activity log — so “who refunded that?” has an answer.
You, the account owner, are not a team member. You are the account. The owner is never a seat, cannot be disabled, and can always do everything. Everyone else is a member with a role.
02 — Who can do what
The two roles
There are exactly two roles you can give someone, plus you.
| Role | Can do | Cannot do |
|---|---|---|
| Owner (you) | Everything, always. Not a seat and not removable. | — |
| Admin | Everything a member can be given: build and edit offers, run refunds, switch coupons off and back on, change settings. | The handful of owner-only actions — anything that changes the account itself. |
| Support | The day-to-day: look things up, answer buyers, do the work that does not change what you sell. | Anything gated to Admin — which includes deactivating and reactivating coupons. |
The rule the server applies is simple: an action marked owner refuses every team member including Admins; an action marked admin refuses Support and passes Admin and you. When it refuses, it names what was needed — an Admin or the account owner — rather than failing vaguely.
03 — Doing it
Inviting someone
Go to Settings → Team and press ＋ Invite a member. You give an email address and pick the role. They get a link, set their own password, enrol two-factor, and they are in.
Until they accept, the invitation sits in its own table with its Expires date, and two controls: Re-send if it went to spam, and Revoke if you have changed your mind. An invitation that expires is simply dead — re-send rather than wondering.
04 — The part people miss
Members and API keys
A member can mint their own API keys, and this is the part worth understanding: a key minted by a member is bound to that member. It carries their role, so it can never do more than they can — a Support member's key cannot perform an Admin action even though it is a perfectly valid key.
And it dies with them. Disable the member and their keys stop working in the same moment, along with their sessions. You do not have to go hunting for keys someone made months ago.
The API keys table shows an Owner column when you have a team, so every key is attributable to a person rather than to the account in general.
05 — When someone leaves
Disabling and removing
Disable is the one you almost always want. It kills their sessions and their API keys immediately, and keeps their history intact — the refunds they issued and the offers they built still show who did them. A disabled member can be brought back.
Removing goes further and is the owner's call. Neither one rewrites the past: your activity log keeps naming the person who took each action, which is the entire reason for having members instead of a shared password.
06 — The rules
Seats
The owner is never a seat. Beyond that, three member seats come with Pro, and also with the Worldwide Tax & Affiliates pack, which bundles them. An account with neither has zero seats and will not show the Team panel at all.
07 — Diagnosis
If something looks wrong
There is no Team panel. The account has no seats — see above. Team appears under Settings only once you hold an entitlement that grants them.
A member says an action was refused. Read the message: it names whether the action needed an Admin or the account owner. Support is refused anything Admin-gated, which is working as intended rather than a bug.
An invitation never arrived. Use Re-send. If it has passed its Expires date, it is dead and re-sending is the fix.
A member cannot sign in yet. Setup is two steps — a password and TOTP. Someone who stopped after the first is not finished.
08 — Next
Where to go next
The merchant guide for the whole picture, Coupons → Ending a promo for the Admin-gated example in context, or Connect your AI for how keys work.