Settings Page
A settings page holds choices that change how an app works across tasks. Good defaults let most people start immediately.
Another example
A workspace owner changes the weekly summary and sees which team members the choice affects.
Main parts
- 01Settings group
- 02Plain label
- 03Current value
- 04Effect and scope
- 05Save feedback
Use it when
Use it for general choices that people change rarely and expect to find again.
Do not use it when
Do not hide task-specific choices here. Put those choices beside the task they change.
Name used in code
scope + safe default + grouped controls + save feedback + permissions Before you ship
Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages.
Outcome: Use Settings Page to solve this user need without losing the current context. User context: A workspace owner changes the weekly summary and sees which team members the choice affects. Recommended pattern: Settings Page. Why it fits: Use it for general choices that people change rarely and expect to find again. Do not use it when: Do not hide task-specific choices here. Put those choices beside the task they change. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Settings Page. Definition: A settings page holds choices that change how an app works across tasks. Good defaults let most people start immediately. Release checks: Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.