Action Center: One stop for every action that IT admin have to take
| Role: | Senior UX Designer |
| Team: | 1 Product Manager, Head of Design, CPO, 1 Engineering Manager, 2 Frontend Devs, 3 Backend Devs |
| Timeline: | Nov 2025 – Present (multi phase) |
| Target User: | IT Admins |
1. About Josys
Josys is a B2B SaaS management and IGA platform used by IT admins, MSP operators, and service providers. As Josys evolved its narrative from an IT SaaS management tool to a full IGA platform, admins were increasingly expected to act on a growing volume of signals — policy-triggered approvals, anomalies, manual tasks, and health-improvement opportunities.
2. Problem Statement
IT admins need to take actions across the platform, but these actions are scattered across multiple modules and screens. They must navigate through different sections and drill into specific entity details just to discover what actions are required.
3. Introducing: Action Center
A single, central hub that surfaces every action available across the Josys platform—from manual tasks to automation approval requests—aggregated from all entities (integrated/non‑integrated apps, identities, devices) in one place.
4. Information Architecture
The diagram shows how actions from each Josys module are routed into the relevant bucket, consolidating them into Action Center
As Josys expanded across policy automation, app management, and identity governance, actions relevant to admins started showing up scattered across modules. Action Center exists to pull these into a single, prioritized queue — grouped by type (anomalies, approvals, tasks, etc.) rather than by source module