Notifications
The bell in the console header and its toasts — what its count means, how the list behaves, which events notify whom, where each notification opens, and how long notifications last
The bell near the right-hand end of the console header tells you what is waiting on you: an agent's proposal to approve, a message an agent sent you, a team its budget has stopped, a new escalation ticket, a directory sync that has started failing, or an agent suggested as a template. Without it, each of these shows only on the page it lives on — you would see it only if you happened to open that page.
Notifications are delivered in the console only. AskRAI sends no email, Teams message or push notification for them, and there are no per-person preferences: you receive every notification addressed to you.
The bell and its count
The badge on the bell counts your unread notifications, capped at 99+. Screen readers announce the button as Notifications, 3 unread when three are waiting, and as Notifications when nothing is unread.
The count is not pushed to you the moment something happens. It refreshes every 30 seconds while the console is visible in your browser, whenever you return to the console window, and each time you open the list — so a new notification can take up to half a minute to appear.
Toasts for messages and approvals
A message an agent sends you, and a proposal you can decide, also pop up as a toast at the bottom of the screen, wherever you are in the console — on another project's page, in Admin, or on the Dashboard:
| Toast | Says |
|---|---|
| Message from Release Writer | The start of the message, up to 140 characters |
| Approval requested | The agent's name and what it proposes, such as Release Writer: Publish the v2.4 release notes (+1 more) |
Click Open on a toast to do what clicking its item in the list does: it marks the notification read and opens the project's Interactions tab. A toast leaves after a few seconds; the notification stays in the list either way. Press Alt+T to move to the toasts with the keyboard, which keeps them on screen while you are there.
A toast arrives with the count, so up to 30 seconds after the agent's beat. Each item toasts once in each browser tab open when it arrives: what the list already held when you opened the console, and anything you have read, raises none. Other notifications appear in the list alone.
Reading your notifications
Click the bell to open the Notifications list.
| Element | What it does |
|---|---|
| The list | Shows your notifications newest first, 20 at a time |
| Load More | Appears at the bottom while older notifications remain, and brings in the next 20 |
| An item | Shows its title, any detail beneath it, and how long ago it was raised. An unread item is marked as unread, both on screen and for screen readers |
| Clicking an item | Marks it read, closes the list, and takes you to the page where the thing it names is waiting — see What notifies you |
| Mark all read | Marks every unread notification of yours read, including ones further down that you have not loaded. Disabled when nothing is unread |
| You're all caught up | Shown in place of the list when you have no notifications |
Read state is yours alone. The same event often notifies several people, and opening or marking yours read changes nothing in theirs.
What notifies you
These events raise a notification; a hosted tool server's notices are described with Tools. The title names who or what acted and what happened; the detail beneath it says what it was.
| Notification | Raised when | Title and detail | Opens |
|---|---|---|---|
| Message | An agent sends you a message: one on Full autonomy sends it in a beat, and one on Manual approval once its proposal to send it is approved | Message from Release Writer, with the message beneath | The project's Interactions tab, where the message is |
| Proposal | A beat of an agent on Manual approval autonomy proposes one or more actions | Beacon needs approval, with the first proposal's summary beneath, followed by (+2 more) when the beat proposed three | The project's Interactions tab, whose Pending approvals card sits at the top |
| Budget stop | A project exhausts its budget and its whole team is stopped, or one agent is stopped by its own spend cap | Onboarding Automation: team stopped — budget exhausted, or Onboarding Automation: Atlas stopped — budget exhausted for one agent | The project's Budget tab |
| Escalation ticket | An escalation rule opens a ticket | Escalation ticket opened, with the ticket's title — or, failing that, its question — beneath | The Tickets page |
| Directory sync failed | A Google Workspace directory sync fails when the run before it did not | Directory sync failed, with the error beneath | Admin → Directory Sync |
| Template suggested | Someone with Write access to a project suggests one of its agents as a template | Contract Reviewer is suggested as a template, with who suggested it, from which project, and their note beneath | Admin → Agent templates → Suggestions |
| Suggestion decided | A template admin approves or rejects your suggestion | Your suggestion of Contract Reviewer was approved, with the template and version it was published as; or …was rejected, with the reason beneath | The template, if you may manage agent templates; otherwise the project's Team tab |
Opening a message, proposal or budget-stop notification selects that project on the Projects plane and opens the tab. If the project belongs to an organization other than the active one, the console first switches the active organization to the project's own. If the project can no longer be opened, the Projects plane opens as it normally would.
- A ticket notification opens the Tickets page, not the ticket. Pick the ticket out of the list by the title the notification showed.
- A budget stop for one agent opens the project's Budget tab. The agent's own cap, and its Resume, are on the agent's Budget tab — open the agent from the Team tab.
Who receives a notification
A notification goes to the people expected to act on it, not to everyone who could open the page it points to. Everyone a project is shared with can open it, but you see only the notifications addressed to you.
| Notification | Who receives it |
|---|---|
| Message | The person the agent addressed it to, if they can open the project. A message to the whole team, or to another agent, notifies nobody |
| Proposal, Budget stop | The people on the project's Team tab who hold Write access or above on it. When none does, the people its Admin grants name — each person granted Admin, and the members of each active group granted Admin. When those name nobody, the people its organization's Admin grants name, in the same way. When those name nobody too, the tenant's Platform Admins, so an agent-only team's proposals still reach someone. Everyone notified can decide a proposal, and so can anyone else with Write access to the project |
| Escalation ticket | Everyone who holds the permission to manage Escalation Rules |
| Directory sync failed | Everyone who holds the permission to manage Directory Sync |
| Template suggested | Everyone who holds the permission to manage Agent templates |
| Suggestion decided | The person who made the suggestion — unless they decided it themselves |
A Platform Admin holds every permission that opens Admin, an Auditor only the one to read the Change Log, a Member none, and a role you build the ones you chose for it. So the ticket, directory-sync and template-suggestion notifications go to the tenant's Platform Admins and to whoever holds a role granting that permission — whether the role was assigned to them directly or through a group.
A Platform Admin does not receive a project's notifications when someone on its team holds Write access or above, or its or its organization's Admin grants name anyone, though they can still approve or reject its proposals. Holding Administer every organization or Administer every project gives Admin on every project but brings none of its notifications. To hear about such a project's proposals and budget stops, add yourself to its Team tab: a Platform Admin, like a holder of either permission, holds Admin on every project, so you qualify.
Recipients are decided when the event happens, not when you look:
- Joining later brings nothing from before. A person added to a project, or made a Platform Admin, receives only the notifications raised from then on.
- Leaving the team takes nothing away. A person removed from a project's team, or whose access to it is lowered but not removed, keeps what they already received until it expires, though they decide its proposals only while they hold Write access or above.
- Losing access hides a project's notifications. A message, proposal or budget-stop notification shows, counts and toasts only while you can still open its project. If the project is no longer shared with you, they leave your list and count, and come back if it is shared with you again before they expire.
- One event notifies at most 500 people. In a tenant with more recipients than that for a single event, some of them do not receive it.
One notification per event
Each event notifies you once, however many times AskRAI comes across it:
- Messages — one per message.
- Proposals — one per agent beat. A beat that proposes several actions raises a single notification, naming the first and counting the rest.
- Budget stops — one per stop. A team or agent that stays stopped raises nothing further. One that is restarted and runs out again raises a new notification.
- Escalation tickets — one per ticket.
- Template suggestions — one when suggested, one when decided.
- Directory sync failures — one per change in what failed. A sync that fails notifies you, and further failures of the same kind do not: one you can fix (Google refused the connection), or one on AskRAI's side. A failure of the other kind notifies you again, so a refusal that follows a failure on AskRAI's side always reaches you. Once a sync succeeds, the connection is disconnected, or one of its connection fields is saved with a new value, the next failure notifies you again. Changing only Real-time user sync does not count.
How long notifications last
Notifications are kept for 30 days, read or unread, and then disappear from the list. Only the notification goes: the proposal, ticket, budget state or sync status it pointed to stays on its own page. Deleting a project deletes its notifications with it.
Nothing clears a notification when someone deals with its source. If a colleague approves or rejects a proposal before you open yours, your notification stays unread, and opening it lands on a Pending approvals card that no longer lists that proposal.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| You receive nothing for a project's proposals or budget stops | You are not on the project's Team tab, or you hold less than Write access on it. Admin grantees, the organization's Admins and Platform Admins receive a project's notifications only when nobody on its team holds Write or above | Ask one of the project's Admins to share it with you at Write if you hold less, then someone with Write to add you to its Team tab. Notifications raised before you joined do not appear |
| An agent acts but never raises a proposal notification | The agent is not on Manual approval — Full autonomy agents apply their actions directly, so there is nothing to approve | Set its autonomy on its Heartbeat tab if you want to review its actions first |
| A proposal notification opens on a Pending approvals card without its proposals | Someone else with Write access to the project approved or rejected them first, the agent that raised them was deleted — which rejects them — or the run was cleared with Reset, which deletes proposals but leaves their notifications | Nothing to approve — the task board and the Activity tab show what a person decided, unless Reset cleared those too. A deleted agent's proposals leave no entry there: the agent is simply gone from the Team tab |
| A budget notification names one agent, but the project's Budget tab shows budget left | That agent was stopped by its own spend cap, not by the project budget | Raise or clear the cap on the agent's Budget tab, then press Resume there |
| A Member receives no ticket or directory-sync notifications | These go to the holders of Manage escalation rules and Manage directory sync | Expected. Assign that person a role holding the permission under Access if they should receive them |
| A directory sync keeps failing but only one notification arrived | A run of failures of one kind notifies once | Open Admin → Directory Sync and read the error on the card. If it names what Google refused, fix the connection, then click Sync now. If it says the sync failed on our side, there is nothing to fix on your side: the next scheduled sync runs again |
| No toast appeared for a notification in the list | Only messages and approvals toast, and only those that arrive while the console is open. What the list held when you opened the console raises none, nor does one already read | Expected — open it from the list |
| A new notification has not appeared yet | The count refreshes every 30 seconds, not instantly | Open the list, or switch back to the console window, to refresh it at once |
| Opening a notification changed the active organization | The project belongs to a different organization from the one that was active | Expected — switch back with the header org switcher when you are done |
| An older notification is gone | Notifications expire 30 days after they are raised | Its source — the proposal, ticket, budget or sync status — is still on its own page |
Related pages
- Interactions — the Pending approvals card a proposal notification opens
- Projects — the Budget tab a budget-stop notification opens, and how to recover from a stop
- Team — the people who receive a project's notifications, and each agent's own spend cap
- Tickets — the escalation tickets that notify the holders of Manage escalation rules
- Directory Sync — the Google Workspace sync whose failures notify the holders of Manage directory sync
- Access — who holds the Platform Admin role