> ## 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 localization managers

> Set up a project, prepare language resources, and take your team through its first review and delivery.

Start with one source file and one target language. Complete a translation and review cycle before expanding to more content or automating delivery.

## Before you start

Choose the workspace that will own the work. Ask an administrator for the localization manager role and the project access you need. See [roles and permissions](/platform/workspace/roles).

## 1. Choose where content lives

Use a native project to manage files in Hyperlocalise Platform. If your team already manages content in a supported TMS, compare [connected projects](/platform/tms) before moving it. A connection gives access to provider-owned content; it does not migrate that content.

## 2. Prepare a project

[Create a project](/platform/projects/create-project), choose the source and target languages, and [upload a source file](/platform/projects/files). Confirm the file and target locale are available before requesting translation.

If you already have translations, follow [Import existing translations](/platform/translation/import). For a broader move, use the [migration checklist](/platform/getting-started/moving-to-hyperlocalise).

## 3. Give the team shared context

Add [guidelines](/platform/knowledge/guidelines) for tone and audience. Link a glossary for required terminology and a translation memory for reusable translations. [Language resources](/platform/knowledge) explains how these work together.

[Invite teammates](/platform/workspace/members) and confirm their [project access](/platform/projects/access). Assign drafting to translators and approval to reviewers. Share the source paths, target locales, and release scope with each person.

## 4. Translate and review

[Choose a translation workflow](/platform/translation/workflows), then run the first batch. Follow its [job status](/platform/translation/jobs). Once generation completes, [prepare a review handoff](/platform/guides/review-handoff).

Check untranslated strings and unresolved issues as well as the review queue. A successful job does not mean every translation has been approved.

## 5. Deliver and repeat

[Download translated files](/platform/translation/download) and verify them in the destination product. Confirm the locale, terminology, layout, and placeholders with the reviewer.

Once that cycle works, [automate repeated work](/platform/automation/create-automation). Test the automation on a small upload and inspect its output before expanding its scope.

## Next

Follow [Your first translation](/platform/getting-started) with a small example, or share [For translators and reviewers](/platform/getting-started/translators) with your team.


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