Mobile UX · Admin & Security Tooling

ID PAM Mobile App

A case study built around ID PAM, an example privileged-access mobile app — starting from what admins actually did with it: read one-time codes constantly, approve requests reluctantly, never manage passwords on mobile at all.

Scope

Offline Token (existing, restyled and promoted to Home), Approval Management (existing, streamlined), Password Manager (new) — one visual system, two of the three screens admin-only.

Method

User interviews → competitive audit → structural wireframe → moderated usability testing → hi-fi exploration → final screens.

This page

Walks the case study end to end.

For NDA reasons, the interface shown here was rebuilt from scratch with Claude and Figma Make — it carries the original app's logic but isn't a direct copy, in flow or in visuals. Identifying details — product name, participant names, hostnames, account labels — have been changed throughout.
Offline Token list with favorited tokens starred
Offline Token
Approval Management list with pending requests
Approval Management
Password Manager Show Password modal
Password Manager
01

Overview

ID PAM is an example of a mobile privileged-access app already in daily use, already carrying design debt. Interviews with people who use apps like this turned up a mismatch: by far the most-used part of the app was Offline Token — the six-digit MFA code — yet it sat a tap behind the home screen, styled like the rest of the app had moved on without it.

That finding set the priority order. Offline Token moved to the home screen and got restyled first. Approval Management — accepting or rejecting a pending request — got lighter changes to remove friction found in wireframing and testing. Password Manager — revealing or resetting a vaulted credential from the phone — didn't exist before; it's designed here as a new feature.

02

What each surface does now

Each surface started somewhere different — one already the most-used screen, one live but clunky, one that didn't exist yet. All three share one visual language: app bar, session strip, scrollable card list.

Offline TokenExisting · restyled
Read a rotating six-digit code, favorite a token, add or scan one manually — now on the home screen, not a step behind it.
Approval ManagementExisting · streamlined
Accept or reject Connection, Start, and Command requests — several steps got lighter along the way.
Password ManagerNew
Reveal or reset a vaulted credential. Each account shows what's required to unlock it, and a Show Password request's outcome comes back as a status tag on the card.
03

Where the market already stands

A quick audit of four mobile apps in the same space — MFA and privileged-access companions — found no single one covering all three surfaces this case works on.

AppStrengthsGap relative to this case
01Duo MobileOne-tap push approve/deny, plus TOTP passcodes as a fallback — fast, single-purpose interface.No password or credential surface at all — the app's documented scope is MFA only.
02Microsoft AuthenticatorOTP codes plus push sign-in approval — one of the most widely deployed authenticator apps.Briefly paired OTP with password autofill, then Microsoft discontinued it in 2025 and moved passwords to Edge — even a major vendor pulled back from combining the two in one app.
03Okta VerifyPush approval, one of the most widely deployed authenticator apps.Documented as authentication-only — nothing analogous to Approval Management or a credential vault.
04CyberArk Mobile (now Idira)Closest domain match — its dual-control approval feature lets approvers swipe to confirm or reject PAM account-access requests from the phone.Documented scope stops at approving the request — what happens next isn't detailed in the docs.

No competitor pairs token access, approval, and credential reveal in one mobile surface — the case for designing Password Manager as a phone-native screen rather than leaving it to the web console.

04

Who uses it

Not every screen is open to everyone. Offline Token is how anyone with the app authenticates. Approval Management and Password Manager are restricted to approvers; an end user submits access requests elsewhere, and every action is audited from a separate web console, not on mobile. Letting end users submit that request from their own phone is the next direction worth exploring.

End user

Offline Token Approval Management Password Manager

Authenticates with their own tokens. Submits access requests through a different channel, not this app.

Approver / admin

Offline Token Approval Management Password Manager

Reviews requests and reveals credentials from the phone — the only role these two screens are designed for.

Auditor

Offline Token Approval Management Password Manager

Reviews every action from a separate web console. No mobile surface at all today.

Persona · Offline Token

The everyday user

General employee, day-to-day system access
  • Mobile use starts and ends with Offline Token — reads a rotating code several times a day
  • Wants the code fast, with nothing to configure; doesn't think of this as a security tool
  • Where they got stuck: registering a new token and finding it again afterward (testing task 2)
Persona · Approver / admin

The approver

IT/ops or security admin with approval authority
  • Uses all three surfaces — tokens, approvals, and the vault — often between meetings, not at a desk
  • Needs to triage a queue fast and trust the outcome enough not to double-check on a laptop
  • Where they got stuck: the filter panel, and approving a specific request by ID (testing tasks 1 & 3)
05

A structural wireframe, before any visual style

Before touching color or type, each change went through a low-fidelity structural wireframe in Figma — testing whether a filter actually filters, a step still makes sense as a sheet instead of a page, an access-requirement tag says enough on its own.

Offline Token — register & list
Wireframe flow: Offline Token list, Add New Token, Enter Manually, Enter Manually filled, Token List
Add a token manually, then find it back in the list — straight from the Figma wireframe file.
Home → Approval Management
Wireframe flow: Home, Approval Management, Filter Panel, Filter Filled, Operation type, Filtered Results, Request Detail
From Home into Approval Management: filter, pick an operation type, review the filtered queue, open a request.
Password Manager
Wireframe flow: Password Manager list, Show Password confirmation, Duration, Device detail, confirmation screen
Reveal or reset a password, confirm the action, and see the result.
06

Five people, four tasks, one moderator

This round happened right after the structural wireframe, on Offline Token and Approval Management — Password Manager didn't exist yet. Each participant ran the same script: configure a connection, register and favorite a token, approve a request by ID, then log out. Tasks were scored 1 (easy) to 3 (not completed); quotes are translated from Turkish.

P1
Participant 1
3 easy · 1 with difficulty
P2
Participant 2
2 easy · 2 with difficulty
"There needs to be more breathing room between the request cards — let's open it up a bit."
P3
Participant 3
2 easy · 2 with difficulty
Seemed to think the request list stayed hidden underneath the expanded filter panel, rather than the panel sitting on top of it.
P4
Participant 4
4 / 4 tasks easy
"The circles are too big — simplifying them would help."
P5
Participant 5
3 easy · logout not recorded
"The first thing that caught my eye on Approval was the buttons — smaller would be better."
19 / 19
recorded tasks reached completion — nobody got stuck
5 of 19
finished only with visible difficulty (score 2)
4 / 5
of those difficulty scores landed on two tasks: registering a token and approving a request
PromptP1P2P3P4P5
1 · Configure a connectionEasyEasyDifficultyEasyEasy
2 · Register a token manually, set it as favoriteEasyDifficultyDifficultyEasyEasy
3 · Find & approve a pending request by IDDifficultyDifficultyEasyEasyEasy
4 · Log outEasyEasyEasyEasyNot recorded
Easy to complete
Completed with difficulty
Not recorded

Where the friction actually was

Offline Token — a newly favorited token doesn't read as "favorited" Four of five participants couldn't find the token they'd just favorited, and proposed four different fixes — a new color, a favorites section, a separate tab, a menu affordance. The real problem: the screen never signaled "this list is your favorites" at all.
"If the new token were red — a color completely outside the palette — it'd be easier to tell apart."
Approval Management — the filter goes unused, and is actively misread Three of five scrolled the full queue by eye instead of using the filter — one gave up and restarted from Home. A recurring misconception: the request list seemed to hide underneath the filter sheet, instead of the sheet sitting on top.
"There needs to be more breathing room between the request cards."
Logout isn't where people expect it One participant's first reflex was to open Settings; logout wasn't there, and took a second look to find.
Reached for Settings first, before finding the actual logout control.
The structure was landing before the visual design was Independent of task performance, four of five raised the same complaint — oversized buttons, inconsistent icons, too much blue. One participant put it precisely: structure and UX were sound, the visual design still needed a pass — the gap Offline Token's restyle closes.
"The overall structure and UX are good — the visual design needs refinement."
07

What changed on the way to final

Three kinds of decision followed: promotion and style, removing steps, and designing something new.

Offline Token

Token cards moved off a secondary page and onto the home screen — the app now opens straight to the six-digit codes most sessions were for anyway.
A newly registered token gets a high-contrast NEW badge that clears once the screen is left.
Favoriting a token now fills its star in the brand accent, not just a subtle outline change.
Answers findings 1 & 4

Approval Management

Several steps that used to be their own page — picking an operation type, setting a duration — now happen in a bottom sheet without leaving the list.
Each card carries both a one-tap action for the confident case and a details chevron for anyone who wants the full picture first.
"Return to Approval Management" restores whatever filters were active — nothing resets, so a scrolled queue stays scrolled.
Answers finding 2

Password Manager

Every vault account now shows up front what it takes to unlock it — an approval policy, or nothing.
Static and dynamic secrets stay visually distinct: one button (Show) for static, two (Reset + Show) for dynamic.
New, not iterated
WireframeStructural wireframe of the token list before restyling
FinalFinal home screen with the favorite token promoted

Offline Token's promotion to Home, from structural wireframe to final screen.

WireframeStructural wireframe of the request detail screen before restyling
FinalFinal full request screen with Reject and Approve buttons

Approval Management's request detail, restyled with the one-tap Reject / Approve pattern.

08

The final screens

Captured straight from the working hi-fi prototype, not staged mockups. They carry the original app's overall logic but aren't a direct copy, in flow or in visuals: a few steps go beyond what the original interface does, partly to stay unidentifiable, partly because they were worth trying even though the original never justified the effort. Only the Offline Token screens are seen by every user — Approval Management and Password Manager stay behind approver access.

Home screen with the favorite token surfaced in a hero card
Offline TokenPromoted onto Home — the six-digit code most sessions were for anyway, not a tap behind it.
Home — favorite token surfaced
Offline Token tab with the full list of tokens, favorites starred
Offline TokenFavoriting fills the star in the brand accent — not a subtle outline anyone missed in testing.
Full list, favorites starred
Approval Management list with pending requests and history
ApprovalOne-tap Submit for the confident case; the card itself still opens for the full picture.
List — pending and history
Full request detail with Reject and Approve buttons
ApprovalReject / Approve as two unmistakable actions — nothing resolves by accident.
Full request, before deciding
Resolved request detail marked Approved
ApprovalA resolved request keeps its outcome in history — nothing is re-editable after the fact.
Resolved — status kept in history
Reset Password screen with new password fields and a logged-action warning
Password ManagerA deliberate, logged action — an explicit warning stands between the admin and a reset.
Reset — a deliberate, logged action
Sign in
Login screen with username, password, and biometric options
Final
Sign in — password or biometric
Offline Token
Home screen with the favorite token surfaced in a hero card
Final
Home — favorite token surfaced
Offline Token tab with the full list of tokens, favorites starred
Final
Full list, favorites starred
Add New Token screen with import, register, and scan options
Final
Add — import, register, or scan
Enter Manually screen with account name and secret key fields
Final
Register manually with a secret key
Approval Management
Approval Management list with pending requests and history
Final
List — pending and history
Full request detail with Reject and Approve buttons
Final
Full request, before deciding
Resolved request detail marked Approved
Final
Resolved — status kept in history
Password Manager
Password Manager account list, each account tagged by type
Final
Account list, tagged by type
Account detail with Show Password and Reset Password options
Final
Account detail — show or reset
Show Password modal with the revealed username, password and URL
Final
Password revealed
Reset Password screen with new password fields and a logged-action warning
Final
Reset — a deliberate, logged action
09

The pattern underneath

Two different hands are on these screens. The rules below — screen anatomy, when a sheet beats a full page, what earns an accent versus a status color — are mine, tested across all three flows. The exact pixels that carry them out came from Claude and Figma Make, since NDA ruled out reusing the real interface — the color and type samples document what resulted, not a palette picked screen by screen.

Screen anatomy

  • App bar + session context, identical across Offline Token, Approval Management, and Password Manager
  • Filter or search sits directly under that context, never buried in a menu
  • Every list resolves to the same card shape: status mark, title, subtext, one action
  • List and detail are the only two levels — nothing nests a third screen deep

Interaction rules

A one-tap action on the card for the confident case, a chevron for the full picture

Confirmation happens in a sheet, never a full-screen replace

PendingApproved

A resolved request keeps its outcome in history — nothing is re-editable after

Favoriting fills the accent rather than toggling a subtle outline

States & feedback

PendingApprovedRejected

Status always pairs a color with a text label — color never carries the meaning alone

RejectApprove
Approved

A resolved request drops Reject/Approve entirely rather than graying them out

RejectApprove

Reject stays outlined and quiet, Approve carries the one filled action on screen

A token's countdown ring empties as its code goes stale — read at a glance

Spacing & elevation

One shadow weight for every card; nothing stacks two levels of elevation

Context headers get a tint fill instead of a shadow, reserved for what's tappable

Icon-in-a-tinted-circle, reused for lock, account type, and status alike

A destructive action gets an inline warning ahead of the button, never a modal

Color & type, as rendered

Accent
Surface
Approved
Pending
Rejected

One accent, status color reserved and always paired with a label — Claude and Figma Make's read of the rule, not a hand-picked palette.

IBM Plex Sans — headings & UI
Approval Management
IBM Plex Mono — codes, secrets, data
482 913
10

Reflection

This case didn't start from a blank page, and it isn't finished.

It also covers a limited slice of a larger app — other features are out of scope for the same reasons as Section 08, not for lack of attention.

Early signal since shipping favors Offline Token specifically: people get to their code immediately, and surfacing the favorited token — the fix for finding 1 — is the part actually getting praised. Approval Management and Password Manager are new enough that they haven't been actively promoted or used yet, so whether the streamlining actually lands is still open, not a settled result.

Two things are still open, both about who can reach the app at all. The bigger one: only approvers can act on a request from the phone today — letting the end user submit that request from the same app is next. The smaller one: auditors still have no mobile surface, reviewing everything from a separate web console — worth exploring once the approver-facing work is further along.