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.
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.
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.
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.
| App | Strengths | Gap relative to this case |
|---|---|---|
| 01Duo Mobile | One-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 Authenticator | OTP 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 Verify | Push 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. |
Based on each vendor's own product documentation, current as of September 2026:
Duo Mobile — Cisco Duo ·
Microsoft Authenticator autofill changes ·
Okta Verify ·
CyberArk Mobile (now Idira), dual control approval
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.
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
Authenticates with their own tokens. Submits access requests through a different channel, not this app.
Approver / admin
Reviews requests and reveals credentials from the phone — the only role these two screens are designed for.
Auditor
Reviews every action from a separate web console. No mobile surface at all today.
The everyday user
- 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)
The approver
- 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)
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.
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.
| Prompt | P1 | P2 | P3 | P4 | P5 |
|---|---|---|---|---|---|
| 1 · Configure a connection | Easy | Easy | Difficulty | Easy | Easy |
| 2 · Register a token manually, set it as favorite | Easy | Difficulty | Difficulty | Easy | Easy |
| 3 · Find & approve a pending request by ID | Difficulty | Difficulty | Easy | Easy | Easy |
| 4 · Log out | Easy | Easy | Easy | Easy | Not recorded |
Where the friction actually was
What changed on the way to final
Three kinds of decision followed: promotion and style, removing steps, and designing something new.
Offline Token
Approval Management
Password Manager
Offline Token's promotion to Home, from structural wireframe to final screen.
Approval Management's request detail, restyled with the one-tap Reject / Approve pattern.
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.
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
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
Status always pairs a color with a text label — color never carries the meaning alone
A resolved request drops Reject/Approve entirely rather than graying them out
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
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.
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.