Roles
Bu içerik henüz dilinizde mevcut değil.
Crowdin’de ÇevirinRoles in Crowdin 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 resources.
Below you can find descriptions of each role and its associated permissions.
Owner is the user who created the project and has complete control over it. The owner can invite users to the project and manage their access, work with source and translation files, configure project settings, and manage account-level resources such as AI providers, MT engines, and more.
Manager has similar rights to the project owner within assigned projects. They can manage project members, files, localization resources (i.e., TMs and Glossaries), tasks, integrations, reports, and other project-specific resources. Managers can’t delete projects or configure the project owner’s account-level resources such as AI providers or MT engines.
Use case: Suitable for trusted team members who manage the full localization process within specific projects.
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 join requests, 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.
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.
Member is a project participant who hasn’t been assigned a specific role yet; they can view the project but can’t translate until they join a language’s translation team (subject to manager approval).
Use case: Suitable for people you invite to a project (with the Empty roles option) before deciding which role to assign them.
Blocked users cannot access the project and are restricted from performing any actions.
Use case: Used when a user’s access to the project needs to be revoked.
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 | 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 AI, MT, or TM) | ✓ | ✓ | ✓ | ✓³ | ✗ | ✗ |
| 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; Owners and 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.
| Action | Owner | 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 | ✓ | ✓³ | ✗ | ✗ | ✗ | ✗ |
| Install and manage apps | ✓⁴ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Delete project / transfer ownership | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ |
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.
- Only for the specific resources the Manager has been assigned to manage on the Managers page.
- Project owner only.
Translation Memories, glossaries, style guides, Machine Translation engines, and AI are account-level resources managed from the project owner’s profile home page. TMs, glossaries, and style guides can be delegated to co-managers on the Managers page, while MT engines and AI can be managed only by the owner. Anyone can create their own glossary; glossary deletion is limited to the glossary’s owner.
| Action | Owner | Manager | Developer | Language Coordinator | Proofreader | Translator |
|---|---|---|---|---|---|---|
| Manage TMs, glossaries, and style guides¹ | ✓ | ✓² | ✗ | ✗ | ✗ | ✗ |
| Manage MT engines and AI | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Add managers and assign their project and resource access | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Assign a TM, glossary, MT engine, or style guide to the project | ✓ | ✓² | ✗ | ✗ | ✗ | ✗ |
| Use MT suggestions in the Editor | ✓ | ✓ | ✓ | ✓³ | ✓³ | ✓³ |
| Read glossary terms | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Add / edit glossary terms | ✓ | ✓ | ✓⁴ | ✓⁴ | ✓⁴ | ✓⁴ |
Notes
- Managers can edit the resources assigned to them but can’t create or delete resources.
- Only for the specific resources the Manager has been assigned to manage on the Managers page.
- Limited to the languages the role is assigned to.
- Depends on the project’s Glossary access setting (Full / Drafts / Read-only); Owners and Managers always can.
| Action | Owner | 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) | ✓ | ✓ | ✓ | ✗ | ✗ | ✗ |
| Add / edit glossary terms | ✓⁷ | ✓⁷ | ✓⁷ | ✓⁷ | ✓⁷ | ✓⁷ |
Notes
- Limited to the language(s) the role is assigned to.
- 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 and Language Coordinators can access hidden strings only when Allow proofreaders to access hidden strings is enabled; Owners, Managers, and Developers always can.
- Translators can resolve only issues they opened.
- Depends on the project’s Glossary access setting (Full / Drafts / Read-only); Owners and Managers always can.