Translations
RAMP supports multiple languages and allows Administrators to customize UI labels and translations for their tenant. The Translations page provides an interface for managing localized strings used throughout the application.
Required role: Administrator
Accessing Translations
Section titled “Accessing Translations”Navigate to Administration > Translations (or /_admin/translations).
How Translations Work
Section titled “How Translations Work”RAMP uses a key-based translation system where each piece of text in the user interface is identified by a unique key. Each key has a value for every supported language. When a user views the application, the text is displayed in their selected language.
Two values per translation row
Section titled “Two values per translation row”Every translation key stores two values internally:
| Column | What it holds | Who writes it |
|---|---|---|
| Shipped default | The value bundled with RAMP for this key in this language. | RAMP version updates only — you never edit this directly. |
| Effective value | The value the application actually serves. | Equals the shipped default until an administrator overrides it through this page. |
The translation editor exposes both:
- A status chip next to the key shows “Shipped default” (the value has never been customized in this tenant) or “User-modified” (an admin has overridden it).
- When the row is marked User-modified, a Shipped Default Value panel shows what RAMP currently bundles for that key in this language, alongside the field where you edit the effective value.
Override behavior across RAMP upgrades
Section titled “Override behavior across RAMP upgrades”RAMP version updates re-seed shipped defaults on every startup. Customizations survive because the re-seed only refreshes the shipped default column. The effective value is left untouched for any row marked User-modified.
For untouched rows (Shipped default), the effective value tracks any change RAMP ships — which means you automatically benefit from improved wording, typo fixes, and newly translated keys without redoing anything.
Managing Translations
Section titled “Managing Translations”Viewing Translations
Section titled “Viewing Translations”The Translations page displays all translation keys with their values for each configured language. You can:
- Search for specific keys or text values
- Filter by language
- Filter to show only keys with custom overrides
Editing a Translation
Section titled “Editing a Translation”- Find the translation key you want to modify (use the search field to narrow results).
- Click on the translation entry.
- Edit the value for the desired language(s).
- Click Save.
Resetting to Default
Section titled “Resetting to Default”If you have customized a translation and want to revert to RAMP’s shipped value:
- Find the row — look for the orange User-modified chip next to the key.
- Click on the translation entry.
- Review the Shipped Default Value panel to confirm the value you would receive.
- Click Reset to Default and confirm the prompt.
Reset sets the effective value back to the shipped default and clears the User-modified flag. From that point on, any future RAMP update that ships a new value for this key will be picked up automatically.
Admin-created keys
Section titled “Admin-created keys”When you save a value for a key that RAMP did not ship (a key you introduced through bulk import or custom code), the row is created with an empty shipped default. The detail panel shows “No shipped default (admin-created key)” for such rows. If a future RAMP version introduces the same key, the next re-seed will populate its shipped default for you while leaving your value alone.
Custom Labels
Section titled “Custom Labels”Beyond translating existing interface text, you can use translations to customize labels that match your organization’s vocabulary.
Common Customizations
Section titled “Common Customizations”| Default Term | Example Custom Term | Typical Reason |
|---|---|---|
| ”Template" | "Runbook” | Organization uses different terminology |
| ”Instance" | "Execution Plan” | Industry-specific language |
| ”System" | "Application” | Matches internal naming |
| ”Step" | "Task” | Simpler terminology |
Multi-Language Support
Section titled “Multi-Language Support”Adding Language Support
Section titled “Adding Language Support”RAMP ships with built-in support for several languages. The available languages are determined by the translation files included in the application.
User Language Selection
Section titled “User Language Selection”Each user can select their preferred language in their profile settings. Resolution order on every request:
- User personal preference (set via the user menu → Settings).
- Tenant default language (set on the Settings page).
- English as the final fallback when neither of the above is set.
Within a chosen language, any key without a tenant-specific value falls back to the shipped default for that language.
Translation Coverage
Section titled “Translation Coverage”When customizing translations, ensure you provide values for all languages your users need. If a translation key has a custom value in one language but not another, users of the other language will see the built-in default.
Best Practices
Section titled “Best Practices”- Start with high-visibility terms — customize the most frequently seen labels first (navigation items, page titles, button labels).
- Be consistent — if you rename “Template” to “Runbook”, apply this consistently across all related translation keys.
- Test with users — after making translation changes, ask a few users to review the interface to confirm the labels make sense in context.
- Document your customizations — maintain a record of which translations you have customized and why, to ease future maintenance.
- Update all languages — when you customize a key, update the value in every language your organization uses.