Identity access management
A cleanup and redesign of the platform’s tools-and-permissions access management — shorter, consistent names, a leaner catalog, and clearer permission states for faster, safer access assignment.
Research & insights
- Tool and permission names were too long and inconsistent, which slowed search and assignment.
- The catalog still held outdated, unused tools and permissions.
- Users didn’t understand the basic permission, or how the “all / partial” selection actually worked.
Goals
- Speed up search and assignment with short, familiar names.
- Remove obsolete tools and permissions.
- Make the basic-permission behavior and checkbox states clearer.
- Standardize naming and drop redundant words like “Can.”
Process
- Interviewed users to learn which tools and permissions are actually used.
- Audited the lists across staging and production.
- Built and aligned a table of updated names and statuses for every element.
- Set naming conventions and clarified how the basic permission behaves.
- Tested on staging before rolling changes out to production.
Solutions
- Renamed tools to concise, familiar abbreviations (e.g. Billing Back Office → Billing BO, Raid Game Back Office → Raid GBO, Geo LiveOps → RTS LiveOps).
- Removed unused tools — Plarium Flight, Promotion Tool, Exiles Game Back Office, UDD Tool, VIP CRM and others — and deleted obsolete permissions and audiences.
- Renamed production permissions to include “on production,” dropped “Can,” and kept the action verb only (e.g. Give Offers → Give Offers on production).
- Clarified the basic permission in the UI: with only the basic permission selected the checkbox shows a “partial” state; with everything selected, “all.”
- Tested every change on staging, then applied to production with no access loss for users.
Outcome
- Faster search and assignment thanks to simplified names.
- A cleaner, more maintainable tool with irrelevant items removed.
- A standardized naming style across all tools.
- Users now read the basic-permission behavior and checkbox states clearly.
- Better usability and maintainability for both users and admins.
3 screens
Strategy — coming soon
Personas — coming soon
UX artifacts — coming soon
Collaboration
- Product Coordinator: brought user-reported tasks and problems to the team; together we analyzed them, set priorities and timelines, and clarified details before starting — and stayed aligned through solution reviews.
- Design Team Lead: reviewed my work against the overall concept and guidelines, helped me understand the product and its context, and we discussed and approved decisions to keep them consistent with the design system.
- Developers: walked the team through user flows and interactions, discussed technical constraints and opportunities, adjusted designs accordingly, and verified the build against the intended design.
- QA: worked with QA through testing to confirm the implementation matched the design specs and user scenarios, flagging UI/UX issues and supporting fixes.
Impact
The changes shipped to production with zero access loss for existing users — a hard constraint that shaped every decision in the process.
- Search speed improved: shorter, consistent names reduced the time to find and assign the right permission from several attempts to one
- Support requests related to permission confusion dropped after the basic-permission behavior was clarified in the UI
- Onboarding new admins became faster — the catalog no longer required tribal knowledge about which tools were active or what naming patterns to expect
- Catalog maintenance overhead reduced: with obsolete entries removed and conventions established, new additions follow a clear pattern rather than diverging further
- The audit trail of naming decisions and staging test results became a model for future IAM changes — the process itself was a deliverable
Next project
Atlas