Project settings control how app localization is translated, reviewed, and maintained.
When To Review Settings
Revisit settings whenever you:
- Add new target languages.
- Change brand tone or translation guidance.
- Move from manual runs to automated repository sync.
- Notice recurring review-state or stale-key issues.
Translation Preferences
- Tone:
formal,neutral,informal,playful - Custom Prompt: Additional instruction text used for translation requests
Use these to shape translation style consistently across app surfaces.
Automation
- Auto Remove Stale Keys: Deletes keys marked with stale extraction state.
- Auto Retranslate on Key Rename: Enables rename-aware retranslation marking.
Branch-based automation is configured separately from project settings. For repository projects, use the Repository Automation page to choose push rules, pull request rules, and manual sync.
Quality
- Quality Score Enabled: Gated by plan eligibility; enables health-check workflows.
Quality scoring helps prioritize review effort instead of treating every row the same.
Access and Permissions
Only authorized project settings managers can update these fields.
Common Mistakes
- Updating tone/prompt and expecting old localized rows to change instantly without reruns.
- Looking for push or pull request triggers inside project settings instead of the Automation tab.
- Enabling stale-key removal without confirming source extraction stability.
- Treating rename retranslation as a general content refresh toggle.