Team Access Levels and Permissions

Reference6 min read

Every team member has one of three access levels: Admin, Project manager, or Member. The person who created the team is its Owner. Access controls what someone can see and change. It does not decide who translates, edits, or proofreads. That is decided by workflow assignments (see Who does the work).

Access Overview#

AccessDescription
OwnerThe person who created the team. Full control over everything, including billing and deleting the team. Cannot be removed.
AdminRuns the team: people, settings, every project. Equivalent to Owner for day-to-day operations.
Project managerSets up projects and workflows and hands out work. Sees every shared project. Cannot manage people or team settings.
MemberDoes the work they're assigned. Sees only the documents they are assigned to. Most people who translate, edit, or proofread are Members.

Upgrading from an earlier version? The former Translator access level has been folded into Member. Everyone who was a Translator keeps everything they could do before, and can now also switch between translate, edit, and review modes on documents shared with them.


Permissions Matrix#

Team Management

ActionOwnerAdminProject managerMember
Edit team settingsYesYes----
Enable or disable AI copyeditingYes------
Delete teamYes------
Invite membersYesYes----
Remove membersYesYes----
Change member accessYesYes----
View team membersYesYesYesYes

Projects

ActionOwnerAdminProject managerMember
Create projectsYesYesYes--
Share projects with teamYesYesYes--
Manage workflowsYesYesYes--
Assign documentsYesYesYes--
Manage documents (upload, move, split)YesYesYes--
View all project documentsYesYesYes--
View assigned documents only------Yes
Translate segmentsYesYesYesYes

Glossaries

ActionOwnerAdminProject managerMember
Create glossariesYesYesYes--
Share glossaries with teamYesYesYes--
Edit terms (if editor role on glossary)YesYesYesYes
View terms (if viewer role on glossary)YesYesYesYes
Confirm terms (if editor role on glossary)YesYesYesYes

Team owners can additionally allow specific access levels to confirm terms and approve suggestions on glossaries shared with the team, in the team's glossary settings.

Translation Memories

ActionOwnerAdminProject managerMember
Create TMsYesYesYes--
Share TMs with teamYesYesYes--
Import entries (if editor role on TM)YesYesYesYes
View entries (if viewer role on TM)YesYesYesYes

Translation Rules

ActionOwnerAdminProject managerMember
Create rulesYesYesYes--
Share rules with teamYesYesYes--
Edit rules (if editor role)YesYesYesYes
View rules (if viewer role)YesYesYesYes

Workflow Steps

ActionOwnerAdminProject managerMember
Complete assigned workflow stepsYesYesYesYes
Comment on segments (in commenting steps)YesYesYesYes
Reopen a finished workflow stepYesYesYes--

Resource-Level Roles#

In addition to team access, individual resources (glossaries, TMs, and translation rules) have their own sharing roles:

Resource RoleCan ViewCan Edit
ViewerYes--
EditorYesYes

When a resource is shared with a team, each team member gets the default role set on the share. Admins can override this on a per-member basis.

Project shares work the same way: a project shared with the team at Editor level lets Members translate their assigned documents; at Viewer level they can read them. Owners, Admins, and Project managers can always edit.

Tip: Use Project manager for coordinators who need to create projects and assign work but should not manage team membership or billing. This keeps your team administration clean.


Who does the work#

Access says what someone may see. Assignment says what they are doing. Every workflow step (Translation, Editing, Proofreading, Review, and so on) is done by whoever is assigned to it on that document.

  • Set the people who usually handle each step under Who usually does what in the team's workflow settings. New projects that use the workflow start with those people, and assignment lists suggest them first.
  • Anyone on the team can still be assigned to any step. Suggestions help you find the right person quickly; they never limit who you can choose.
  • A Member sees a document as soon as they are assigned to one of its steps, and only for as long as the assignment lasts.

See Set up workflows for assigning steps and defaults.

Need more help?

Chat with our AI assistant or create a support ticket.