Notification Preferences

Let users control product, email, digest, and urgent notifications by event without hiding important defaults or channels. The screen connects Preferences and Email so workspace admins can find the “Save changes” action while checking enabled and muted.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Mentions · Product + email and Assignments · Product, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Form

Primary action

Save changes

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Save changes” action without losing sight of enabled, muted and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Save changes is clearly available where the task happens.
Main view: Preferences keeps the starting point obvious.
Connected view: Email supplies nearby context.
Metric: Enabled is visible with a meaningful value.
Another signal: Muted helps people judge what to do next.
Representative record: Mentions · Product + email makes the example specific.
Second record: Assignments · Product shows the pattern works beyond one item.

States worth designing

Missing required details; show what people can do instead of leaving a blank panel.
Loading preferences without changing the layout unexpectedly.
Invalid or conflicting entry; explain the problem and preserve work.
Permission denied for email; clarify who can continue.
Success after choosing Save changes; confirm the result and the next step.
Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Preferences → Email → Save changes → Review outcome

Patterns used

Form, Preferences, Email, Product, accessible states, contextual actions

Why these choices work

Put requirements beside each field and show validation near the source of the error. Keep entered details if saving fails.

In this design, people should be able to compare Mentions · Product + email with Assignments · Product. Make enabled clear, then use muted to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Save changes” action. The happy path alone is not enough.

Related UI examples: Integration Settings, Organization Settings, API Access.

Start from this in Figr

Design a notification preferences screen for our existing software product. Use our real design-system tokens, components and product language. Show Preferences and Email, include believable records such as Mentions · Product + email, and make save changes easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr