Team and roles

Your organization's team is everyone who can sign in to its dashboard. Each person holds one role in the organization, and the role decides what they see and what they can do. A person can belong to several organizations, with a different role in each, and moves between them with the organization switcher.

The rolesCopy Anchor Link

What each role can doCopy Anchor Link

A ✓ means the role can; a dash means it cannot. Under each line, in code, are the permissions behind it. The dashboard shows the same matrix under Settings → Team → Roles and permissions, read from the API.

• Every role works in test mode. Live mode opens to every role once your organization is active: see Go-live checklist.
• A button your role cannot use stays on the page, disabled, with the reason: "Your role, Analyst, cannot refund". The API refuses the action anyway, whatever the page shows.
• Support's ceiling applies to each refund. The refund form shows it before you type an amount; above it, the refund is refused. See Refunds.
• API keys are not people. A secret key acts for the whole organization, whatever the role of the person who created it: a key made by a Developer can refund through the API. Keep secret keys on your servers, and roll the ones a person could see when that person leaves. See Security.

Invite peopleCopy Anchor Link

1. Open Settings → Team, then Invite members.
2. Enter up to ten email addresses and choose one role for them. The page shows what that role can do.
3. Each person receives an email with a link. The link works once, for seven days, for that address only.

The person who opens the link creates their account there. If an account already uses that address, they sign in with it first: an invitation never works for another account. They land in your organization with the role you chose. Until then, the invitation is listed under Invitations as Pending, with Resend and Revoke. Resend mails a new link, which works for seven days from then; the link sent before stops working.

Owners and Administrators can invite, once their own email address is verified: invitations go out in their name.

An invitation is refused when:

• the address is already in the team, or already has a pending invitation: resend that one instead. One address refused refuses the whole list, and the message names it;
• the organization already holds 100 pending invitations: revoke some first;
• too many emails went out: an organization sends at most 100 invitation emails in 24 hours, one person 200 across their organizations, one address receives at most 5, and one invitation is sent again at most once a minute.

Nobody is invited as Owner: ownership is handed over (below).

Change a role or remove someoneCopy Anchor Link

Open the person's page from Settings → Team. Change role gives them another role; Remove member takes them out of the team, after a confirmation. The Team page also shows, for each person, the role, whether two-step verification is on, and when they were last active.

• Nobody can be given the Owner role this way: ownership is handed over (below).
• Nobody can change their own role.
• The Owner cannot be removed.

A removed person loses access to the organization at once: every request is checked against the team, not only the sign-in. The invitations they sent that are still pending are revoked with them, as they are when a new role no longer lets them manage the team.

Leave an organizationCopy Anchor Link

Any member except the Owner can leave by themselves, with Leave organization on the dashboard. You lose access at once, and someone has to invite you again to come back. The Owner hands over ownership first.

Hand over ownershipCopy Anchor Link

Only the Owner can do it: Settings → Team → Transfer ownership, choose a member of the team, and confirm. The new Owner must be an active member, someone who has accepted their invitation, and may not already own 20 organizations. They receive every right, and you become an Administrator. Your organization has one Owner at every moment.

Coming laterCopy Anchor Link

• Two-step verification asked again before a change to the team.
• Custom roles, beyond the seven above.

We will announce each in the changelog.