Team of 2 · B2B SaaS · Admin tooling · 7 weeks · In development
Nexus Admin Console

Self-serve feature and role management inside Nexus’s Admin Console

WHAT I WORKED ON Interaction Design · Multi-step Form Flows · Delete & Error Prevention
Developer overwhelmed with feature tickets

Every change to the platform’s features & user roles needed a developer

Nexus is built from features. Each feature has roles, which are levels of access: a viewer can only read logs, an editor can change them. RBAC (role-based access control) is the system that stores those roles

Ticket process flow diagram
  • Admins waited
  • Developers got interrupted
  • More features = more tickets, it didn’t scale

How might we let admins manage features & roles on their own, with no developer in the loop?

(02) THE SOLUTION

Feature Directory

A tab in Nexus’s Admin Console where admins add, rename and delete features and roles themselves, built to take the ticket and the developer out of routine changes

Nexus Admin Console Interface Laptop Mockup Integration Hub Card
ENTRY POINTS

Create

Add a feature, with new or existing roles

Manage

Adding roles, renaming, deleting

(03) HOW IT WORKS

The conceptual mental model

Create a feature

name it

Assign roles

pick existing ones or create new ones, then add approvers

Go live

review, confirm, done

Workflow diagram
(04) UI

Create a feature

Add names: one the system uses, one admins see

Create a feature screen

Add roles from RBAC

Search to attach roles that already exist - existing roles are fetched

Add roles from RBAC

Or create new roles

Search to attach roles that already exist - existing roles are fetched

Or create new roles

Review

Check everything before it goes live

Review screen

Manage feature

Add roles, rename or delete them - Deleting a feature also removes its roles, approvers and settings

Manage feature screen
(05) DESIGN DECISIONS

A long form added scroll, became difficult to navigate & overwhelming as more roles were created

Intake step flow comparison

The intake was split into three steps so that each one asks for a single kind of thinking. A final review step was made mandatory, so everything gets checked once before it goes live.

Review step overview

Delete & rename on every row added visual clutter & increased the chance of accidental deletion

Delete and rename table comparison - before

Deletion was placed inside a 3-dot kebab menu, keeping the table clean while making deletion more intentional

Delete and rename table comparison - after

A simple confirmation message did not communicate the impact of deleting a feature

Simple confirmation modal

An impact-focused modal was introduced to clearly show the affected users, roles, and permissions before deletion

Detailed impact confirmation modal
(06) RETROSPECTIVE
Two perspectives on number 6 and 9

Defending the UX with Intent

Standing up for user needs during handoff by defending the logic behind critical safeguards, while staying grounded in engineering feasibility.

Reaching mutual decisions with POs

Understanding the business pressures POs face helped us make mutual decisions that hit business goals without hurting the user experience.