Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Notifications

On Advanced → 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.

The page opens only for a role that can manage notifications. 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​

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.

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. Delivered only when a default or the person's own preference names a channel
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

Access-review events are sent by email only, whatever a default or a supervisor's preference says. See What Managers Are Told.

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 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 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.