How do I invite team members?

Invitations are per organization, not per project — a member you invite can see the projects their role allows, across the whole org.

Sending an invitation #

Open Members
Invite member
Enter the email address
Pick a role — the dialog describes each one as you select it
Send

They get an email with a link. If they have no Better i18n account yet, the link takes them through creating one and then straight into your organization.

Which roles you can offer depends on your own. An Owner can invite an Admin; an Admin cannot — they see Developer, Reviewer, and Translator. See What are the roles and permissions? for what each one can do.

Two tabs, two states #

The Members page separates them, with a count on each:

Members — people who accepted
Pending Invites — sent, not yet accepted

Pending invites are only visible to people who can manage members.

Cancelling an invitation #

Find it under Pending Invites and cancel it. You are asked to confirm against the email address, so cancelling the wrong one takes a deliberate mistake.

Once cancelled, the link in the email stops working. Send a fresh invitation if you cancelled by accident.

Changing someone's role #

Click the role in the members list and choose another. It applies immediately — no re-invite, no sign-out.

Some rows are not editable, and it is not a bug:

Owners cannot be demoted from the members list
An Admin cannot change another Admin — that takes the Owner
You cannot change your own role

Removing a member #

Remove them from the members list and confirm. Access ends immediately: their session stops working on the next request, not at some later expiry.

Their translations stay. Removing a person does not remove their work, and it does not reassign what they were in the middle of — check for anything unapproved before you remove a reviewer.

Inviting an outside translator or agency #

Use Translator. They can read every key and its source text, translate, and use AI translation. They cannot approve, delete keys, create API keys, change project settings, or see billing — so their pass stays reviewable and nothing sensitive is exposed.

If they also sign off on their own work, they need Reviewer instead, which means giving up the second pair of eyes.