FIGR / UI TEMPLATE

Organization Settings

Manage organization identity, domains, defaults, data region, workspace rules, and ownership in one settings surface. The screen connects General and Domains so workspace admins can find the “Save changes” action while checking workspaces and verified domains.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Organization name · Northstar and Primary domain · northstar.ai, rather than an empty visual shell.

Organization Settings

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

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 with

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

What to look for

  • Primary action: Save changes is clearly available where the task happens.
  • Main view: General keeps the starting point obvious.
  • Connected view: Domains supplies nearby context.
  • Metric: Workspaces is visible with a meaningful value.
  • Another signal: Verified domains helps people judge what to do next.
  • Representative record: Organization name · Northstar makes the example specific.
  • Second record: Primary domain · northstar.ai shows the pattern works beyond one item.

States to consider

  • Missing required details; show what people can do instead of leaving a blank panel.
  • Loading general without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for domains; 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 it fits

General → Domains → Save changes → Review outcome

Patterns in this screen

Form, General, Domains, Defaults, accessible states, contextual actions

UX choices to review

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 Organization name · Northstar with Primary domain · northstar.ai. Make workspaces clear, then use verified domains 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: Notification Preferences, Compliance Center, Integration Settings.

Try a similar screen in Figr

Design a organization settings screen for our existing software product. Use our real design-system tokens, components and product language. Show General and Domains, include believable records such as Organization name · Northstar, and make save changes easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗