Skip to main content

Companion Context and Handbook

For Companion to be effective, it needs access to the right information. "Context" refers to the data boundaries and knowledge base Companion uses to answer your questions.

Organization Context​

When you log in, Companion automatically gathers your Organization Context - think of this as the set of information it's allowed to use to help you. Here’s what that means for you:

  • Relevant Data: Companion can see meetings, transcripts, and notes - but only the ones you personally have permission to access. Nothing outside your allowed workspace is included.
  • Insights: It also pulls in useful, structured information, like KPIs and project metrics, so you can ask about trends, results, or stats from your own projects.
  • Private & Secure: Your privacy is a top priority. Companion strictly respects all workspace permissions. If you don’t have access to a meeting, Companion won’t be able to answer questions about it or see its contents. Simply put: it only knows what you’re allowed to know.

This approach keeps your data both helpful and safe, ensuring answers are personal, relevant, and always respect your privacy.

Data Connectors​

You can explicitly control what data Companion uses for a specific query. Use the handy + button right in the chat bar. This lets you guide Companion on exactly where to look for answers.

Here’s how you can focus your search:

Meetings: Only look through meeting transcripts. Perfect when you’re digging for something specific that was discussed in a call.
Notes: Search in your written notes and summaries. Great for finding ideas or details you’ve jotted down in the past.
Events: Ask about your schedule, upcoming appointments, or anything in your calendar.
Connectors: Tap into integrated apps like Google Calendar to expand your search even further.

The "Handbook" (Custom Knowledge)​

Beyond raw meeting data, you can teach Companion about your specific business via Project Knowledge (often called the Handbook).

If you find Companion doesn't understand your internal acronyms or project code names, you should add these definitions to your Project Settings under Project Knowledge. Companion reads this "handbook" before answering to ensure it uses your terminology correctly.