Roles
Roles in Crowdin Enterprise define the level of access and control users have within the platform. By assigning roles, you can manage user permissions across the Editor, project settings, and organization settings.
Below you can find descriptions of each role and its associated permissions.
Owner is the user who created the organization and has complete control over it. The owner can invite users to the organization and manage their access, configure organization settings, manage vendors, create projects and groups, work with source and translation files, set up integrations, and more.
Admin has similar rights to the organization owner, with full access to the organization, including inviting and managing users, configuring organization settings, and creating and managing projects and groups. Admin can’t delete the organization or transfer ownership.
Use case: Suitable for trusted team members who need full access to manage the organization, its projects, and settings, without the ability to delete the organization.
Manager has a more focused scope of control that depends on their assignment at various levels. Based on the Permission granularity settings, Managers can be assigned at the organization, group, subgroup, or project levels. They inherit access to all child entities within their assigned parent entity (i.e., organization, group, or subgroup). Managers can’t manage vendors, manage users at the organization level, or configure organization settings, but they can invite organization members. Whether a Manager can create new projects depends on their scope: Workspace and Group Managers can, while a Project Manager only manages the projects already assigned to them.
Workspace Manager can create and manage projects across the entire organization, including all its groups and subgroups (inviting people to projects and managing resources).
Use case: Suitable for users responsible for maintaining consistency across multiple projects in the organization.
If permission granularity is disabled, Workspace Manager can be assigned using the Workspace manager toggle in the User details. If enabled, the role is granted by assigning the user to manage the whole workspace from the Groups tab in the User details (select the top-level Workspace entry).
Group Manager can create and manage projects within an assigned group and its subgroups (inviting people to projects and managing resources).
Use case: Suitable for users responsible for managing a group of projects and ensuring consistency within that group.
Group managers can be assigned only when permission granularity is enabled. In that case, organization owners and admins can assign users to manage specific groups or subgroups from the Groups tab in the User details.
Project Manager manages the projects they’re assigned to, including members, tasks, resources, and project settings, but can’t create new projects or access anything outside those projects.
Use case: Suitable for users who need to focus only on managing specific projects without broader organizational responsibilities.
Developer / Translation Requestor can upload source files, edit translatable text, connect integrations, and access the API. They don’t have permissions to manage project members, tasks, or reports.
Use case: Suitable for users handling the technical aspects of localization, such as file management, integration setup, or automation.
Language Coordinator can manage certain project features only for their assigned languages. They can translate and approve strings, manage project members and teams, generate project reports, create tasks, and auto-translate content. Language Coordinators cannot access other project settings such as source files, integrations, or project configurations.
Use case: Suitable for users coordinating translations across specific project languages.
Contributor is a general term for both Translators and Proofreaders who primarily work in the Editor. They can view projects, tasks, and workflow steps they are assigned to, access the Editor on corresponding workflow steps, generate personal translation reports, and communicate with other project members.
Proofreader can translate and approve strings within assigned projects. They do not have access to project settings or management functions.
Use case: Suitable for users focused on finalizing translations and ensuring quality.
Translator can add translations and vote on suggestions made by others. They do not have the ability to approve translations or access project settings.
Use case: Suitable for users responsible for providing translations without additional management responsibilities.
Vendors are separate organizations that provide professional translation services. After you invite a vendor to your project, their organization receives a copy of the assigned workflow step in the Incoming Projects section of their workspace. This setup is commonly used when outsourcing translations to external teams while keeping the workflow and quality control within Crowdin Enterprise.
The tables below summarize what each role can do, grouped by area of the product:
- ✓ — the role can perform the action
- ✗ — the role can’t perform the action
- A superscript number (for example, ✓¹) marks a conditional permission explained in the Notes under each table.
| Action | Owner / Admin | Workspace Manager | Group Manager |
|---|---|---|---|
| Delete the organization or transfer ownership | ✓¹ | ✗ | ✗ |
| Manage organization settings (branding, security, SSO, plan & billing) | ✓ | ✗ | ✗ |
| Invite organization members | ✓ | ✓² | ✓² |
| Edit member data / grant or revoke Admin | ✓³ | ✗ | ✗ |
| Invite vendors and clients | ✓ | ✗ | ✗ |
| Create and manage groups / subgroups | ✓ | ✓⁴ | ✓⁵ |
| Delete or transfer a group | ✓ | ✓⁴ | ✓⁶ |
| Create projects in a group | ✓ | ✓⁴ | ✓⁵ |
| Manage group resources (TMs, glossaries, MT, style guides, workflow templates) | ✓ | ✓⁴ | ✓⁷ |
| View organization and group reports | ✓ | ✓⁴ | ✓⁸ |
Notes
- Owner-only.
- Also available to anyone who manages at least one group or project; the Admin-Managed Invitations setting can restrict inviting to admins.
- Except for the Organization Owner or themselves.
- Workspace Manager covers the whole organization (all groups and projects), regardless of Permission granularity mode.
- Group Manager requires Permission granularity mode and acts only within the assigned group and its subgroups.
- Only as a manager of the group’s parent group, not the group they manage directly.
- Group Managers can edit resources in their group and subgroups, and read resources that live in a group above them.
- Own scope only; also depends on the plan. See Organization Reports.
In Crowdin Enterprise, Organization Owners and Admins have full access to every project, and an in-scope Group Manager has the same project access as a Manager within their group.
| Action | Manager | Developer | Language Coordinator | Proofreader | Translator |
|---|---|---|---|---|---|
| View project dashboard and activity | ✓ | ✓ | ✓ | ✓ | ✓ |
| View reports¹ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Participate in discussions (view, create topics, reply) | ✓ | ✓ | ✓ | ✓ | ✓ |
| Moderate discussions (edit / delete others’ topics & replies) | ✓ | ✗ | ✗ | ✗ | ✗ |
| Auto-Translate content (via TM, MT, or AI) | ✓ | ✓ | ✓³ | ✗ | ✗ |
| View tasks / open an assigned task | ✓ | ✓ | ✓² | ✓² | ✓² |
| Manage tasks (create / edit / delete) | ✓ | ✗ | ✓³ | ✗ | ✗ |
| Change task status | ✓ | ✓⁴ | ✓⁴ | ✓⁴ | ✓⁴ |
| Download a full project build (all target languages) | ✓ | ✓ | ✗ | ✗ | ✗ |
| Download translations for a single target language | ✓ | ✓ | ✗ | ✓⁵ | ✓⁵ |
Notes
- Every role can view reports, but the available set depends on the role and the plan. See Project Reports and Contributor Reports.
- Limited to tasks they’re assigned to (Language Coordinators — tasks in their assigned languages).
- Only for their assigned languages.
- A user assigned to a task can advance its status but can’t close it; Managers are unrestricted.
- Available only when Allow offline translation is enabled and the role has access to that language; with task-based access on, downloads happen through assigned tasks.
The same hierarchy applies here as in the Project zone: Organization Owners/Admins and in-scope Group Managers can perform these actions.
| Action | Manager | Developer | Language Coordinator | Proofreader | Translator |
|---|---|---|---|---|---|
| Edit project settings (name, languages, privacy, QA checks, branch protection) | ✓ | ✗ | ✗ | ✗ | ✗ |
| View members and their permissions | ✓ | ✗ | ✓ | ✗ | ✗ |
| Invite members / assign roles | ✓¹ | ✗ | ✓² | ✗ | ✗ |
| Manage members (remove / block / change status) | ✓¹ | ✗ | ✗ | ✗ | ✗ |
| Manage source files, branches, integrations, and webhooks | ✓ | ✓ | ✗ | ✗ | ✗ |
| Assign a TM, glossary, or style guide to the project | ✓ | ✗ | ✗ | ✗ | ✗ |
| Delete or transfer the project | ✗³ | ✗ | ✗ | ✗ | ✗ |
Notes
- Managers can’t edit the project Owner or themselves.
- Language Coordinators can invite and assign only the Translator or Proofreader role, and only within their assigned languages.
- Deleting or transferring a project is available to the project Owner (its creator), Organization Owners/Admins, Group Owners, and in-scope Group Managers, but not a regular Manager.
Organization Owners/Admins and in-scope Group Managers act as Managers in the Editor.
| Action | Manager | Developer | Language Coordinator | Proofreader | Translator |
|---|---|---|---|---|---|
| Add / save translation | ✓ | ✓ | ✓¹ | ✓¹ | ✓¹ |
| Approve / unapprove translation | ✓ | ✓ | ✓¹ | ✓¹ | ✗² |
| Vote on suggestions (+/−) | ✗³ | ✗³ | ✗³ | ✗³ | ✓³ |
| Delete own translation | ✓ | ✓ | ✓¹ | ✓¹ | ✓⁴ |
| Delete others’ translations | ✓ | ✓ | ✓¹ | ✓¹ | ✗ |
| Access hidden strings | ✓ | ✓ | ✗ | ✓⁵ | ✗ |
| Add comments & issues | ✓ | ✓ | ✓¹ | ✓¹ | ✓¹ |
| Resolve issues | ✓ | ✓ | ✓¹ | ✓¹ | ✓⁶ |
| Edit source strings (context, key, max length) | ✓ | ✓ | ✗ | ✗ | ✗ |
| Enter Review mode (source text review)⁷ | ✓ | ✓ | ✗ | ✗ | ✗ |
| Add / edit glossary terms | ✓⁸ | ✓⁸ | ✓⁸ | ✓⁸ | ✓⁸ |
Notes
- Limited to the language(s) the role is assigned to (in multi-step workflows, also the workflow step).
- Approving is reserved for Proofreaders and above; Translators can’t approve.
- In the Editor, voting and approving are mutually exclusive: vote controls appear only for Translators, who can vote only in their assigned languages and not on their own suggestion.
- Translators can delete only their own translations, within their assigned languages, and only when task-based access is off.
- Proofreaders can access hidden strings only when Allow proofreaders to access hidden strings is enabled; Managers and Developers always can.
- Translators can resolve only issues they opened.
- Review mode is available only in projects that include a Source Text Review workflow step; it’s for reviewing and editing source strings, so it’s limited to Managers and Developers.
- Depends on the project’s Glossary access setting (Full / Drafts / Read-only); Managers always can.