Tokens and environments

Create a project token for builds and CI. Keep it out of browser code.

Create a token

1. Open Tokens and select the project and environment.
2. Choose New token and use a recognizable name such as GitHub Actions.
3. Copy the complete value immediately. Linguana stores only its hash and never shows the secret again.
4. Save it as LINGUANA_PROJECT_TOKEN in the matching CI environment.

export LINGUANA_PROJECT_TOKEN='lna_…'

Do not prefix it with VITE_, serialize it into client state, log it, or commit it to an environment file.

Environment policy

Use development tokens for manifest upload and optional build-triggered development publishing. Keep production publishing in the dashboard’s explicit release workflow. A token is scoped to its project and environment; a correct-looking token from another environment should be rejected.

Rotate safely

1. Create the replacement token.
2. Update CI and complete a successful authenticated build.
3. Confirm Last used changed for the replacement.
4. Revoke the old token.

Next

Connect hosted translations using the token. For runtime delivery, use a browser-safe publishable key as described in Show translated content.