Skip to main content

Change a teammate's role

Give someone a different role across the whole workspace: Admin, Developer, Reviewer, Translator or one of your custom roles.

Give someone a different role across the whole workspace: Admin, Developer, Reviewer, Translator or one of your custom roles.

Who this is for

Admins, and the Owners of the account that holds the workspace.

Steps

  1. Open People for your workspace.

  2. Under Who reaches what, find their row.

  3. Pick the new role in the Role column.

  4. Read the confirmation, which asks "Change" followed by their name and the new role, describes the role, and adds "It applies straight away, and you can change it back."

  5. Select Change role.

What happens next

The change applies at once. A message confirms it with "Role updated.", naming the person and their new role. It is recorded in the workspace audit log with who made it, the person is emailed their previous and new role, and the workspace's other admins and the Owners of its account get a security email about it.

The person keeps their one seat on the account's plan whatever their role, so a role change never changes the bill.

A role is a set of permissions, not a step on a ladder. Moving someone from Developer to Reviewer takes away adding keys and running AI translation and gives them approving; moving them from Reviewer to Translator only takes approving and reviewing assignments away. Roles and what each one can do lists what each one holds.

The picker offers only the roles you may hand out, so a role that carries more than you hold is not in it. Nobody is made an Owner of the account here, and the account's Owners are not in this list at all. They are under Account Owners at the top of the page, and their access is changed on the account's Owners & billing members page.

If it doesn't work

  • If the role column shows a role but no picker, you cannot change that person's role here.

  • If the picker reads "A role this workspace no longer has", the role they held is gone from this workspace. Pick one that exists.

  • While the workspace is read-only, for example while it waits to be deleted, a change that only takes permissions away still goes through, and any other change is refused with the reason.

  • To change what someone can do on one project rather than the whole workspace, use a project grant instead.

Related

  • Roles and what each one can do

  • Grant access to one project

  • The member list

Did this answer your question?