Team members and roles

Invite the people you work with to a website. Each person signs in with their own account and gets a role on that website: owner, admin or viewer.

Roles

Viewers see visitor details because they are people you invited by name, signed in with their own account. To show numbers without any personal data, use a read-only share link instead.

Invite someone

1. Open Settings → Members

   On the website's dashboard, open the Settings tab. Admins and the owner see the invite form.

2. Enter their email and choose a role

   They get an email with a link. You can also copy the link and send it yourself. The link works once and expires after 7 days.

3. They accept

   The link opens a page where they sign in, or create a free account, with the invited email address, then click Accept invitation. Only that address can accept, so a forwarded link is useless to anyone else.

Pending invitations are listed under the members. Resend sends a new link and restarts the 7 days; the previous link stops working. Revoke cancels the invitation.

Change roles, remove and leave

Admins and the owner can switch anyone except the owner between admin and viewer, or remove them. Changes apply at once, including to that person's access tokens. Any member except the owner can leave a website from the same list.

To script this, use the members API, the CLI (metricraven members …) or the MCP tools.

Transfer ownership

The owner can make another member the owner from Settings → Members → Transfer ownership, by typing the website's name to confirm. The website's events then count toward the new owner's plan, and you stay on as an admin. If their plan has no room for another website or for its team, the transfer is refused until they upgrade.

Plan limits

Team members are counted per owner, across all the websites you own: someone on three of your websites is one team member, and you count as one. Pending invitations count until they expire or are revoked. Share links and embeds are unlimited and never count. If you downgrade, nobody is removed; you can't invite more people until you're under the limit.

Rotate your site key

The site secret key (ana_sec_…) lets your server send payments and events and read reports. Rotate it if it may have leaked, or when someone who had it leaves.

1. Open Settings → Secret key

   Admins and the owner see the current key's first characters, when it was created and when it was last used.

2. Click Rotate key and choose what happens to the old key

   Stop it now for a leaked key. Keep it working for 24 hours or 7 days to give your servers time to switch.

3. Copy the new key and deploy it

   It is shown once. Put it in your server's environment and redeploy. The previous key's Last used time tells you when nothing sends it anymore; then click Stop accepting previous keys now, or let the grace period end.

Named keys

Give each server or integration its own key with Add a named key in Settings → Secret keys (up to 10 besides the default key). Each one shows when it was last used, can be rolled with the same grace periods, and can be revoked on its own: requests with a revoked key fail with 401 at once. The default key can be rolled but not revoked. Keys can also be managed with the API and metricraven websites keys in the CLI.