> ## Documentation Index > Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Notifications and the inbox > The member who started a session is told when it waits on them, opens a pull request or fails, in the Inbox and, as they choose, with a pop-up, a sound or a browser notification while Scaling is open. Scaling tells the member who dispatched a session when it needs them, opens a pull request or fails. You are told while Scaling is open in a browser tab. If no tab is open, what you missed waits in your Inbox until you next open Scaling. There is no email. The Inbox is the second item down the left-hand side, above **Sessions**. It is the only thing in the product called an inbox: the list of your organisation's sessions is **Sessions**. ## What you are told A session has a dispatcher, the member it belongs to: * the member who started it in Scaling, or * the member whose assignment of a Linear issue started it, when Scaling matched that Linear user to a member of your organisation. The dispatcher gets one notification when the session: * **Waits on you**, for any of the reasons [Sessions waiting on you come first](https://docs.scaling.cloud/guides/starting-and-following-a-session.md#sessions-waiting-on-you-come-first) lists. * **Publishes a pull request.** * **Fails.** Nobody else in the organisation is told about it, unless they chose to hear about sessions in projects they work on (see [Choosing what reaches you](#choosing-what-reaches-you)). The **Sessions** list still shows everyone's sessions, and the **waiting in org** count beside it still counts every session waiting on a person in your organisation. Who is told is worked out when the thing happens, not when the session started. A member who has left the organisation by the time a session fails is not told, and nobody else is told in their place. A session that is waiting on a person with nobody to tell says so at the top of its own page, so you know to look at it yourself. ## Waits only an admin can clear Three waits can only be cleared by an admin of your organisation: * your Anthropic key is missing or was refused, * a usage cap was reached, * a brokered secret needs to be allowed. For these, the dispatcher is told as usual, and the notification says that an admin must act. It also says when the session will end if nobody acts. The time carries its date unless that is today. For a session that is still working, that is when its environment reaches its time limit. For one that is idle, it is as long as your organisation lets an idle session live, 7 days unless an admin chose otherwise in [General settings](https://docs.scaling.cloud/guides/your-organisation.md#how-long-an-idle-session-lives). Every admin of the organisation gets the same wait in their Inbox. They get no pop-up for it, because it is not theirs unless they are the dispatcher. An admin who is also the dispatcher is told as the dispatcher, once. ## While Scaling is open You are told only while Scaling is open in a browser tab. In any open tab, a small pop-up appears when a session you dispatched needs you, and the count beside **Inbox** goes up. A tab shows only the organisation it is acting in, so a notification from another organisation of yours does not pop up there; it is in that organisation's Inbox. A sound and a browser notification, if you turn them on, also only reach you while a Scaling tab is open; nothing reaches you when every tab is closed. > [!NOTE] > > Closing the last Scaling tab means you are not told until you open Scaling again. Whatever > happened in the meantime is in your Inbox, newest first. The same two counts are in every open tab, and they update on their own within a few seconds. In the tab where you reply, approve, stop a session or replace the key, both counts change at once. There is nothing to refresh. ## Choosing what reaches you Open **Notifications** under **Personal** in settings. The page has three parts. ### Who you hear about Choose one: * **Sessions I dispatched** is the default. * **Also anyone's session in projects I work on.** A project you work on is one where you dispatched a session in the last 30 days. With the second choice, the page lists the projects that count right now ("Covers acme/api and acme/web."), or says "You have not dispatched a session in the last 30 days, so this adds nothing yet." A project drops off 30 days after your last session in it. You are then told about other members' sessions in those projects as well as your own. Switching back to **Sessions I dispatched** stops new notifications about other members' sessions. It does not remove what is already in your Inbox. A note on the page says the same of **The Waiting in org count**: it counts every session waiting in your organisation, whatever you choose here. ### Events and channels A table lists three events, **Waiting on you**, **Published** and **Failed**, against three ways of being told: * **In-app** is the pop-up. * **Sound** plays a short chime. * **Browser** shows a notification from your browser. Sound and Browser need an open Scaling tab. Neither reaches you when every Scaling tab is closed. Until you change them, the defaults are: | Event | In-app | Sound | Browser | | - | - | - | - | | Waiting on you | On | On | On | | Published | On | Off | Off | | Failed | On | Off | On | Every notification lands in your Inbox, whatever you tick. Nothing reaches you through a channel you have not ticked for that event, including for sessions of other members in your projects. Admins also see a **Waits only an admin can clear** row. Those waits stay in the Inbox, with no pop-up, sound or browser notification. A note under the table repeats that **Sound** and **Browser** reach you only in an open Scaling tab, and that **In-app** is the pop-up in an open tab. Each change saves as you make it, and a message confirms it ("Published by In-app saved"). If a change does not save, the box goes back to what it was and the page says "That did not save. Try again." ### Browser notifications on this device Until you allow them, the page shows "Browser notifications need your permission" and the **Browser** column is off. Press **Allow on this device** and answer your browser's question. Each browser asks separately, so allowing notifications on your laptop does not allow them on your phone. If you blocked notifications for Scaling, the page says "Browser notifications are blocked on this device" and the **Browser** column stays off. To allow them again, open this site's settings in your browser, set **Notifications** to **Allow**, then come back. In a browser that cannot show notifications at all, the page says so and the **Browser** column stays off. ## Reading your Inbox Choose **Inbox** in the list down the left. Each notification names the session, says what happened, and says when. * **All** shows every notification, and **Unread** shows the ones you have not opened. * **Mark all read** is at the top. * **Opening a notification marks it read** and takes you to the session. There is no separate button to mark one read. * **Mark unread** is in the menu on the right of each row, for a notification you want to come back to. * A notification for a wait says **Still waiting on you** for as long as the session is waiting, even after you have read it. * Once the wait is cleared, the notification says who cleared it and how: a reply, in Scaling or in Linear, a click such as approving a plan, or an admin's fix. Whether you have read it is separate from whether it is still waiting. With the Inbox open, **J** moves down the list and **K** moves up. Press **G**, let go, then press **I** to open the Inbox from any screen. None of these keys does anything while you are typing in a field. Notifications leave your Inbox after 90 days, whether you have read them or not, and they stop counting as unread at the same time. Each organisation has its own Inbox. You see only the notifications and the count of the organisation you are acting in, and switching organisation shows the other one's. ## When the connection drops If your tab loses its connection to Scaling, the Inbox count and the **waiting in org** count both say **Reconnecting**, and so does the Inbox itself. An Inbox that is reconnecting is not an empty Inbox: what is shown may be out of date until the connection is back, and notifications that arrived meanwhile appear as soon as it is. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.