You will have a role for people who translate, with only what they need.
Before you start
You need permission to manage roles, and you can tick only permissions you hold yourself. Follow "How do I create a role with only the permissions I choose?" for the screen itself.
Steps
- Open User Management, the Roles tab, and press Add. Name it, for example "Translator".
- In the permission matrix tick the translate permission for each kind of content they should translate, plus the read permission that lets them open it:
| They translate | Tick | And |
|---|---|---|
| Pages, header, footer, menus, blog posts, site name | Translate CMS Content (cms.translate) |
the CMS read permission (to open Pages, Blog and Menus) |
| Products, categories, brands, attributes, shipping methods, store texts | Translate Catalogue (ecommerce.catalog.translate) |
store read permissions for products and categories and tags |
| Courses, lessons, bundles, plans, instructors | Translate Courses (lms.translate) |
the courses read permission |
| Forms | Translate Forms (forms.translate) |
the forms read permission |
| Booking calendars | Translate Booking Calendars (booking.translate) |
the events read permission |
| The AI glossary and review queue | View Translations and Edit Translations |
- Press Save, then give the role to the person.
What you will see
The person can open the pages above, find the Languages tab or the Translate button, save and (for pages) publish a language. They cannot change a page's layout, a product's price, a course's structure or delete anything. People who can already edit a kind of content can translate it without this role.
If something goes wrong
- A person who sees no Languages tab: the site has one language, or they hold neither the translate nor the edit permission for that kind.
- Using Translate with AI also needs a plan that includes AI translation.
- Approving a page translation in review is a separate permission (cms.review.approve).