Companion Context and Handbook
For Companion to be useful, it needs the right context: which data it is allowed to read, and the background knowledge about your organisation that helps it interpret what it sees. Harmony combines two things to provide that context — the workspace's Handbook for organisation-wide knowledge, and a per-thread Sources picker for narrowing the answer to specific data.
What Companion can see
When you open Companion, it has visibility into the data the current user is allowed to access:
- Conversations the user can read (including transcripts, summaries, action items, and insights for those meetings).
- Workspace content the user has read-permission on — projects, reports, contacts, accounts, custom fields, etc.
- Connected integrations the user (or the workspace, when applicable) has authorised.
Companion always respects the workspace's role-based permissions — see Roles and Permissions. If you don't have read access to a meeting, Companion can't read it for you either.
The Handbook (workspace-wide context)
The Handbook is a free-text area where workspace admins describe the organisation. Companion, Insights, and other AI surfaces read the Handbook when reasoning about your data, so it is the right place for jargon, product positioning, and the business context every AI surface should know.
The Handbook lives on Settings → General, not under Project Knowledge.
To edit it:
- Open Workspace Settings → General.
- Scroll to the Handbook section.
- Type or paste your context.
- Click Save.
The Handbook supports up to about 5,000 characters.
Good things to include:
- What your organisation does.
- Your products and services (and any names that are easy to confuse with everyday words).
- Your target customers.
- Key terminology, acronyms, and jargon used internally.
- Pricing tiers, packaging, and any non-standard deal structures the AI should be aware of.
For project-scoped context (when something only matters for one Insight project), use Project Knowledge under that project's Basics tab — see Project knowledge. Project Knowledge applies only to its project; the Handbook applies workspace-wide.
Narrow Companion to specific sources for one thread
Companion's composer includes a Sources picker on the input bar. The picker lets you scope a single thread to specific entities — a conversation, a contact, an account, a project, a goal — so Companion answers from those rather than the whole workspace.
In practice:
- Open or start a Companion thread.
- Use the source picker on the composer to attach one or more entities (conversation, contact, account, project, goal, etc.).
- Companion's answer is grounded in the attached sources for that thread.
The exact controls and the labels of the entity types in the picker are documented under Companion sources and entities. The intent is the same: bound the answer to data you care about.
Companion vs Insights vs Project Knowledge
| Surface | Where context lives | Scope |
|---|---|---|
| Companion | Workspace Handbook + per-thread sources + the user's permissioned data | Per user / per thread |
| Insights | Project Knowledge (project-scoped) + Additional Context (definition-scoped) | Per project / per definition |
| Both | Workspace Handbook | Workspace-wide |
If a piece of context matters for one Insight project only, put it in Project Knowledge. If it matters for everything Companion and Insights ever touch, put it in the Handbook.
Privacy
For details on how Companion processes meeting and chat data through AI providers, see Models and training data. Workspace permissions are the source of truth for what each user can ask Companion about.