Core Concepts

Understanding Sessions, Accounts, and Vaults is key to getting the most out of Ida. These concepts help you organize your meetings, track relationships, and scope your knowledge bases.

Sessions

A Session represents a single meeting, call, or work period. Think of it as a container that captures everything from one interaction—the transcription, AI recommendations, notes, and chat history.

What's in a Session?

  • Transcriptions — Real-time audio converted to text
  • AI Recommendations — Context-aware suggestions from your indexed documentation
  • Notes — Your own notes taken during or after the session
  • Chat Messages — Questions and answers with the AI assistant
  • Pinned Resources — Important items you've saved for quick reference

Session Properties

Property Description
title Custom name (or auto-generated from calendar event)
created_at When the session started
ended_at When recording stopped (null if still active)
total_duration Length of the session in seconds
calendar_event Linked Google Calendar event (optional)
account Associated account/company (optional)

Working with Sessions

  • Create a new session — Click the "New Session" button or it's created automatically when you start recording
  • Switch sessions — Use the session dropdown to view past sessions
  • Rename a session — Click the session title to edit it
  • Link to calendar — Connect a session to a Google Calendar event for context
  • Assign to account — Group sessions by company or client
Pro Tip

Link sessions to calendar events for automatic naming and easy organization. When you select an upcoming meeting, Ida pre-loads relevant context.

Accounts

An Account represents a company, client, or organization you interact with. Accounts help you group related sessions and maintain persistent notes across multiple meetings with the same entity.

Why Use Accounts?

  • Organization — Group all sessions with a client in one place
  • Persistent Notes — Account-level notes carry over between sessions
  • Context — Quickly see your history with any company
  • Analytics — Track total time spent with each account

Account Properties

Property Description
name Company or client name
domain Website domain (optional, helps with auto-matching)
industry Industry category (optional)
stage Relationship stage like "prospect", "customer", etc. (optional)

Account View

The Account view shows a consolidated overview including:

  • All sessions linked to this account
  • Account-level notes (persistent across sessions)
  • Session notes from all related meetings
  • Pinned resources saved during any session
  • Chat history across all sessions

Vaults

A Vault is a self-contained knowledge base—a collection of indexed documentation that can be scoped for specific use cases. Vaults let you organize and control which documentation feeds into your chat and recommendations.

Why Multiple Vaults?

  • Separation — Keep work and personal documentation separate
  • Focus — Only surface relevant docs for each context
  • Team Sharing — Share organizational vaults across your team (coming soon)
  • Performance — Smaller, focused vaults search faster

Vault Structure

Each vault contains:

  • Sources — The URLs, folders, or text snippets you've indexed
  • Chunks — Individual pieces of content with embeddings
  • Metadata — Settings like embedding model and chunking strategy

Workspace Configuration

The Workspace controls which vaults are active at any time. You can enable or disable vaults for chat and recommendations independently:

Setting Effect
enabled_for_chat Include this vault's docs when answering questions
enabled_for_recommendations Use this vault for automatic recommendations during meetings
priority Search order when multiple vaults are active
Example Setup

Create a "Product Docs" vault for customer calls (enabled for recommendations) and a "Internal Wiki" vault for internal meetings. Toggle them based on your meeting context.

Default Vault

When you first use Ida, a "Default" vault is created automatically. All your indexed documentation goes here unless you create and select a different vault.

How They Work Together

Here's a typical workflow showing how Sessions, Accounts, and Vaults interact:

  1. You have a Vault called "Product Docs" with your API documentation indexed
  2. You create an Account for "Acme Corp" (a client)
  3. You join a call with Acme Corp and start a Session
  4. The session is linked to your "Acme Corp" account
  5. As you discuss integration options, Ida searches the "Product Docs" vault
  6. Relevant API documentation surfaces automatically
  7. After the call, notes and recommendations are saved to this session
  8. Next time you meet with Acme Corp, you can see your full history in the Account view

Next Steps