Inbox

#What the Inbox is

The Inbox in the left menu gathers everything that needs to reach you in one place. The page has two tabs: Notifications and Activity; a workspace admin also sees the Audit tab. The Today box on the right shows today's due dates and events from every workspace you belong to; a line whose time has passed reads red, and tomorrow's lines wait below. The box stays in place whichever tab you are on — even while you work in another workspace, a card whose day has come does not slip out of sight.

The Notifications tab shows what arrived from all of your workspaces in a single list, newest first and split by day. The title of each line is the name of the thing being talked about — the card, the flow or the channel — and what happened is written in the small colored label under it. If you work in more than one workspace, the line's footer also says which one it came from. The choices at the top narrow the list: All, Unread, or Awaiting action for the ones that expect something from you. Marking everything read and clearing the list also live on this page.

The bell in the sidebar is now a quick glance: at the top, under Waiting for you, sit the unread notifications that expect something from you — whatever the badge counts, those lines are there — followed by the last few pieces of news. For anything older, the Open the inbox link at the bottom of the panel brings you to this page.

The workspace menu shows the same information: in the switch list, each workspace carries the number of notifications waiting for you there. You decide which workspace to switch to by looking at the list.

The calendar also speaks up on its own: you get a notification when a task assigned to you reaches its due date, and when an event you created starts. Every morning, in the workspace's own time zone, a short summary counts the day's due dates and events; a workspace with an empty day sends none. These notifications are managed in your profile's notification preferences under Due dates and calendar. Email arrives switched off for this group; turn it on if you want it.

#What Activity is

The Activity tab gathers everything that happens in the open workspace into one list. Work done by agents, actions taken by your teammates and flow runs all flow through the same place, newest first. The list is split by day, and each group starts with Today, Yesterday or the date of that day.

The tab exists for one question: what did the agents do overnight, and where do you look in the morning. That information used to be scattered. A card's history sat in the card detail, a flow run sat on the flow page, and nothing at all told you that a file had received a new version. Activity puts them side by side.

Once a line is written it cannot be edited afterwards. It also stays where it is until its retention period runs out.

#What a line tells you

Every line says three things: the time of the action, the avatar of whoever did it, and a sentence describing what was done. When an agent writes something, the reason it gives is shown under the sentence.

An agent run is a single line. The sentence "worked on this card, updated three records, moved the card to review" describes the whole run. If every write inside a run were its own line, a run of ten steps would fill the list on its own. That detail lives under the line and opens when you ask for it.

You recognise run lines by the thin purple edge on their left. The edge means "an agent did this". If the run ended in an error the edge turns red, because at that point what matters is no longer who did the work but how it ended. The avatar of an agent connecting from outside is drawn inside a dashed ring.

#Views and filters

On the left of the filter strip are the views. One of them is always selected, and picking another one takes its place.

• Agent work. The tab opens with this one. It holds what agents did, together with automatic actions that cannot be attributed to anyone.
• My activity. Only your own actions.
• Needs attention. Runs that ended in an error, setup proposals waiting for your approval, and cards that moved into review or into an error state. This is the first place to look in the morning. A card being queued or finished does not appear here, because neither one needs you.
• Everything. Everything that happened.

On the right of the strip are the filters. These sit on top of the selected view, so more than one of them can be active at the same time.

• Who. One agent or one person. This list picks from inside the selected view: the Agent work view lists only agents, and My activity hides the filter altogether, because only your own actions are there anyway. When you switch views, a selection the new view does not offer is dropped. Each name is listed with the number of actions behind it in the selected time range.
• What. Cards, records, collections, files, channels, flow runs or agents.
• When. Today, This week or This month. The tab opens on This week.

The filter you pick turns into a chip, and the x next to it removes the filter. As soon as there is something to reset, a Clear button appears in the strip. It returns Who, What and the time range to their defaults, so the time chip goes back to This week as well. It does not touch the selected view: one of the views is always selected, so there is nothing to clear there.

The sentence under the strip states in plain words what you are looking at, for example "this week, work done by agents". You do not have to read the chips one by one and combine them in your head.

The Load older button at the end of the list adds the next page. If nothing at all matches your filter, the list does not simply go blank; a short text tells you what to try instead.

#Opening a run

Click a run line and what the run did opens underneath it. The traces it left behind come first: which record it wrote, which comment it touched, which state it moved the card into. These lines run from oldest to newest and speak the same language as the list above them, so each one carries its own time, avatar, sentence and reason.

Below them sits a line carrying the step count, for example 11 steps. Open it and you see what the agent did step by step: which tool it ran on which target and what came back. That trace arrives folded, because someone clicking a run usually asks "what happened"; the question of which tool was called is asked less often, and ten open steps would push the real answer off the screen.

The same step count is also written at the right end of the line. That is how you know there is something to open. A run that wrote nothing does not open empty; a line says so. Stand-alone actions do not open at all, because there is nothing underneath them to tell.

Open lines close when you change a filter, because the list is now made of different lines.

#The history of one item

Besides the Activity tab of the Inbox, the same list is drawn in four more places, and it speaks the same language in all of them.

• On an agent's page. When you open a saved agent you see the Definition and Activity tabs. The Activity tab lists only that agent's work, so the Who filter is not drawn there and the views come down to Everything and Needs attention.
• On a collection screen. The activity button in the header strip opens a side drawer showing what happened in that collection.
• Inside a record. Opening a record gives you the Record and Activity tabs. The second one is the history of that single record.
• In the card detail. The History tab of a card draws the same lines. More in Tasks and Kanban.

No time range is applied to the list next to an item. The answer to "why is this collection set up this way" is usually months old, and a one-week window would not show it. That is why the When chip is not drawn there; since the target is already fixed, the What filter is not drawn either. Views and Who are what remain.

#What leaves a trace

• What happens on cards: state and assignee changes, comments, checklist steps, outputs, dependencies, archiving and deletion.
• Creating a collection, adding a field and changing a field.
• Creating, updating and deleting a record. Once a record is deleted this line is all that is left of it, so the record number is kept inside the line.
• Uploading a file, a new version arriving on a file, and deleting a file.
• Opening a channel, and a message an agent posts to a channel.
• A note an agent saves to its memory, and a change to an agent's definition. The second one is the record that explains why later runs behave differently.
• A setup an agent proposes, and a setup you approve. More in Orchestrator.
• Task runs and flow runs. Even when you trigger a flow run yourself, the work is done by an agent, so the run appears on the agent side.

Messages people write in channels are not written to this list. They already live in the channel itself, and if every message were a line the timeline would turn into a second copy of the conversation.

#How long it is kept

The lines inside a run and the agent's step-by-step trace are kept for 180 days. The runs themselves and stand-alone actions are kept for 400 days. So the question "who did what" can still be answered months later, while the detail of "what happened at which step" is cleared earlier.

In on-premise installations your administrator can change these periods. More in Plans and security.