Skip to main content

Invite a teammate

Invite someone to your workspace by email, choosing the role they arrive with and, for a vendor, the single project they are allowed to see.

Invite someone to your workspace by email, choosing the role they arrive with and, for a vendor, the single project they are allowed to see.

Who this is for

Admins, and the Owners of the account that holds the workspace. Developers, reviewers and translators can be in the workspace but cannot invite.

Steps

  1. Open People for your workspace.

  2. Select Invite someone. The dialog has three steps and sends nothing until the last one.

  3. Enter the Email address. If that address already has an invitation waiting, the dialog says so here and offers two choices in place of the rest of the form: see "Sending one again" below.

  4. Choose the Role. Each choice says what the role is for. The list holds the roles you may hand out: Admin, Developer, Reviewer and Translator, and any custom roles, leaving out a role carrying more authority than your own. Nobody is invited as an Owner of the account: the account's Owners are added on the account's Owners & billing members page.

  5. Select Choose a scope. Leave What they can open on All projects for a normal teammate. To onboard a vendor or freelancer, pick a single project instead: they will see nothing else in the workspace.

  6. When you have scoped the invite to a single project, Locales they will own appears. Leave it empty for every locale in that project, or narrow it, for example de, pt-BR.

  7. Select Review the invite, read what it says they will see, then select Send the invite.

What happens next

The invitation appears under Waiting to accept with its role, its project scope if it has one, and the date it expires, seven days out. The person receives an email with a private link that carries them through signing in or signing up and brings them back to it. Accepting attaches them to the workspace with that role, and for a scoped invitation mints the project access it promised.

A waiting invitation holds a seat on the account's plan from the moment you send it until it is accepted or expires. Seats are counted across all the account's workspaces, one per person. The person you invite needs only a login, needs no account of their own, and pays nothing.

Until they accept, its row offers two things. Resend sends the same link again: the link in the first email keeps working, and the invitation then expires seven days from the day you resend. Revoke ends it, after asking you to confirm, and the link in their email stops working.

Sending one again. Typing an address that already has an invitation waiting is the other way to reach this. The dialog stops on its first step and shows what is waiting: the role, what they can open, when it was sent and when it expires. Upper and lower case do not matter.

  • Resend the same invite sends the same link again, exactly as Resend on the row does.

  • Change this invite carries on through the dialog, filled in with what the invitation says now. Its last step lists what changes, and the button reads Change and send the invite. Changing it makes a new link, so the link in the first email stops working and only the new one opens.

Neither choice sends anything until you select it, and nothing about the waiting invitation changes unless you change it. When the invitation is at a role you cannot hand out, or at a role this workspace no longer has, Change this invite is the only choice offered, and Resend is not on its row either.

If it doesn't work

  • "An invitation to ... is already waiting to be accepted.", followed by the date it was sent: use Resend the same invite or Change this invite.

  • "That user is already a member.": change their role from the list of people instead.

  • "You cannot invite someone at a role with more authority than you hold.": ask an admin or an Owner of the account to send it.

  • "That project does not belong to this workspace.": the scoped project is not one of yours.

  • "Unknown locale: use BCP-47 tags like de or pt-BR.": one of the locale tags is not recognised.

  • "Nothing was sent to ...": email to that address is being held back, usually because an earlier message to it bounced. Nothing was saved either, so a waiting invitation is untouched and the link in its first email still works.

  • "... is already a member of this workspace, so there was nothing to send." after Resend: they joined another way while the invitation waited. Revoke it.

  • "The invitation to ... has expired and its link no longer works.": invite them again to send a new link.

  • If your plan has no seat left, the form reports the limit and no invitation is sent. Changing an invitation that is already waiting is not refused this way, because it already holds its seat.

Related

  • Accept an invitation

  • Onboard a vendor or freelancer

  • Roles and what each one can do

Did this answer your question?