See what lands in the inbox

Which events each module sends, and where each notification opens.

In short

Each module sends a notification only when something concerns you personally. This guide lists what each module sends and what opens when you click it. Use it when you wonder why a notification arrived, or why one did not.

Before you start

Who: anyone signed in.
Plan: none.
First: nothing. A notification is addressed to a person, not a team.

Events by module

Steps

Find the module in the table above, under "Module".
Check that the event concerns you directly. It must be assigned to you, mention you, or be about something you own, watch or manage.
If the module's notifications are missing altogether, open "Notification settings" in the Inbox page's … menu and check that the module is not set to Muted.

Result: you know whether a notification should have reached you, and where it opens.

Good to know

A notification is addressed to a person, not a team. If a run failed and you were not among the people responsible for that request in that environment, it does not reach you.
When something closes to you - a share removed, a team left, a role changed, a pause - what your inbox said about it leaves at once.
Some rows carry their own buttons. A request to turn a module on offers "Turn it on", "Open members" and "Dismiss". A failure that started after a change offers "Open the change" and "Create bug".
Chat writes an inbox row only while you are away from Chat, and only when the conversation's own level (All messages, Mentions only or Muted) lets it.

If something goes wrong

A whole module never notifies you: it is set to Muted, or the module is switched off for you in this workspace.
A failed run did not notify you: the environment is not Preprod or Production, or you are not responsible for that request there.
A notification opens a page that says it is not available: the record was deleted or your access ended.

/help/inbox/inbox
/help/inbox/inbox-settings
/help/chat/presence-and-notifications