Members and roles

During the beta an account holds 5 people, counting open invitations: you and four more. Revoking an invitation or removing a member frees a place. Paid plans will allow more.

One login can belong to several accounts. Switch between them from the account name at the top of the sidebar.

Roles

Every member has one of three roles in each account they belong to.

Action	Read	Write	Admin
View every report and project setting	✓	✓	✓
See a project's write key	✓	✓	✓
See members and open invitations	✓	✓	✓
Create a project; rotate a write key		✓	✓
Delete a project			✓
Invite people; change roles; remove members			✓
Add and verify domains			✓
Rename or delete the account			✓

Billing will be admin-only too when it arrives. The beta is free.

Seeing the write key is not a privilege worth guarding: it is public by design, and anyone with your extension installed can read it.

An account always has at least one admin. The last admin cannot leave, be removed, or be demoted until someone else is made an admin.

Inviting someone

Under Account → Members, an admin enters an email address and a role. Read is the default, because it is the safest thing to hand out by mistake.

Inviting waits until your own email address is confirmed. Until then the dashboard says so, with a button that sends a new confirmation link.

AnalyticsTrend emails the invitation to that address, naming the account, the role and you, and a reply to it comes to you. The screen says whether the email went out, and shows the link once either way, so you can send it yourself if the email lands in spam. The link:

• works once, for 7 days;
• works only for the address it was made for;
• stops working the moment you choose Revoke.

Renew link makes a new link with a new 7 days, emails it, and stops the old one working.

To keep invitations from becoming a way to fill a stranger's inbox, AnalyticsTrend emails one address at most three times a day from an account, an account at most 50 times a day in all, and all accounts together at most 200 times a day. Past any limit the link is still made and shown, just not emailed.

If the account is an organization, inviting an address outside its verified domains asks you to confirm first, and the member is labelled External.

Accepting an invitation

Opening the link shows the account, the role and who sent it.

• No login yet: choose a password and you are in. No invite code is needed. A confirmation email follows, and inviting others waits for it, because whoever invited you also saw the link.
• Already have a login: sign in, and the invitation adds the account to the ones you have.
• Signed in as someone else: the page says which address the invitation is for. Sign out and back in as that address.

Changing roles and removing members

An admin changes anyone's role from the role list beside their name, and removes them with Remove. A removed member keeps their login and their other accounts; they just stop seeing this one. To leave an account yourself, use Account → General.

Access tokens

A personal access token lets an AI assistant read this account's reports through MCP, and, if its owner chooses, create and change goals and funnels. Admins can always make one. Anyone else can once an Admin allows them: on Account → Members, the Access tokens column has Allow beside each member, and Turn off once allowed.

Turning it off deletes that member's tokens in this account at once, as removing them does. So does changing an Admin to Write or Read; allow them access tokens afterwards so they can make new ones. An Admin sees every member's tokens on Account → Access tokens, and can revoke any of them. A token never does more than its owner's role: a Read member's token only reads. See connect an AI assistant.