Skip to main content
Version: 11.5.0

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.

ChannelShown asDelivers
PushfirebaseA notification on the recipient's registered mobile devices, through Firebase Cloud Messaging
EmailemailAn 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:

  1. Turn on Enable Firebase channel.
  2. Enter the Project ID. It is under project_id in the service-account JSON file.
  3. Paste the Service Account JSON. Once stored, it shows Configured. To paste a new one, click Replace.
  4. 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 typeSent whenSent toPlatform default
approval.createdAn agent's request is held for approval, or a connector needs the person to sign in againThe agent's supervisorPush, high urgency, locked
automation.run-failedAn automation run failsThe automation's supervisorPush, high urgency
connector.upstream-unauthorizedA connector's sign-in with its upstream service has expiredThe supervisor whose request found itPush, high urgency, locked
agentcore.reply-readyAn AWS Bedrock AgentCore agent replies in a conversationThe person in the conversationNone
user.invite-sentA person is invited to set up AgentPass, or reminded toThe invited personEmail, normal urgency
access-review.assignedA reviewer is given agents to reviewThe reviewerEmail, normal urgency
access-review.due-soonA review is close to its due dateEach reviewer with decisions leftEmail, normal urgency
access-review.overdueA review is past its due dateEach reviewer still behind, and the review's managersEmail, normal urgency
access-review.access-removedA reviewer removes access from an agentThe agent's ownerEmail, normal urgency
access-review.needs-managerA review needs something only its managers can fixThe review's managersEmail, normal urgency
security.guardrail-heldA guardrail holds an agent's sensitive action for approvalThe agent's supervisorEmail, high urgency
security.guardrail-deniedA guardrail denies an agent's sensitive actionThe agent's supervisorEmail, high urgency
security.session-hostileA session reads content that the gateway judges hostileThe agent's supervisorEmail, high urgency
security.tool-changedA connector's tool changes after it was approvedNo one directly. The change is raised on the Guardrails Alerts pageEmail, high urgency
security.session-supervisor-attestThe session investigator pauses a session, and asks the agent's supervisor to attest before it resumesThe agent's supervisorNone
security.session-escalatedThe session investigator pauses a session, and routes the decision to resume it to your security teamThe SOC distribution list, or the address that Escalate a pause to namesNone
security.session-pausedThe session investigator ends a session for security reviewWhoever Escalate a pause to names: the agent's supervisor, the SOC distribution list or an addressNone
security.session-resumedA paused session resumesThe agent's owner, so they can run their last step againNone

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:

  1. Click Edit on the row.
  2. Choose the Channels. For access-review and security. events, the channel is fixed to email.
  3. Choose the Urgency: high, normal or low.
  4. Turn Locked on or off.
  5. 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.