Access Reviews

Review who has access to sensitive product areas, capture reviewer decisions, and surface stale or risky entitlements. The screen connects Reviews and Users so workspace admins can find the “Start review” action while checking in scope and reviewed.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Finance admins · 24 users and Production access · 62 users, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Workspace

Primary action

Start review

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 “Start review” action without losing sight of in scope, reviewed and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Start review is clearly available where the task happens.
Main view: Reviews keeps the starting point obvious.
Connected view: Users supplies nearby context.
Metric: In scope is visible with a meaningful value.
Another signal: Reviewed helps people judge what to do next.
Representative record: Finance admins · 24 users makes the example specific.
Second record: Production access · 62 users 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 reviews without changing the layout unexpectedly.
Unavailable or restricted panel; explain the problem and preserve work.
Permission denied for users; clarify who can continue.
Success after choosing Start review; 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

Reviews → Users → Start review → Review outcome

Patterns used

Workspace, Reviews, Users, Roles, 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 Finance admins · 24 users with Production access · 62 users. Make in scope clear, then use reviewed 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 “Start review” action. The happy path alone is not enough.

Related UI examples: Audit Logs, Security Incidents, Admin Console.

Start from this in Figr

Design a access reviews screen for our existing software product. Use our real design-system tokens, components and product language. Show Reviews and Users, include believable records such as Finance admins · 24 users, and make start review easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr