Admin Console

Give workspace admins one place to manage members, roles, domains, integrations, policies, and recent administrative changes. The screen connects Overview and Members so workspace admins can find the “Add member” action while checking members and admins.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as SCIM sync completed and Admin role granted, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Workspace

Primary action

Add member

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Add member” action without losing sight of members, admins and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Add member is clearly available where the task happens.
Main view: Overview keeps the starting point obvious.
Connected view: Members supplies nearby context.
Metric: Members is visible with a meaningful value.
Another signal: Admins helps people judge what to do next.
Representative record: SCIM sync completed makes the example specific.
Second record: Admin role granted shows the pattern works beyond one item.

States worth designing

First-use workspace; show what people can do instead of leaving a blank panel.
Loading overview without changing the layout unexpectedly.
Unavailable or restricted panel; explain the problem and preserve work.
Permission denied for members; clarify who can continue.
Success after choosing Add member; 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

Overview → Members → Add member → Review outcome

Patterns used

Workspace, Overview, Members, Access, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare SCIM sync completed with Admin role granted. Make members clear, then use admins 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 “Add member” action. The happy path alone is not enough.

Related UI examples: Audit Logs, Access Reviews, Security Incidents.

Start from this in Figr

Design a admin console screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Members, include believable records such as SCIM sync completed, and make add member easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr