Language Settings
Enable or disable custom translations for the workspace.
Language settings control whether Agiled uses workspace translation overrides. Use this page before adding custom labels in Settings > Translations.
Only enable custom translations when someone owns reviewing the translated labels. Outdated labels can make the app harder to support.
Treat language overrides as workspace configuration. A bad label can affect training, support, public pages, and customer instructions.
Use custom translations for workspace-specific terminology, not for hiding features or creating labels that differ from your team's process.
Enable Custom Translations
- Open Settings.
- Go to Language.
- Turn on Use custom translations.
- Save the setting.
- Add or edit translations from Settings > Translations.
When enabled, Agiled reads matching workspace translation entries instead of the default product text.
Enable translations during a review window when an owner can check the affected screens. Do not turn them on immediately before a customer-facing launch unless the labels have already been tested.
Disable Custom Translations
Turn off Use custom translations when you want the workspace to use Agiled's default text again. Existing translation rows are not deleted, but they stop affecting the workspace while the setting is off.
Use this as a workspace-wide rollback. If only one label is wrong, edit or delete that translation instead so the rest of the approved terminology stays in place.
Translation Ownership
Assign one owner for workspace terminology. That owner should review changes to labels used in finance, HRM, public pages, forms, booking, and error messages. Small wording changes can affect training and customer support.
After Saving
Saving language settings clears the runtime translation cache. Users may need to refresh active browser tabs before they see updated labels.
Review the most common work areas after enabling translations: dashboard, tables, create/edit dialogs, finance documents, public forms, booking pages, checkout pages, email templates, and error messages. A translation that is clear in Settings can still be confusing inside a compact button, column heading, or public customer page.
Check long translations on small screens and compact tables. Text that is correct linguistically can still be too long for the UI.
Before Disabling
Confirm no team process depends on custom labels. Disabling the setting does not delete translation rows, so you can re-enable them later after review.
If a translation causes confusion, disable the setting only when you need an immediate workspace-wide rollback. For a single bad label, edit or remove that translation entry and refresh the affected page.
Review Checklist
After enabling translations, test compact UI areas, public pages, finance documents, forms, booking pages, and emails. Long labels can break clarity even when the translation is technically correct.
Review both internal and customer-facing screens. A translation that works for employees may be too informal, unclear, or long for customers.
Troubleshooting
If labels do not update, save the setting, refresh the browser tab, and confirm the translation key exists.
If users report confusing labels, turn off custom translations temporarily only when a fast rollback is needed.
If only one area is confusing, edit the specific translation instead of rolling back the entire workspace.
Rollout Checklist
Before enabling translations broadly:
- assign a terminology owner
- review internal navigation and tables
- review public forms, booking, checkout, and finance pages
- test long labels on small screens
- document how admins should roll back a bad label