Collaborative multilingual websites need more than a translation process. They also need a clear access model. When site owners, agency teams, project managers, freelancers and language specialists work in the same WordPress installation, each person should know what they can start, edit, review and publish. Without that separation, translation coordination can become confused with broad site administration.
WPML provides a documented role model for translation workflows: Administrator, Translation Manager and Translator. It also provides controls for assigning language pairs and managing access to automatic translation. These controls can support a least-privilege workflow, but they are not a complete security model for the whole website. WordPress roles, other plugins, hosting access, exported content and account security remain relevant. Exact labels and behavior may also depend on the installed WPML version and the broader WordPress user configuration.
Why WPML Translation Roles Matter for Team Workflows
A multilingual project usually includes several different responsibilities. A site owner or trusted manager may need to oversee the complete configuration. An agency project manager may coordinate content and send translation jobs. A freelancer or language specialist may only need to translate assigned content in particular language pairs. Treating all of these people as administrators gives them a broader responsibility than their actual work requires.
WPML’s role model helps separate these activities. Sending content for translation is different from translating assigned content, and both are different from reviewing automatic translations. Defining these boundaries makes it easier to decide who should initiate work, who should perform language tasks and who should approve the result according to the site’s publishing policy.
The practical principle is simple: give each user the WPML responsibilities they need, rather than granting administrator access by default. This does not mean that WPML permissions isolate every part of a website or guarantee security. It means that translation work can be organized more deliberately within the limits of the installed configuration.
WPML Administrator vs Translation Manager vs Translator
WPML identifies three relevant roles for translation workflows. The Administrator has access to all listed WPML capabilities. This includes sending content for translation, translating content and reviewing automatic translations. Because this is the broadest of the documented WPML roles, it is generally more appropriate for a site owner or trusted site manager than for every person involved in language work.
A Translation Manager can send content for translation, translate content and review automatic translations. However, this role does not have all administrative privileges. It fits a person who coordinates multilingual work, such as an internal project manager or an agency team member, while keeping the broadest administration separate.
A Translator can translate assigned content and review automatic translations, but cannot send new content for translation under the documented WPML role model. This distinction is important. A translator may work on the content assigned to them without being responsible for deciding which new material enters the translation workflow.
| WPML role | Send content for translation | Translate content | Review automatic translations |
|---|---|---|---|
| Administrator | Yes | Yes | Yes |
| Translation Manager | Yes | Yes | Yes |
| Translator | No | Yes, for assigned content | Yes |
This table describes WPML’s documented translation capability model, not every underlying WordPress capability. A user’s broader access may also be affected by WordPress configuration or other tools. In practice, reserve Administrator access for trusted managers, use Translation Manager for coordination and use Translator for narrowly assigned language work.
How to Add Translators and Assign Language Pairs
WPML provides a specific setup path for adding translators and defining the language combinations they can work with. An administrator should begin at WPML → Translation Dashboard and open the Translators tab. From there, choose Add a Translator, define the translator’s language pairs and save the configuration.
Language-pair assignment should reflect the person’s actual responsibility. A translator should receive only the source-target combinations needed for their work, rather than a wider set of languages simply because it is convenient during setup. This supports a more focused workflow and makes later permission checks easier.
After saving the configuration, test the assignment with a limited, non-critical content set. Confirm that the translator can work with the intended language pairs and that the workflow behaves as expected in the current installation. Interface labels and permission behavior may change between WPML versions, so verify the visible options on the website rather than relying only on an older procedure.
For agencies and internal teams, document who owns each language pair and who is responsible for coordination or review. The goal is not to create unnecessary administration. It is to ensure that every user receives the language access and translation responsibility required for their role.
Who Can Send Content for Translation and Review Automatic Translations
Sending content for translation and reviewing a translation are separate actions. Under WPML’s documented capability model, Administrators and Translation Managers can send content for translation. Translators cannot send new content for translation, even though they can work on assigned content.
Administrators, Translation Managers and Translators can review automatic translations. Therefore, a Translator may be involved in checking an automatic result without having the authority to initiate new translation jobs. This separation can help a team keep content selection and workflow coordination with a manager while assigning language work and review to the appropriate specialist.
Review access should not be confused with a guarantee of translation quality. It is a workflow permission. Whether a human review is needed depends on the content risk, language-quality requirements and the site’s publishing policy. The same distinction applies to automatic translation: permission to use it is separate from the decision about whether a result may be published immediately.
Restricting Automatic Translation Access
According to the documented WPML workflow, translators can use automatic translation in the Advanced Translation Editor by default. Administrators can control this access for specific translators from WPML → Translation Dashboard → Tools → Who can use automatic translation.
From this area, access can be enabled or disabled for individual translators. This gives administrators a separate control for automatic-translation use instead of treating every translator as equally authorized to use that workflow. Before enabling access, decide whether the person should be able to use automatic translation and whether their work requires review before publication.
Keep automatic-translation access limited to users who understand the site’s content standards and publishing process. Test a permission change with a limited user and non-critical content before applying a broader policy. This control does not guarantee security or translation quality. WordPress roles, other plugins, hosting access and account security remain separate parts of the overall access model.
Choosing a Safer Review and Publishing Workflow
The Translation Dashboard is the central WPML interface for selecting content, choosing a translation method, sending work and monitoring translation status. When using automatic translation, WPML documents publication and review choices that allow a team to match the workflow to its content policy.
One option is to wait for review before publication. This keeps the translation from being published until an authorized person checks it. Another option is to publish the translation while marking it for later review. The second approach can support a workflow where publication happens earlier, but it makes the later review responsibility important.
Choose between these options based on content risk, language-quality requirements and the site’s publishing policy. Legal, medical, financial, regulated or brand-critical content deserves an appropriate human-review process rather than an assumption that automatic translation is sufficient. For other content, a team may choose a different balance between review and publication speed. The documented settings are workflow controls, not certification or a guarantee of quality for every language or content type.
Before applying a publication choice across the site, test it with non-critical content. Confirm who sees the work for review, how the status is monitored and who can edit or publish the result. Separating automated translation from human approval makes the process easier to explain and audit.
Team Permission Checklist and Troubleshooting
Use the following checklist when configuring a collaborative multilingual website:
- Verify each user’s WPML role and confirm that it matches their actual responsibility.
- Check the language pairs assigned to every Translator.
- Confirm who can send new content for translation.
- Confirm who can translate assigned content and who can review automatic translations.
- Check automatic-translation access separately from general translation permissions.
- Test the workflow with non-critical content before applying it site-wide.
- Review WordPress roles, other plugins and hosting access as separate permission layers.
- Check the current WPML interface because labels and behavior may change between versions.
If a user cannot start a translation job, first check whether they are a Translator rather than an Administrator or Translation Manager. If a translator cannot use automatic translation, review the specific setting under Translation Dashboard → Tools → Who can use automatic translation. If a language pair is unavailable, return to the Translators tab and verify the saved assignment. These checks help distinguish a role boundary from a broader configuration issue.
WPML translation roles and permissions work best when administration, coordination, translation and approval are treated as separate responsibilities. Administrators can oversee the complete workflow, Translation Managers can coordinate and send work, and Translators can focus on assigned language tasks and review. Assign language pairs carefully, control automatic-translation access separately and choose publication settings that match the content policy. Remember that broader WordPress and hosting permissions still matter. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.