CrownSync Playbooks supports two languages: English (the default) and Cymraeg (Welsh). This reflects the platform's focus on UK organisations and compliance with the Welsh Language (Wales) Measure 2011 for organisations operating in Wales. You can switch between languages at any time, and your preference is saved to your user profile.

Switching Between Languages

To change your language preference:

Click your profile avatar in the top navigation bar
Select Language from the dropdown menu
Choose either English or Cymraeg
The interface updates immediately without requiring a page reload

Alternatively, you can change the language from the settings page under Preferences > Language. The language switcher is also available in the footer of every page for quick access.

Your language preference is stored against your user account, so it persists across sessions and devices. If you sign in from a different browser or computer, your preferred language will be applied automatically.

What Gets Translated

When you switch to Cymraeg, the following elements of the interface are translated:

Navigation and menus— All sidebar items, top navigation labels, dropdown menus, and breadcrumbs are displayed in Welsh.
Buttons and actions— All interactive elements including Save, Publish, Export, Cancel, and other action buttons.
Form labels and placeholders— Input fields, select dropdowns, and form validation messages are translated.
Status badges and indicators— Severity levels, incident statuses, and access mode indicators.
Notification text— Both in-app notification summaries and the notification preferences page.
Error messages— Validation errors, permission errors, and system messages are displayed in Welsh.
Dashboard labels— Stat card titles, activity feed descriptions, and quick action labels.
Documentation navigation— Section titles and page titles in the documentation sidebar.

What Stays in English

Certain content remains in English regardless of the language setting. This is by design, as translating this content could introduce ambiguity or compliance risks:

Playbook content— The actual incident response guidance within playbooks remains in English. This includes all section text, checklists, and procedures. Incident response terminology is standardised in English across the UK cyber security industry, and translating technical procedures could introduce dangerous misinterpretation.
Regulatory references— ICO, FCA, PRA, and other regulatory body names and their specific requirements are kept in English to ensure accuracy.
Communication templates— Templates for regulatory notifications and external communications remain in English, as most UK regulators require English- language submissions.
Audit log entries— Audit records are stored in English to maintain a consistent, unambiguous trail for compliance and legal purposes.
PDF exports— Exported documents are generated in English, including watermarks, classification markings, and verification text.
Technical identifiers— Playbook slugs, API endpoints, condition codes, and other technical references.

Why playbook content stays in English

Incident response procedures use highly specific technical terminology. Translating phrases like “isolate the affected endpoint” or “revoke OAuth tokens” into Welsh could create confusion during a high-pressure incident. The interface language helps Welsh-speaking users navigate the platform comfortably, while the technical content remains in the language used by the UK cyber security community.

Translation Quality

All Welsh translations are professionally produced and reviewed by native Welsh speakers. CrownSync does not use machine translation for the interface. If you notice any translation issues or have suggestions for improvement, please contact [email protected] and our localisation team will review the feedback.

The translation files are maintained as part of the platform's internationalisation system and are updated alongside feature releases to ensure new interface elements are available in both languages from launch.