Give a member a different role on one project, optionally narrowed to specific languages.
Who this is for
Owners and admins.
Steps
Open the project, then Settings → Project access.
Under Project access, choose the person from Choose a member.
Choose the role they should hold on this project.
Optionally list the locales they may write in: the box reads locales (blank = all).
Add the grant.
What happens next
The grant overrides their workspace role for that project only. Somebody who is a translator across the workspace can be a developer on one project, or the other way round.
Locale narrowing is enforced where it matters: a scoped translator can open the project but can only write in the locales they hold.
Admins and the Owners of the account that holds the workspace always have full access and cannot be scoped. A grant for one of them is refused: "Account owners and admins already have full access to every project."
Assign to translator → does the same grant and creates a tracked piece of work, which is usually what you want for a real job rather than a bare grant.
Related
Onboard a vendor or freelancer
Assign a language to a translator
Roles and what each one can do