> ## Documentation Index
> Fetch the complete documentation index at: https://hyperlocalise.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# For translators and reviewers

> Find your assigned content, edit translations, resolve quality issues, and hand off reviewed work.

Use this path when a teammate has prepared a project for you. Ask for the project, source file, target locale, and scope of the review before editing.

## Before you start

Accept your workspace invitation using the invited email address. Your workspace role controls which actions you can take; project access controls which content you can open. Translators can prepare drafts. Approval requires a reviewer, localization manager, or administrator with access.

If the project is missing, follow [Project access](/platform/projects/access).

## 1. Read the context

Open the project's guideline and review the glossary or other [language resources](/platform/knowledge) provided for the work. Confirm the audience, tone, and terms that must stay unchanged.

## 2. Open the content

Open **Projects**, select the project, and open **Files**. Select the source file and target locale to open the [Content Editor](/platform/cat). Confirm the locale before changing text.

Connected TMS projects expose the actions supported by that provider. If an action is unavailable, check [TMS capabilities](/platform/tms) and your provider permissions.

## 3. Edit and check

Use **Queue** to find the requested strings. Review each source and target in context, and use glossary and translation-memory suggestions where appropriate. Check placeholders, ICU syntax, and length before saving or approving.

Check **Untranslated**, **Needs review**, and **Has issues** separately. Filtering one category can hide work in another.

## 4. Resolve questions and approve

Use [Board issues](/platform/translation/issues) for wording or product decisions that need a teammate. Include the file, key, locale, and question.

If you have approval access, review and approve the final text. Otherwise, hand the draft to an authorized reviewer. If an approval action is unavailable, check [roles and permissions](/platform/workspace/roles).

## 5. Hand off the result

Confirm the agreed files and locales are reviewed, and identify any unresolved issues. Use [Download translated files](/platform/translation/download) for product delivery or a [filtered queue export](/platform/guides/review-handoff) for an offline review reference.

## Next

Keep the [Content Editor guide](/platform/cat) nearby while reviewing. Use [quality troubleshooting](/platform/help/quality) when terminology, placeholders, or suggestions do not match your expectations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.