Reviews, context and knowledge sources

The translation editor keeps text, context and human review separate. A review approves one saved text revision and its ICU contract. A glossary or memory suggestion does not approve a translation and never saves a value automatically.

Language permissions

Owners and admins manage Editor permissions in Workspace → Members → Translation permissions. Existing Editors retain unrestricted language writing until Restrict translation writing is enabled. In restricted mode, select explicit project/language grants. New projects and languages do not gain permissions automatically. Review access is a separate grant. Owners and admins can write and review every active language.

Projects remain readable to current workspace members. A resource editor assignment does not grant translation writing or review access. Inactive languages and archived content remain read-only. Changing a shared ICU contract requires permission to correct every incompatible value; one unauthorized correction rejects the entire change.

Review a saved translation

1. Save the translation normally.
2. Hover over or focus the dashed-circle icon beside the saved text. Its tooltip shows Unreviewed · Review translation. Activate it to open the inline confirmation.
3. Select Memory source language. The project source language is selected initially.
4. Inspect the source and choose Approve.

You may review your own work if you have review permission. A Missing target cannot be approved. If the source is Missing, review can proceed without creating a memory pair. The same language cannot form a source/target memory pair. A changed source version rejects the operation instead of capturing a different pair silently.

Reviewed values use a checked-circle icon; its tooltip shows Reviewed · Revoke review when you have review permission. Without that permission, the icon only explains the saved review state and has no mutation action. Missing cells have no review icon. Status icons share the value’s row; confirmation controls appear only after activation. Cancel closes the confirmation and returns keyboard focus to the icon without changing the value.

Changing text or clearing its value removes that value’s current review. Changing the ICU contract invalidates affected reviews. Renaming a key or updating its description preserves reviews. Revoke review also invalidates fork copies carrying the same evidence; independent later approvals remain independent. Losing permission does not erase valid historical review evidence.

Use the Reviewed or Unreviewed language filter to find work. Review state is separate from translation coverage. Language headings show an outer review ring around the existing translation dot. The ring counts current reviews out of saved, nonempty translations: dashed red for none, dashed yellow for partial, solid green for all, and gray when the branch has no active keys. A green ring can surround a yellow dot when all available translations are reviewed but some keys are still Missing. Hover/focus explains both counts. See column coverage. API clients can review or revoke up to 100 cells atomically with expected versions and an idempotency key.

For a batch on the current table page, select keys and choose Review selected. Choose one target language and Approve or Revoke. For approval, choose a memory source from the displayed active columns; cancel and display another language first if needed. Inspect the frozen saved text, then choose Approve selected or Revoke selected. Missing targets block approval; unreviewed targets block revocation. A single version or permission conflict rejects the entire batch and leaves its scope visible for comparison. Cancel before changing the selection. This batch does not silently include other pages.

Key context

Open a key and choose Context to edit its description or existing scoped file notes. Save context and Cancel are explicit actions. Conflicts preserve the draft; refresh the current key before reconciling a newer version. Context belongs to the branch and participates in fork snapshots and merge comparisons.

Image uploads and complete file-format note round trips are still under implementation. Do not treat a saved description as proof that every import/export format retains it.

Glossaries and translation memories

In Workspace → Settings → Knowledge sources, owners and admins create a Glossary or Translation memory. A glossary concept contains a description and language terms, with alternatives, case sensitivity and do-not-translate flags. A managed memory entry contains a source/target language pair, text and an explicit Plain text or ICU contract. Managed entries are not Localisync human approvals.

Choose Manage resource to rename a source. Owners and admins can also assign Resource editors from current workspace members. Save the name and editor assignments separately; each uses the current resource version. An assigned Viewer can manage this resource but still cannot write or review translations. A conflict preserves your selection.

In Project → Settings → Glossary and memory sources, select readable sources and save the links. You may link several memories and select one Automatic review target. Approving translations records immutable pairs in that target when a saved source exists. Forking does not duplicate those pairs. Revoking the only supporting review removes an automatic entry from suggestions; independently supported or managed entries remain.

Open a translation cell and choose Glossary and memory suggestions. Use suggestion only fills the current draft. Inspect it, then Save; review remains a separate action. Exact matches use real source text equality. Similarity is a search score, not translation accuracy. Memory candidates must match the key’s ICU contract. Matching is limited to the linked resources and selected language pair; each result set is bounded to 25 entries. Glossary matching includes preferred terms and alternatives using each term’s case setting. Missing source/target text and blank glossary terms are rejected; meaningful whitespace is preserved rather than normalized away.

Archiving a resource stops linked suggestions and automatic recording. Removing the last project link removes ordinary member access; managers and assigned resource editors retain management access. Use knowledge file transfer for mapped glossary CSV and plain-text TMX previews, conflict choices and atomic Apply.

Optional Production gate

Owners and admins can enable Require reviewed translations in Project settings. Preview remains available. A new Production decision then requires review evidence for every exact text revision used by the package, including resolved fallback values. Reviewing unchanged text after Preview allows the same immutable package to be promoted. Policy and evidence are checked again at the durable publication decision.

Existing publications and rollback behavior are not changed retroactively. A committed publication continues its original delivery decision. This policy does not change the SDK protocol or add runtime review checks to downloaded translations.

Discussion

Open a key’s details and select Discussion. Every current workspace member, including a Viewer, can start a thread and reply. A new thread can apply to the whole key or one active language. Comments are plain text, not HTML. Choose up to 20 current members in Mention members; the selected references are saved with the comment. Newly mentioned members receive an inbox notification. Choose Reply to comment to notify that comment’s author; a general thread reply does not notify every participant. Mentioning the reply recipient produces one notification, not two.

Thread authors, Editors, Owners and Admins can Resolve thread and Reopen thread. Editors cannot edit someone else’s comment merely because they can resolve its thread. Authors can edit or remove their own comments; Owners and Admins can moderate any comment. Comment history retains earlier revisions, including the text before removal. Removal is not an erasure of that history.

Changes use the current version. A conflict keeps your unsaved text; refresh the thread and compare its current content before retrying. Leaving with an unsaved comment requires confirmation. Archived content is read-only. Threads remain bound to their original branch and are not copied by fork or merge.

Tasks

Select Tasks in the branch navigation. Owners and Admins can manage every task; Editors can create tasks and manage only those they created. Viewers can read tasks. Assignment does not grant task management, translation writing or review permission.

1. Choose Create task, enter a title and select Translate or Review.
2. Select the exact keys, using search and pagination as needed. Selections on earlier pages are retained. Only selected keys enter the task; later search matches do not.
3. Select an active language and an eligible member, then Assign language. Repeat for the languages in scope. Review assignments require separate review permission.
4. Optionally enter a deadline with its explicit UTC offset and a display time zone. The deadline is stored as an absolute time and displayed in that zone.
5. Review the cell count and Save task. A task is limited to 10,000 keys and 50,000 key/language cells.

Refresh progress reads current saved values and current reviews. Translate cells complete when their value is present; Review cells require approval of the exact current text and contract. Clearing a value or invalidating its review reopens the work. A lost permission, inactive language or archived key is Blocked, never completed work. The worker checks changed tasks and records completion/reopening notifications from the latest committed progress. Rapid changes before one check are combined into that latest state, rather than generating a notification for every intermediate edit.

Manage task edits the explicit scope, assignments, title or deadline with version control. A task’s type and creator cannot change. If someone changes it first, the whole save fails and your draft remains available. Task scope never follows the header into a different branch; fork and merge do not copy tasks.

Notifications and optional email

Open Notifications in the sidebar for mentions, replies, assignment/scope changes, completion, reopening and a single deadline reminder for unfinished tasks. View task or View discussion opens the exact branch record. Mark as read changes only your inbox. Use Refresh notifications for new events. Notifications remain inaccessible after workspace membership is removed or their branch is deleted.

Email is off initially. Enable Email me about new notifications across my workspaces and choose Save email preference to receive fixed event summaries and a sign-in link. Emails contain no translation, comment or task-title text. Current membership, active context and your preference are checked immediately before dispatch. Disabling email does not retract an email already accepted by the mail server.

A task receives at most one deadline reminder. Editing its deadline after that reminder does not start repeated overdue emails. Task changes and mentions are deduplicated; replaying the same request does not produce another notification. If SMTP delivery is uncertain, the inbox reports that state and the email is not automatically sent again. The inbox remains usable when email delivery fails.

Private images

Attach, preview and edit image context from the same key details. A shared workspace quota protects storage; AI images are separately opt-in. See private context images for limits, permissions and retained references.