Design system¶
Admin → Settings → Design system documents the interface patterns the product is built from: the reference behind every screen, not a screen you configure.
What it covers¶
| Area | What it defines |
|---|---|
| Layout | The shell: rail, sidebar, top bar, and how content sits inside them |
| Typography | The type levels and where each one is used |
| Colour | The tokens themes are built from — primary, danger, surfaces, text |
| Components | Buttons, tables, modals, panels, and their states |
| Governance | How a new pattern is proposed and accepted |
How it relates to Themes¶
Themes is where colours are applied to the workspace; the design system is where those colours are named and used consistently. Changing a theme does not change the design system, and editing this page does not change the workspace: it is a reference.
Who it is for¶
- Administrators — to understand why two screens look consistent, and what a theme will change.
- Implementers — to reuse the existing patterns instead of inventing a local style.
- Reviewers — to check a new screen against the documented components.
How to use it in a review¶
When a screen looks wrong, compare it against the patterns here before reporting it as a defect: spacing, button hierarchy, table behaviour, and modal layout are all specified. A deviation from the design system is a defect even when the screen "works".
Permissions¶
This page requires PM_SETUP. See
Permission reference.
Related¶
- Themes — applying colours to the workspace.
- Environment — regional formats.
- Language — the labels used across the interface.