Role Permission Setup

Define product roles, compare permission coverage, and spot members with elevated access. The screen connects Roles and Permissions so workspace admins can find the “Create role” action while checking custom roles and permissions.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Workspace Admin · 42 permissions and Billing Manager · 14 permissions, rather than an empty visual shell.

Role Permission Setup
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Create role

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 “Create role” action without losing sight of custom roles, permissions and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Create role is clearly available where the task happens.
  • Main view: Roles keeps the starting point obvious.
  • Connected view: Permissions supplies nearby context.
  • Metric: Custom roles is visible with a meaningful value.
  • Another signal: Permissions helps people judge what to do next.
  • Representative record: Workspace Admin · 42 permissions makes the example specific.
  • Second record: Billing Manager · 14 permissions 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 roles without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for permissions; clarify who can continue.
  • Success after choosing Create role; 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

Roles → Permissions → Create role → Review outcome

Patterns used

Workspace, Roles, Permissions, Members, 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 Workspace Admin · 42 permissions with Billing Manager · 14 permissions. Make custom roles clear, then use permissions 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 “Create role” action. The happy path alone is not enough.

Related UI examples: SSO Setup, Profile Setup, Team Invitation.

Start from this in Figr

Design a role permission setup screen for our existing software product. Use our real design-system tokens, components and product language. Show Roles and Permissions, include believable records such as Workspace Admin · 42 permissions, and make create role easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr