Skip to main content
Open Projects, select the project, and open Settings. Check Source connection first: native projects and connected TMS projects have different editable settings.

Update project details

In General, review Name, Identifier, and Description. Use the name to help teammates find the project and the description for scope, ownership, or release notes. The identifier is the prefix for new issue IDs, such as HL-12, and must be unique within the workspace. Changing it keeps existing issue IDs. Follow the identifier requirements shown in the form. Select Save settings after editing. Reopen the settings to confirm the saved values. If a field is read-only, check the project’s source connection and your permissions.

Manage languages

Use Locales to change the source and target locales of a native project. Provider-owned languages are managed in the connected TMS. Follow Manage project languages, especially before changing a source language.

Configure review behavior

Under Translation & Content Editor behavior, use Automatically merge identical strings to set the Content Editor default. Review the confirmation before changing it. Identical text can have different meanings in different contexts, so agree on merging with your reviewers. Translators can still switch View → Show strings in the editor. See Merge strings. Allow source text editing lets source text in JSON, JSONC and ARB files be edited in the Content Editor and through the API, and makes uploads and repository syncs keep those edits; a GitLab sync sends them back in its merge request. See Edit source text in Hyperlocalise. For tone and terminology, configure guidelines, glossaries, and translation memories.

Connect delivery tools

For a native project, Sync moves source files in from a GitLab repository when you select Sync now or on a schedule, and sends approved translations back as a merge request. A GitHub repository syncs from its Automation settings under Integrations instead. See Sync content with a repository. For a native project, Connect CLI & CI shows the project ID and sample i18n.yml. Follow Connect the CLI to configure credentials, source paths, and target paths. CDN publishes approved translations to a public hash for mobile and web apps. Create a distribution, pick files and locales, then Release. Use the hosted Hyperlocalise CDN or a customer S3 destination. See CDN distributions. Use Open in provider for settings owned by a connected TMS. See TMS integrations for provider capability boundaries.

Before deleting a project

Download the content you need to retain and inspect jobs, automations, and delivery configurations that refer to the project. Read the deletion confirmation before proceeding.
Project deletion is permanent. Jobs, files, and shared context linked to the project lose their project association. Do not treat deletion as a reversible archive action.

Next

Check project access, upload source files, or prepare a review handoff.