Reframing access as a system, not a list of screens
The redesign started with relationships: who requests access, who approves it, what changes over time, and how every action stays visible.
Identity management system
A hierarchical role model helps users navigate complex access structures without losing context.
IDM is an enterprise system for managing employee identities and access. It brings access requests and approvals, account lifecycle management, roles and permissions, and activity auditing into one product.
The system is used by employees, managers, administrators, and information security teams. Each role has different responsibilities, but all workflows follow the same principle: access must be granted to the right person, for the right system, with clear ownership, justification, and a complete history of changes.
The product evolved from an existing enterprise platform. The challenge was not only to design new features, but also to reorganize complex legacy workflows, unify inconsistent patterns, and create a scalable foundation that could support future functionality without introducing new exceptions.
Year
2025
Type
Enterprise Identity & Access Management platform
Users
Employees, managers, IT/security teams, contractors
Role
Product design, research, design system
Status
Desktop design delivered and approved
Result
Scalable system with consistent workflows
Product context
The product lacked a unified design system, resulting in inconsistent interface patterns across the platform.
Design mockups often diverged from the implemented product, while the homepage showed only a small part of the product.
The existing workflow also did not support creating and processing requests for different user roles. In addition, there was no structured documentation system, making product development and maintenance more difficult.
The system is modular. New features reuse existing blocks, so the product grows without a full redesign.
I started by auditing the existing product and comparing the designs with the implemented interface. This revealed inconsistent components, gaps in role-based request workflows, missing documentation, and major differences between design and development.
I reorganized the information architecture, redesigned request flows for different roles, and updated the homepage to represent the product’s broader functionality.
I then reviewed every product section and prepared detailed development specifications describing interface patterns, states, and behavior. In parallel, I unified reusable blocks and created a design system with clear layout rules for both designers and developers.
Modular and flexible. The design system uses a neutral palette, while emphasis comes from hierarchy, shape, and spacing rather than excessive color. Reusable components and universal input blocks adapt to different roles and workflows, allowing new functionality to be added without redesigning the product from scratch.
Problem
Solution
Process
Design system
Required documents, validity periods, and upload states are handled directly within the access request.
Employee attributes and dynamic conditions define when access is granted automatically.
Nested roles can be updated without losing the overall access structure.
A data-dense account view brings identities, systems, statuses, and access lifecycle details into one workspace.
Made on
Tilda