How the Supervisor App Works
Supervisors approve agent actions in the HYPR mobile app. This page sets out how the app works with your HYPR AgentPass™ gateway: how supervisors get it, how it signs in, how long a sign-in lasts, what its notifications carry and how a supervisor's access on the phone ends. Each section links to the page where you configure that part.
Getting the App
How a supervisor gets the app depends on the phone:
- Getting the HYPR App on iOS
- Signing and Deploying Your AgentPass App on iOS, for your mobile build and deployment team
- Getting the HYPR App on Android
How Supervisors Sign In
The app signs in to the gateway with the supervisor's passkey, which the phone unlocks with the supervisor's face, fingerprint or PIN.
Passkeys are enrolled through your HYPR tenant, which you connect to the gateway once. See Connecting to Your HYPR Tenant and Setting Up Your Approval Passkey.
How Long a Sign-In Lasts
A passkey sign-in gives the app two credentials.
| Credential | Lifetime | Behavior |
|---|---|---|
| Access token | 1 hour | Renewed with the refresh token |
| Refresh token | 30 days | Works once. Each renewal replaces it with a new refresh token, valid for another 30 days |
- After 30 days without a renewal, the supervisor signs in again with their passkey.
- A refresh token presented a second time is refused, and the gateway logs it as a possible stolen token.
- When the app signs out, the gateway revokes its refresh token.
What Notifications Carry
You set up push delivery on the Notifications page. Each notification carries a title and text, which the phone shows. It also carries the event type, the item the notification refers to, its urgency, when the event happened and the supervisor's email address.
For example:
| Event | Title | Text |
|---|---|---|
approval.created, for a held request | Approval requested | <agent> is waiting on your approval. |
approval.created, for a connector sign-in | Sign-in needed | Re-authenticate <connector> so AgentPass can finish the task. |
automation.run-failed | Automation failed | The automation's name, and up to the first 120 characters of the reason it failed |
connector.upstream-unauthorized | Connector authorization expired | Re-authentication needed for <connector>. |
agentcore.reply-ready | <agent> replied | Up to the first 120 characters of the reply, or Your agent has a message waiting. |
A held-request notification names the agent, but carries nothing from the request itself.
How the Gateway Recognizes the App
Under Mobile App Associations, you enter the identifiers of the HYPR apps your supervisors use. See Associate the Mobile Apps.
From these values, the gateway publishes the standard files that iOS and Android read to decide which apps your gateway's address trusts:
/.well-known/apple-app-site-associationlists the iOS App IDs./.well-known/assetlinks.jsonlists the Android Package name with its Signing-cert SHA-256 fingerprints. It needs both.
Until you set them, the files list no app.
Which Passkeys Can Approve
Passkey approval policy decides which passkeys may approve an agent action, for example only passkeys enrolled from the HYPR mobile app. See Decide Which Passkeys Count.
Ending Access on the Phone
| When | What to do | Where it is covered |
|---|---|---|
| A supervisor loses their phone | The supervisor enrolls a passkey on their new device, and deletes the one belonging to the lost phone | Replace a Lost Phone |
| A person leaves your organization | An administrator offboards them. Offboarding expires every refresh token the person's phones hold, so the app cannot renew its sign-in | Offboard a Person |
Related
- Security Controls — the controls AgentPass applies across agents, approvals and data
- Approving and Denying Agent Actions — what the supervisor sees in the app
- Notifications — push delivery, event defaults and test pushes