top of page

Designing safer role management for enterprise admins

I designed a role-management experience that helps workspace admins create, review, and manage custom roles with clearer permission scope, risk awareness, and decision support.

ns-create-role-med-risk-desktop.png
ns-create-role-med-risk-mobile_edited.png
joan-alps.png

Scenario: Joan needs to create a role without overexposing access.

Joan Alps is a Workspace Admin at Northstar Analytics. She needs to create a custom Growth Ops Manager role that gives teams access to projects, reports, and dashboards without exposing billing, user management, or role-management controls.

Roles List

A governance-first view of every role

The Roles List helps Joan compare system and custom roles by risk, permission scope, assigned users, and review status before creating a new custom role. This helps her identify reusable access patterns while avoiding duplicate roles or overexposed permissions.

Product Decisions

Search vs Comparison: I separated search from comparison because they support different admin behaviors: search helps Joan find a known role quickly, while row selection supports deeper evaluation across multiple roles.

What does this demonstrate?

System-level thinking across role comparison, auditability, and access governance.

ns-roles-list-3-selected-desktop.png
Create Role

Create custom roles with real-time decision support

Joan can define a new Growth Ops Manager role, select from eligible permissions, and understand the impact of her choices as she configures access. The layout keeps role setup, permission selection, and risk feedback visible together.

What does this demonstrate?

Risk-aware workflow design that balances admin speed with control.

ns-create-role-med-risk-close-up-desktop.png
Role Summary

Turning permission choices into risk-aware decisions

I introduced a Role Summary to shift the experience from a static permissions form into a decision-support tool. As permissions change, Joan can see risk level, enabled permissions, sensitive access, assigned users, and the role's current configuration status.

What does this demonstrate?

Product judgment around surfacing the right information at the moment of decision.

ns-create-role-low-risk-desktop.png

Baseline access

The Risk level updates as the permission scope changes, helping admins understand impact before saving a draft role.

ns-create-role-med-risk-close-up-desktop.png

Growth Ops Manager Configuration

Risk Warning

Slow down only when the decision carries risk

When selected permissions increase risk, the system gives Joan a clear checkpoint before saving. This adds intentional friction only when it protects the workspace from high-impact access decisions.

Product Decisions

Warning: I added a warning only when the draft role reaches High risk, so Joan gets a final checkpoint before saving sensitive access changes.

What does this demonstrate?

Thoughtful use of friction for sensitive enterprise workflows.

ns-create-role-warning-modal-desktop.png
Mobile Adaptation

Preserving clarity when dense permissions move to mobile

On mobile, the permissions table becomes stacked permission cards while the Role Summary stays compact and accessible. Risk definitions are available through a tooltip on desktop and a bottom sheet on mobile, helping Joan understand Low, Medium, and High risk without crowding the interface.

What does this demonstrate?

Responsive product thinking that adapts information density without losing governance context.

ns-create-role-med-risk-mobile.png

Compact summary state

ns-create-role-med-risk-level-mobile.png

Risk level guide

ns-create-role-med-risk-summary-expanded-mobile.png

Expanded summary state

Designed role creation as part of a broader role-management system across list views, creation, review, and confirmation states.

Systems Thinking

Across the role-management experience, I focused on making access decisions clearer, safer, and easier to manage.

Supported safer access management through audit-friendly signals, clear ownership, and safeguards around high-impact actions.

Enterprise Governance

Kept default views scannable while giving admins access to deeper permission and risk context when needed.

Progressive Disclosure
bottom of page