Approvals in the Console
In the HYPR AgentPass™ console, Approvals lists the requests that need human review before an agent can proceed, and the requests already resolved. You can approve or deny a request here, and supervisors can also decide from the HYPR mobile app. See Approving and Denying Agent Actions.
Who Sees Which Requests
You need Approvals: View to open the page. Its scope decides which requests you see:
- All, as Admin, Operator, Security analyst and Auditor hold it: every request in your organization.
- Own, as Supervisor holds it: the requests raised for the agents you supervise.
Each action needs its own permission: Approvals: Grant to approve or deny, Approvals: Revoke to revoke, and Approvals: Delete to delete. Security analyst and Auditor hold only Approvals: View, so they read every request and its details, and decisions stay with the supervisors and administrators. See Permissions by Role.
Read the Page
Pick a range: Today, 3 days or 7 days. The page covers at most the last seven days. The counts show how many requests in that range are Pending, Approved, Denied, Expired and Revoked.
Click a count to filter Resolved requests to that status. Click it again to clear the filter.
Resolved requests lists each request with its agent, the request and the connector it came through, its status, who resolved it and the time. Filter by type: Onboarding, Policy, Agent or MCP OAuth. Click Clear filters to show every request again.
The page refreshes on its own every few seconds. To refresh it now, click the refresh button beside the range.
A request that reaches its timeout without an answer is Expired. An expired request is not an approval. Administrators set the timeouts under Settings › Gateway settings, on the Approvals tab.
Answer a Request
Open requests appear under Needs your attention. Each card shows the connector, the request type, the time remaining, the message, the agent and when it asked.
- Under Needs your attention, find the request.
- Click Approve or Deny. A dialog opens with the request and your identity.
- Optional: In Reason (optional), enter a message to the agent.
- Click Approve or Deny in the dialog.
- If your approval is signed, complete the passkey prompt in your browser or on your phone. When signing is optional, you can click Skip signature instead. See Sign an Approval With Your Passkey.
The request moves to Resolved requests, with its new status.
Sign an Approval With Your Passkey
Whether an approval carries your passkey signature depends on two things:
- The Require signed approvals setting, under Settings › Gateway settings, on the Passkeys (FIDO2) tab
- Whether you have enrolled a passkey that can approve
The following table shows what happens when you click Approve.
| Require signed approvals | Passkey that can approve | When you click Approve |
|---|---|---|
| Required (production) | Enrolled | Your browser or phone asks for Face ID, Touch ID or your screen-lock PIN, and the approval is signed |
| Required (production) | None | Approve is unavailable. The dialog links to enrolling a passkey |
| Optional (soak) | Enrolled | The approval is signed by default. Click Skip signature to approve without it |
| Optional (soak) | None | The approval is recorded without a signature |
An approval made without a signature shows no signer under Cryptographic evidence in its details. See Review a Request's Details. A denial is never signed. Every decision is also part of the audit trail. Click How signing works for a short summary. To enroll a passkey, see Setting Up Your Approval Passkey.
Who Can Answer
A supervisor answers the requests raised for their own agents. A role that can decide every approval, such as Admin or Operator, can deny any request, and can approve another supervisor's onboarding request. Only the supervisor a request belongs to can approve any other request. See Permissions by Role.
A request held by a spend limit goes to the limit's owner, not to the agent's supervisor. Approving it raises that person's limit for the day. Nobody can approve their own spend over a limit, except the limit's owner. See What Happens Over the Limit.
When signed approvals are required, an administrator who approves another supervisor's onboarding request signs it with their own passkey, and the signature records the administrator.
Sign-In Requests for MCP Servers
When an MCP connector needs a person to sign in to the service behind it, the request appears under Needs your attention, tagged MCP OAuth and named for the MCP server. Instead of Approve and Deny, the card offers Authenticate, which opens the service's sign-in.
A sign-in request belongs to the person it was raised for. Anyone else sees a note, in place of the button, that only that person can complete the sign-in.
The supervisor's steps are in Connecting to a Gateway MCP Connector.
Review a Request's Details
Click a row in Resolved requests to open its details. The details show the status, the type and the message, and these fields where they apply:
- Agent or Requested by, and Supervisor. For a request held by a spend limit, Owner of the limit takes the place of Supervisor
- Data classification, when a data label raised the request
- Agent ID and Connector
- Requested, and Expires while the request is open
- Access expires for an approved onboarding request, or Access expired at once it lapses
- Resolved by and Resolved at, Revoked by and Revoked at, and the Response
- Why this was held, when a guardrail held the action. It lists the action and its destination, the kind of sink, any untrusted source and any sensitive data the session read. See The Approval a Person Sees.
Under the fields, Cryptographic signature shows the signature and the request's digest. Timeline lists every event recorded for the request, such as Approval requested, Approved, Revoked and Access used. For an approved request, Cryptographic evidence shows who signed it with a passkey, when, and when HYPR verified it.
Revoke an Approval
Revoke withdraws an agent's standing access. It is offered on approved onboarding requests only, and needs Approvals: Revoke. A supervisor revokes the approvals for their own agents.
- In Resolved requests, find the approved onboarding request.
- Click Revoke in its Actions.
- Optional: Enter a reason.
- Click Yes, revoke approval.
The request then shows as Revoked, and counts toward the Revoked total. The agent's next request must onboard again, and its active channel sessions end.
Delete a Pending Request
Deleting a pending request is for Admins, through Approvals: Delete. Click the delete icon on its card, and click Yes, delete request to confirm. Deletion is permanent.
Deleting an MCP sign-in request also cancels that sign-in. A notification already sent to the phone for it no longer works.
Related
- Approving and Denying Agent Actions — the supervisor's side on the phone
- Onboarding Mode — which requests are held, and for how long
- Connecting to Your HYPR Tenant — the passkey approval policy and signed approvals
- Home — approvals as a trend across agents, connectors and supervisors