Skip to main content

How to allow users to review translations without editing segments

The Editor includes a dedicated access right that turns the Editor into a review-only workspace. It is designed for users who validate translations without changing content: typical reviewers who check quality, flag issues through comments, move segments through statuses, and close the loop once the translation team has applied edits.


What is the review-only access right?

A user profile option that blocks every editing action in the Editor. Users with this right can still open the Editor, read segments, change segment and job status, and use comments, but they cannot modify source or target text, labels, custom fields, bookmarks, or locks. It applies identically to Standard and Codyt jobs.

The right acts as an override: it takes precedence over any editing permissions granted elsewhere in the same profile.


How do I enable it?

The right is disabled by default and is configured per user profile.

Follow these steps:

  1. Go to ConfigurationUsersUser profiles.

  2. Open the profile you want to configure.

  3. In the Editing section, enable Can only review content in the translation editor.

  4. Save.

Users assigned to the profile enter review-only mode the next time their Editor session loads. No cache wait, no sign-out required.


What can a reviewer do in the Editor?

A typical reviewer opens the assigned job, reads through the segments, validates the translations, and drives the work forward through comments and status changes.

Action

Allowed

Open the Editor for the assigned job

Yes

Read segments, memories, terminology, revisions

Yes

Add comments to flag issues or leave feedback

Yes

Resolve their own comments once the edit is applied

Yes

Change segment status (inline or in bulk)

Yes

Update job status (e.g. mark the review as complete)

Yes


What is blocked?

Anything that would modify the content itself is prevented, whether applied one segment at a time or through batch actions:

  • Editing source or target text, including Find & Replace.

  • Editing labels, custom fields, Key/Context, or bookmarks.

  • Locking, unlocking, splitting, or joining segments.

  • Deleting or resolving other users' comments.


Can a reviewer still move the job forward?

Yes. Status changes are the main way reviewers signal progress. They can mark each segment as reviewed or send it back through a status change, use batch status changes to move many segments at once, and update the overall job status when the review is complete. Together with comments, this is enough to run a full review cycle without touching the content.


Which viewing rights shape what a reviewer sees?

A reviewer's ability to make a sound assessment depends on having enough context visible on screen. Review-only does not touch any of the "Can see" rights, so they continue to govern which panels, columns, and details show up in the Editor. When you set up a review-only profile, check that these rights are enabled so the reviewer has everything they need:

  • "Can see comments": Shows existing comment threads on segments and allows the reviewer to read past discussion.

  • "Can see revision history": Gives access to the log of changes made on each segment over time.

  • "Can see QA issues": Displays flagged issues in the QA Panel.

  • "Can see labels and custom fields": Makes metadata columns and fields visible in the grid and Overview Panel.

The other rights in the Editing section, such as editing translations, splitting or joining segments, locking or unlocking, running QA checks, or editing labels and custom fields, are intended for users who actively work on the content (translators, revisers, QA leads). These rights are automatically disabled when review-only is enabled on the profile.


Learn More

  • Comments: How comments work in the Editor, including threads and resolution.

  • Revision History: Track changes to segment content over time (useful during review stages).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.