Reviewers and translators
On this page
The review area is for teams who want a second pair of eyes on translations before they go live. It is at Review in the dashboard. Editors and above see it in the menu. People you invite for single languages see only this area.
Two jobs per language#
- A translator can suggest a translation and write comments.
- A reviewer can approve or reject suggestions and write comments.
Owners and admins can do both for every language. Editors can suggest and comment in every language. Viewers can only read. A collaborator invited for specific languages sees only those languages. Other languages look as if they do not exist.
The flow#
- A translator suggests new text for a string.
- While review is required for the site, the suggestion waits as Pending. It is not saved as the live translation, so it cannot be published by mistake.
- A reviewer reads the source, the live text and the suggestion with the changed words marked.
- The reviewer approves or rejects. A rejection needs a reason.
- An approved suggestion becomes a Reviewed translation.
The person who wrote a suggestion cannot approve it, unless an owner or admin turns on self-approval for the site.
Other tools#
- Comment threads on each string, which can be resolved and reopened.
- A history of every step, with who did it and when. You can propose an older version again.
- Approve many strings at once, up to 200.
- Withdraw your own suggestion.
Site settings#
| Setting | Default |
|---|---|
| Require review | On |
| Allow self-approval | Off |
| Reviewers may publish | Off |
| Block publishing while suggestions are pending | Off |
Owners and admins can always request a publish. By default reviewers may not publish. The owner approved that default on 2026-10-28 (decision D49), and an owner or admin can change it per site. A publish request is refused when nothing approved is newer than the last publish.
Invite a translator, reviewer or client#
Owners and admins open Review > People.
- Type the e-mail address.
- Choose what the person may do: Translator (suggests and comments), Reviewer (approves, rejects, comments) or Read-only (looks at the queue, strings and comments; for clients).
- Tick the sites and the languages. Invitations are always for chosen sites and languages, never for the whole account. A site only gets the languages it has.
- Pick the language of the invitation e-mail and send it.
The person gets an e-mail with a button to the Accept an invitation page and a one-time code. They sign in with the invited e-mail address (or create an account with it) and confirm. The code works once and expires after 7 days. You also see the code once on your screen, in case the e-mail does not arrive. Send again replaces the old code.
The code stays in the link while the person signs in and while they set up two-factor sign-in, which owners and admins need before they can open anything. If they create a brand-new account first, they open the e-mail link again after confirming their e-mail address.
Read-only client access is part of the Business plan. Translators and reviewers are available on every plan today. The plan features collaboration (inviting people) and review (approving and rejecting) are checked against your plan; on a plan without them the page shows a notice with a link to upgrade, and nobody loses anything that is already published.
Who has access#
Review > People lists every invited person with their sites, role and languages. Remove access takes a person away from one site in one click; Remove from all sites takes everything away; the small x next to a language removes only that language. Each removal is written to the audit log. Open invitations can be cancelled or sent again.
What an invited person sees#
Only the review area: the sites and languages they were given, the queue, the strings and the comments. After accepting, Open review takes them straight to the workspace they were invited to. The menu shows Review, Inbox, Account and, if they have a workspace of their own (everyone who signed up does), My workspace. My workspace switches back to their own dashboard with the normal full menu; to return, they use the invited workspace from Review. Everything else of your account is hidden from them.
Your inbox#
Review > Inbox is your own list of notifications: you got a language, a suggestion needs your review, someone commented on a string, your suggestion was approved or rejected, someone accepted your invitation. The number of unread notifications is shown next to Inbox in the menu. Mark one or all as read. Notifications never contain translation text.
The optional daily e-mail summary is off until you turn it on in the inbox. It sends at most one e-mail a day, only when something new is waiting.
Review rules per site#
On Review > People you set the rules of each site (the table below). Changes are written to the audit log.
Reviewed translations#
An approved suggestion is stored as a Reviewed translation. A machine translation never overwrites it. The Usage page counts it as reviewed. The translations table shows Waiting for review or Review: rejected next to a string that has an open review step.
The reviewed mark in the published translations#
Every time you publish, the signed manifest says, for each language, how many strings a person approved (the reviewed count), and the language file lists which ones. Strings are marked only when their latest version was approved in the review queue; a later machine rewrite never keeps the mark. Your visitors do not see it; the language switcher does not show it.
Where you see it:
- Usage shows, per language, how many of the translated strings were checked by a person (reviewed or written by hand).
- Search engines (our own site, back office): machine translations stay
noindexuntil the owner allows indexing. A separate switch, Only languages a person has reviewed, lets a language into the sitemap and hreflang once at least 90 % of its strings are approved (our judgement, verify with an SEO adviser). Languages below that stay out of search results. - WordPress plugin: the option
index_only_reviewed(off by default) does the same per language;min_reviewedsets the share (0.9 by default).
Bundles published before this feature carry no mark and count as "not reviewed".