Viktoriia ShakhnirClient Portal & Admin Console
Two platforms within one enterprise SaaS ecosystem
Overview
Client Portal & Admin Console are two interconnected products within one enterprise SaaS ecosystem. Built as a single system with a shared design language, but serving different needs for different types of users.
Client Portal
A centralized portal for clients and partners: billing, subscriptions, analytics, support, and a single entry point to all ecosystem products. Designed for both enterprise clients and partners managing multiple organizations simultaneously.
Admin Console
A multi-level role-based admin console. Higher-level admins have full access across all groups and settings, while lower-level admins manage their own scope. The platform covers user management, system configuration, and incident investigation.
My Scope
Full cycle on each module: from requirements analysis and structure definition through to wireframes and final UI. Worked across both platforms simultaneously as part of a two-designer team.
Client Portal - 7 modules. Admin Console - 8 modules.
- 1
Discovery & Analysis
Studied the client documentation, explored the domain, defined all modules and user roles across both platforms
- 2
Module Breakdown
Before starting each module completed a detailed breakdown of states, actions, role access, and edge cases
- 3
Prototypes & Iteration
Built clickable prototypes, tested the logic, iterated on complex flows before moving to UI
- 4
UI Design
Designed modules across both platforms in collaboration with the second designer
- 5
Feedback & Iterations
Iterated based on feedback from the Design Lead. Created alternative solutions when needed
Challenges
Two platforms, one design system
Two designers, two products, one design system. The risk: details diverge and the result looks like two separate products.
Solution Discussed components, patterns, and approaches throughout the process. Regular syncs and an agreement to talk through decisions before locking them in.
Dense admin interfaces
Admins need to see a lot of information and act fast - without the interface becoming cluttered with data. Everything has to be logically structured for comfortable use.
Solution Worked through each module separately: first a detailed breakdown of states, actions, and role access, then a prototype for testing. Priority on minimizing clicks to the needed action.
AI in Process
ChatGPT was used for technical research: analyzed large technical documentation, extracted key requirements, worked through technical terminology and interaction scenarios before starting design. Used for mapping complex flows to find the best solution.
Figma was used for clickable prototypes: testing UX solutions and selecting the best option before moving to UI, saving time on iterations.
Outcome
Two platforms with a unified design system and shared visual language, built to create a consistent experience across different products within one ecosystem.
This project showed me how consistency gets built in a team when working across two products at once - how important communication between designers is, and how creating shared patterns across an ecosystem directly shapes how comfortable the product feels to use.