Notifications
On Settings → Notifications, you switch on HYPR AgentPass™ push delivery, and set the channel and urgency every supervisor receives for each event. Approval requests reach a phone only after you configure this page.
You need Notifications: Manage to open the page. Admin has it. See Permissions by Role.
Channels
AgentPass delivers notifications on two channels.
| Channel | Shown as | Delivers |
|---|---|---|
| Push | firebase | A notification on the recipient's registered mobile devices, through Firebase Cloud Messaging |
email | An email to the recipient's address, through the sending provider on Gateway Settings |
Configure Push Delivery
Push notifications reach phones through the Firebase project that the supervisors' mobile app is registered in. The Project ID and Service Account JSON both come from that project:
- An app deployed in your organization's name uses your own Firebase project. Create a service-account key for it in Firebase, and keep the key in-house. See Signing and Deploying Your AgentPass App on iOS.
- The HYPR app pushes through HYPR's Firebase project. Confirm its values with your HYPR representative.
In the Firebase Cloud Messaging card:
- Turn on Enable Firebase channel.
- Enter the Project ID. It is under
project_idin the service-account JSON file. - Paste the Service Account JSON. Once stored, it shows Configured. To paste a new one, click Replace.
- Click Save FCM settings.
The card shows Active while the channel is on, Configured, disabled while it is off, and Not configured until a service account is stored. While it is off, notifications queue, and are delivered once you turn it back on.
Events and Recipients
Each event goes to one person, named by the event. The platform sets a default for most event types. An event type with no default is not delivered until your tenant has a default for it.
| Event type | Sent when | Sent to | Platform default |
|---|---|---|---|
approval.created | An agent's request is held for approval, or a connector needs the person to sign in again | The agent's supervisor | Push, high urgency, locked |
automation.run-failed | An automation run fails | The automation's supervisor | Push, high urgency |
connector.upstream-unauthorized | A connector's sign-in with its upstream service has expired | The supervisor whose request found it | Push, high urgency, locked |
agentcore.reply-ready | An AWS Bedrock AgentCore agent replies in a conversation | The person in the conversation | None |
user.invite-sent | A person is invited to set up AgentPass, or reminded to | The invited person | Email, normal urgency |
access-review.assigned | A reviewer is given agents to review | The reviewer | Email, normal urgency |
access-review.due-soon | A review is close to its due date | Each reviewer with decisions left | Email, normal urgency |
access-review.overdue | A review is past its due date | Each reviewer still behind, and the review's managers | Email, normal urgency |
access-review.access-removed | A reviewer removes access from an agent | The agent's owner | Email, normal urgency |
access-review.needs-manager | A review needs something only its managers can fix | The review's managers | Email, normal urgency |
security.guardrail-held | A guardrail holds an agent's sensitive action for approval | The agent's supervisor | Email, high urgency |
security.guardrail-denied | A guardrail denies an agent's sensitive action | The agent's supervisor | Email, high urgency |
security.session-hostile | A session reads content that the gateway judges hostile | The agent's supervisor | Email, high urgency |
security.tool-changed | A connector's tool changes after it was approved | No one directly. The change is raised on the Guardrails Alerts page | Email, high urgency |
security.session-supervisor-attest | The session investigator pauses a session, and asks the agent's supervisor to attest before it resumes | The agent's supervisor | None |
security.session-escalated | The session investigator pauses a session, and routes the decision to resume it to your security team | The SOC distribution list, or the address that Escalate a pause to names | None |
security.session-paused | The session investigator ends a session for security review | Whoever Escalate a pause to names: the agent's supervisor, the SOC distribution list or an address | None |
security.session-resumed | A paused session resumes | The agent's owner, so they can run their last step again | None |
Access-review events, and every event that starts with security., are sent by email only, whatever a default or a supervisor's preference says. See What Managers Are Told. Guardrail settings can also limit how many guardrail emails go out. The session investigator's escalation target and the SOC distribution list are set under Guardrails → Settings. See Alerts and Containment.
Set Event Defaults
The Event Defaults table sets the channels and urgency every supervisor receives for each event type, unless they have overridden it. It lists the event types that have a default on your tenant. An event type with no row follows the platform default.
The table edits the rows it lists. To add a default for an event type that has no row, use the notification event-defaults operation in API reference.
The table shows each event's Event Type, Channels, Urgency, Locked state and when it was Updated. To change a row:
- Click Edit on the row.
- Choose the Channels. For access-review and
security.events, the channel is fixed toemail. - Choose the Urgency:
high,normalorlow. - Turn Locked on or off.
- Click Save.
Mark an event Locked to prevent supervisor overrides. Use it for events that must not be muted, such as approval requests. On an unlocked event, a supervisor's own preference can mute it or change its channels. The urgency always comes from the default.
Send a Test Push
Under Test Push, enter a supervisor's email address, and click Send. AgentPass sends that supervisor a test approval notification. The result lists their active devices and the delivery it queued, with its status, attempts and any error. Confirm a device receives it before you rely on it for approvals.
If the result lists no active devices, the supervisor has not registered a device yet. If it lists no delivery, check the event default for approval.created, and whether the supervisor has muted it.
Related
- Connecting to Your HYPR Tenant — the passkey side of mobile approvals
- Approving and Denying Agent Actions — what the notification opens on the phone