Change password
Display current provider rules, verify the user, submit the change, and return the authoritative provider result.
MYID Manage
Routine identity work without a routine helpdesk ticket.
Employees can manage the identity actions their company approves while the server applies provider policy, step up verification, tenant capability rules, audit evidence, and truthful result handling.
Functions a company can enable.
Password recovery
Use approved verification and recovery paths without putting provider secrets or service credentials in the mobile app.
Profile updates
Allow only company approved attributes. Phone changes can require OTP verification before persistence.
MFA factors
Show supported factors and allow approved enrollment, disable, or removal actions when provider APIs permit them.
Directory unlock
Attempt a live unlock and confirm the resulting directory state, even when cached status previously appeared healthy.
Manager approvals
Route assigned recovery approvals to authorized managers with a clear action history and without exposing secrets.
Past activity
Present recent identity and security activity that the server is authorized to associate with the signed in user.
Device evidence
Show supported device information and health signals without turning missing provider data into a false failure.
Profile photo cache
Display a locally cached image immediately and refresh it through a separate background process outside the main sync.
Available when the company allows it.
Manage uses tenant capability information so the screen reflects what each company supports. Cached capability state is shown immediately and can refresh silently. Navigating away from the screen should not disable an allowed function.
- Tenant capability state persisted with company context
- Unavailable providers kept separate from disabled policy
- Readiness testing before onboarding material is issued
- Support route and branding supplied by the company
Do not call a timeout a failure without checking.
Identity providers and directories can apply an action before the response reaches the app. MYID can follow a delayed result with a status confirmation and can distinguish success, pending, provider failure, policy denial, and unavailable evidence.
- Correlation and duration for support investigation
- Provider specific error attribution
- Safe retry behavior for idempotent actions
- Visible freshness for cached status
Step by step
A sensitive action remains controlled from start to result.
1. Check policyConfirm that the tenant and provider allow the requested function.
2. Verify userApply biometric, OTP, password, or provider verification as configured.
3. Call providerSend the action through the server using approved credentials and permissions.
4. Record resultReturn truthful state and create audit evidence with capture boundaries.
Proof that identity self service can change the helpdesk.
IBM reports that Askari Bank worked with SPS to implement self service password reset and IBM Verify. Published results include a 75 percent reduction in help desk time for password issues and 80 percent staff adoption.
That outcome belongs to the documented deployment and is not a guarantee for another customer.
Test every enabled action before broad use.
Customers should validate real provider permissions, a locked and already unlocked directory account, password rules, factor behavior, profile field policy, support routes, audit evidence, timeout recovery, and rollback before production approval.