# How do I invite a teammate and manage access?

> The team under Settings: members card, 30 seats with invitations counted in, invitations that live 7 days, five roles including Custom, and leaving the team.

## Where is the team?

On the **Settings** page — the members card is the first thing on it, at any screen width. The dashboard search opens it too: type *team*, *members* or *invite* and the result takes you straight to the card.

A team holds 30 seats: active members, the owner included, and pending invitations count together. An invitation that expired, was revoked or was declined frees its seat, and the invite window always shows how many seats are left.

## How do I invite someone?

**Invite Member**, in the header of the members card. One address per line, up to 30 at once — never more than the seats you have left. The role is never preselected: choose Admin, Finance, Developer or **Custom**. Inviting takes the Team management permission, so it belongs to the owner and admins; an admin's checkboxes offer only the permissions the admin already has.

**Custom** starts with no permissions at all. You tick the ones this person needs, at least one, or the invitation won't go out.

An invitation is valid for 7 days. A merchant can send up to 50 invitation emails per day, resends included; copying a link doesn't count. After sending, the window reports per address: sent; created but the email didn't go out — then use **Copy link** or **Resend** — or the reason the address was refused.

## What can each role do?

**Owner** — everything, plus the two things nobody else gets: managing withdrawal addresses, and changing another member's role or permissions. Asking for the withdrawal whitelist to be switched off, and turning it back on, are the owner's alone as well. There is one owner, and ownership cannot be transferred.

**Admin** — the team, payments and invoices, projects, API keys and webhooks including secret rotation, the business profile, partnership figures and support chat. Sees the balance and the payout history; cannot send a payout, edit the withdrawal whitelist, or change roles.

**Finance** — balance, payout history, withdrawal addresses as a read-only list, and the right to send a payout to an address the owner already approved — or, if the whitelist has been switched off, to an address typed in by hand.

**Developer** — API keys, webhooks and projects, and can read payments. Cannot create an invoice, see the balance or reach payouts.

**Custom** — exactly the permissions you ticked, nothing else. A member whose Custom role still has no permissions is marked "No permissions — assign some" on their row.

Only the owner changes roles and permissions.

## What does the invited person see?

The link from the email or Telegram opens a page naming who invited them, to which merchant and with which role, and how long the invitation is valid. Opening the page changes nothing.

To accept, they sign in with the invited email — any method works: a code, Google, Telegram or a passkey. After signing in, the invitation waits on the onboarding screen with **Accept** and **Decline**.

One person can belong to one merchant only. Someone already in a team cannot accept an invitation, and while an invitation is pending, creating your own merchant is blocked — accept or decline first. Accepting one invitation declines the rest.

## Resending, copying, revoking

A pending row shows the address, the role and the date the invitation runs out. **Resend** issues a new link valid for another 7 days and emails it again. **Copy link** gives you a fresh personal link, no email — only the invited address can accept by it. **Revoke** closes the invitation for good.

Seven days after sending, the row is marked **Expired** and can be resent. Removing a member and revoking an invitation ask for your second factor if you have one enabled; resending and copying a link don't — the recipient stays the same.

## How does someone leave the team?

Any member except the owner: **Leave team**, in the account settings, with a confirmation. Leaving ends the member's sessions and returns them to their own onboarding — the way back is a new invitation.

The owner gets a notification when an invitation is accepted or declined, and when a member leaves the team.

## Why don't I see a section other people talk about?

Almost always the permission behind it. A menu entry you have no permission for is not shown at all rather than shown and refused, so the screen is absent rather than complaining. Ask the owner to add the permission on your member row, and the entry appears on your next visit.

Two other reasons exist and are covered elsewhere: the setup pages under a project depend on how that project was created, and payment channels are switched on one merchant at a time.