Translations

Customize translated interface text with workspace-specific overrides. Shared default translations remain available when an override is not present.

Find and Edit Text

1. Open Translations in the team workspace.
2. Search for the group, key, or text you need.
3. Open the translation and edit the text for the available locale.
4. Save and reload the relevant page to check it in context.

Viewing requires view_translations; changes require edit_translations. Available locales come from the application's supported language configuration. This screen does not add a new application language by creating a key.

Workspace Settings > Translations also provides workspace override management for users with manage_workspace_settings. Select the correct workspace before making changes.

Import and Export

Export downloads a JSON file for offline editing or backup. Import accepts JSON or CSV files up to 2 MiB, with a maximum of 5,000 translation rows.

• JSON can be a translation list or the exported object containing a translations list. Each row includes group, key, and a text object keyed by locale.
• CSV headers must begin with group,key, followed by unique locale names such as en,fr. Each row must have the same number of columns as the header.

Matching workspace overrides are replaced during import. Shared defaults and other workspaces are not changed. Review the reported created and updated counts after import. Team import and export actions require import_translations and export_translations respectively.

Preserve Dynamic Values

Keep placeholders and formatting used by the original string. Removing a variable can produce an incomplete message. Test the page in the intended language after changing text.

Troubleshooting

• Text unchanged: Check workspace, locale, group, and key, then reload.
• Import rejected: Check file type, size, row limit, structure, headers, and locale names.
• Cannot edit a default: Create or edit its workspace override through the available action.