Preset
Accent

Settings shell

Use the settings shell when the page needs slower form work, grouped decisions, and a local section rail that stays close to the active task.

Why this shell exists Settings pages usually need a calmer navigation rail, clearer section grouping, and enough width for forms without turning into a full application dashboard.

Choose this shell for profile settings, billing preferences, notification rules, workspace options, and other pages where users move through grouped controls instead of hopping across dense application views.

Local workspace rail

The local rail is a real wb-section-nav, not a custom settings-only component. It keeps nearby settings areas visible without competing with the global docs or app navigation.

Good fit
  • Grouped form sections with short descriptions
  • Preferences that benefit from local navigation
  • Destructive actions isolated at the end of the page

Embedded settings demo

This example uses the shared admin standard: page context in the header, sectioned cards for grouped work, full-width monospace fields for long values, and footer-owned submit actions.

Account settings

Use the settings shell for slower form work, grouped decisions, and a local wb-section-nav rail that stays close to the content.

Admin standard

Public profile

Manage how teammates see your workspace identity.

Used in navigation, invites, and workspace switchers.
Keep short identifiers in the shared two-column row.
Optional context shown on the public workspace profile.
Paths, commands, URLs, and tokens should use monospace styling.

Preferences

Row-based settings work well when each preference needs a short explanation and one clear control.

Default densityChoose the baseline spacing scale for the workspace interface.
Security alertsNotify owners when a new device signs in or a role changes.
Default landing pageChoose where members land after they sign in.

Detail and status example

Detail pages should use structured label/value rows and status summaries that distinguish failures from optional notices.

Primary domain
atlas-cloud.example
CMS app path
/var/www/atlas-cloud/web_root
CMS public path
/var/www/atlas-cloud/web_root/public
Healthy with notices Core checks passed. One optional integration is not configured for this workspace, but the base infrastructure is healthy.

Danger zone

Reserve the final section for destructive actions that should stay separate from everyday settings.

Delete workspacePermanently remove all members, projects, and billing history from this workspace.

Delete this workspace?

This action permanently removes members, projects, and settings. Keep destructive confirmation inside a shipped modal surface instead of inventing a custom alert layer.