In Parallel keeps different kinds of context in different surfaces. Use the source-oriented surfaces to inspect what happened, the maintained surfaces to understand it, and AI surfaces to work with it.
The context map
Context | Where to find it | What it is for |
Workspace briefing | Open a Workspace | A focused summary of the Workspace and what needs attention. |
Workspace pages | Expanded favourite Workspace in the left navigation | Durable context such as a Charter, Objectives page, Runbook, Retro Log, or Meetings page. |
Meetings | Personal Meetings timeline and Workspace meeting links | Source conversations with Notes, optional Transcript, and Actions. |
Signals | Follow source links from Home, briefings, meeting Notes, and relevant Workspace views | Source-linked observations such as decisions, risks, and customer needs. Observation kinds define what AI should identify, and organizations can add kinds for their own needs. |
Work items | Relevant Workspace views and source links | Action Items that retain follow-through details such as state, owner, due date, and source context. |
Goals | The Workspace's goal surfaces where enabled | Intended outcomes and progress measures. |
Documents | Settings → [Workspace] → Pages → Background documents, and Chat context selection | Source files added as authorized Workspace or Chat context. |
Topics and storylines | Topics in the left navigation | Cross-cutting themes and source-linked developments. |
Daily Briefing | The Morning briefing suggestion on Home, when available | A Chat-generated, source-linked view of current priorities and what is coming next. |
Chat | Home, Ask anything, Add context (Search, Attach documents, Workspaces, and Tags), or a contextual Ask action | Conversation grounded in selected context. Navigation calls cross-cutting themes Topics, while the current context picker still says Tags. The attachment control is visible, but successful uploads remain rollout-dependent. |
Source records and maintained context
Meetings, transcripts, signals, work items, goals, and documents provide source context. Maintained Workspace pages turn selected sources into a durable narrative for people and AI.
A maintained page is not a replacement for its sources. Follow the linked meeting, signal, or document when exact wording, attribution, or evidence matters.
How context gets added
Context can enter In Parallel when:
the Recorder captures a meeting;
someone adds or updates an observation, work item, goal, page, or document;
a maintained page refreshes from its configured sources;
an authorized integration supplies meeting or notification context;
a connected AI client reads or updates a supported record over MCP;
a person adds a Workspace, document, Topic, or other item to Chat context.
Not every account exposes the same creation controls during rollout. Follow the actions visible in your Workspace rather than relying on an older navigation name.
Permissions travel with the context
Workspace access determines what you can open and what Chat or a connected AI client can retrieve. Adding something to Chat does not make it visible to someone who lacks access to the source.
When context crosses Workspaces, review membership and source permissions before sharing or running an external AI workflow.
Find the source behind an AI claim
Follow source links in Home and Workspace briefings.
Open a signal's source meeting.
Use Transcript when exact wording matters.
Open About this page to understand a maintained page's purpose, perspective, sources, and refresh behavior.
Ask Chat to identify the source, then open it yourself before relying on a consequential claim.