> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traceten.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Team and roles
> Invite people to your Traceten account, choose what they can do, and understand how seats work on each plan.
## What this lets you do
Give other people access to your Traceten data, and decide who can change billing and delete things.
## Before you start
* You need to be an **admin** on the account. Members cannot invite anyone.
* Your plan needs a free seat. Starter includes one seat, which is you. See [Seats](#seats).
## Inviting someone
Go to **Settings → Team**. Members and invitations are on the **Organization** tab.
Select **Invite**, enter their email address, and pick a role. We send them an invitation email.
They follow the link and sign in, or create a Traceten login if they don't have one. They appear
under **Members** as soon as they accept.
Until they accept, the invitation sits under **Invitations**, where you can revoke it or send it again.
## The two roles
There are exactly two roles. There is no read-only role.
| Role | Can |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Admin** | Everything a member can, plus billing and plan changes, adding and deleting sites, minting and revoking API keys and crawl tokens, disconnecting integrations, and closing the account. |
| **Member** | See all analytics for the account. Change site settings, including the site name, its attribution model and its cookie domain. Create and manage outbound webhooks. Read the list of API keys, but not create or revoke them. |
Two things worth being explicit about, because they surprise people:
**A member is not read-only.** Anyone you invite as a member can change a site's
attribution model, which changes how every future conversion is credited. Invite
someone as a member only if you are comfortable with that.
**An admin's access has to cover the whole account.** Admin-only actions check
that the person is an admin *and* that their access is not limited to particular
sites. This is why an admin can occasionally see a screen but get a permission
error on the action.
## When someone leaves
**Their API keys are revoked.** Removing someone from your organization revokes
every API key they created on this account as soon as we are notified. If their
user is deleted altogether, their keys are revoked on every account. Anything
using one of those keys stops working (event ingestion can take up to a minute
to notice), so have someone who is staying create keys for shared scripts and CI. See [API keys](/api/api-keys#when-the-person-who-created-a-key-leaves).
**Their chart notes stay.** Notes they wrote remain on the chart and show as
"Former team member". If their user is deleted, the author recorded on each note
is replaced with a placeholder.
## Limiting someone to specific sites
By default everyone you invite can reach every site on the account. If you run
several properties, you can restrict a person to just the ones they work on.
Go to **Settings → Team** and open the **Site access** tab.
Select **Change** next to their name, then either **All sites** or **Selected sites**.
Select **Save access**. They keep their role; only what they can see changes.
Three things behave deliberately, and each one looks like a bug until you know why:
**"All sites" is its own choice, not ticking every box.** If you use **Selected
sites** and tick every one, that is exactly what they get: those sites, and
nothing you add later. Choose **All sites** when you mean "everything, including
future sites."
**You cannot save an empty selection.** Unchecking the last site is refused
rather than treated as "give them everything." Those are opposite intentions,
and the safer reading of an emptied list is that you did not mean to widen
anyone's access. To grant everything, choose **All sites**.
**You cannot restrict yourself, and someone must keep full access.** Restricting
your own access would remove your admin rights, including the ability to undo
it, so ask another admin. For the same reason the account always has to keep at
least one admin who can reach every site: give someone else full access first,
then narrow your own.
Site access is per account. If you belong to more than one Traceten account,
your access in each is set separately and changing one never affects the other.
Restricting someone to a single site interacts with deleting that site. See
[Troubleshooting](#troubleshooting) below.
## Connecting a revenue source
Connecting or disconnecting Stripe, Shopify, Lemon Squeezy, Polar or Paddle
needs an admin whose access covers the whole workspace. An admin scoped to
specific sites cannot, and neither can a member: both get a 403 with that
reason. Reading the connection status is open to everyone.
Shopify used to be narrower still, because its install flow could only resolve
the account from the person who created it. That flow is gone, so Shopify now
works like the rest.
## Seats
A seat is one person on your account, including you.
| Plan | Seats |
| ------- | ----- |
| Starter | 1 |
| Growth | 5 |
| Pro | 20 |
Once every seat is taken, new invitations fail until a seat frees up. Remove
someone from **Settings → Team**, or move to a larger plan.
**Moving to a smaller plan never removes anyone.** If you drop from Pro to Growth
with twelve people on the account, all twelve keep working exactly as before.
What stops is new invitations: you cannot add anyone else until you are back
under the limit. Nobody is ever signed out or removed because of a plan change.
## Belonging to more than one account
You can be a member of several Traceten accounts, which is how agencies work
across clients. Switch between them under **Settings → Account → Current
workspace**. Each account has its own sites, data, plan and billing, and
nothing is shared between them.
You can only ever **own** one account, which is the one created when you signed
up. Being invited to someone else's account does not change that.
## Troubleshooting
**The invitation email never arrived.** Check spam, then revoke and re-send from
**Settings → Team**. Invitations go to the exact address you typed, so a typo
sends a real email to someone else.
**"You've reached the maximum number of members."** Every seat on your plan is
taken. Remove someone, or change plan under **Settings → Billing**.
**A member sees a page but gets an error when they act on it.** The action is
admin-only. Billing, site creation and deletion, API keys, crawl tokens and
disconnecting integrations all require an admin.
**Someone lost access after a site was deleted.** If a person's access was
limited to one site and that site is deleted, they are usually removed from the
account, because they no longer have anything to see. Admins are never removed
automatically. This runs on a best effort basis, so check **Settings → Team**
afterwards to confirm who is still there, and invite them again once you have
another site for them.
**"Change" is greyed out on my own row.** You cannot restrict your own site
access, because it would remove your admin rights and you would not be able to
undo it. Ask another admin.
**Saving site access says the account would be left without a full admin.** At
least one admin has to keep access to every site. Give another admin **All
sites** first, then narrow the one you were editing.
**A site is missing from the list I can tick.** Only live sites can be granted.
A site scheduled for deletion does not appear until you cancel the deletion.
## Next
* [Plans and billing](/dashboard/billing)
* [Managing sites](/dashboard/sites)
* [Deleting your account](/privacy/account-deletion)