Team and access

Grant access to one project

Give a member a different role on one project, and optionally limit them to specific languages there.

Who can do this: admins, the Owners of the account that holds the workspace, and members whose workspace role includes Grant per-project access. A project grant cannot give this permission.

A project grant overrides a member's workspace role on that project only. Someone who is a Translator across the workspace can be a Developer on one project, or the other way round. A grant can also narrow a member to the locales they may write and approve in.

Open Project access

Open Settings, choose the Workspace tab, pick the project, then open Project access.

Choose the member

Under Project access, pick the person in Member to grant.

Choose their role on this project

Pick the Role on this project.

Limit the locales (optional)

In the box that reads locales (blank = all), list the locales they may work in, for example de, pt-BR. Leave it empty for every locale in the project.

Grant access

Select Grant access. The message reads "Access granted. An email is on its way to" followed by their name, "with what they can work on."

What happens next

The grant is listed under Project access with the person, their Role here, and their locales (or all locales). Locale limits are enforced on writing and approving: a member limited to German can open the project but can only edit and approve German.

Admins and account Owners always have full access to every project and cannot be limited. A grant for one of them is refused: "Account owners and admins already have full access to every project."

Revoke a grant

Select Revoke on the grant's row, then Revoke access. This removes the project-level grant only. Their workspace role applies again, which may still give them access to the project, and the work they have already done is untouched.

Assigning work is different

The Assignments section on the same page assigns a language to a translator as a tracked piece of work. Assigning opens that language to them and takes nothing away. To confine a translator to some languages, set the locales on their grant before you assign. An existing grant for all locales has to be revoked and granted again to narrow it. See Assign a language to a translator.

If it doesn't work

  • "Unknown locale": use BCP-47 tags such as de or pt-BR.
  • "You can only grant a role carrying capabilities you hold yourself": pick a role with no more authority than your own.
  • The member is not in the list: the list holds members whose workspace role is Developer, Reviewer or Translator and who have no grant on this project yet. Admins and account Owners already have full access. To change an existing grant, revoke it and grant it again. Someone who is not in the workspace yet has to be invited first.

On this page