THE VAULT// HELP & GLOSSARY
[USER-FACING OVERVIEW FOR HOSTS AND GUESTS. FOR OPERATOR SETUP, REFERENCE THE PROJECT README.]
SECTION 01
01 // GETTING STARTED
A host runs the studio. Guests join by link. The active meeting stays selected while you move between CRM, email, AI, docs, and scaffold utilities. Subscribe at /pricing to unlock full host access, or sign in if you already have a studio account.
01 // HOST AUTHENTICATION
Sign in as a host to open the master studio dashboard. Subscribe at /pricing for studio host access when billing is enabled.
02 // SESSION INITIALIZATION
From Overview, add a client, schedule a meeting, and distribute the invite.
03 // LIVE CONNECTION
Start the call from the meeting lobby when you and the client are ready.
04 // GUEST ACCESS
Guests join via the invite link or direct room code at /meet without needing a host account.
05 // POST-CALL UTILITIES
After the call, utilize Email, AI output, docs, and Scaffold tabs while the active meeting session remains selected.
SECTION 02
THE GLOSSARY // CORE ARCHITECTURE
- MEETING STUDIO
- The host dashboard where one meeting stays selected across Overview, CRM, email, AI, and scaffold tabs.
- CRM
- Client records with contacts, notes, repositories, and optional encrypted vault storage.
- RECAP
- Post-meeting page with recording playback and summary when a meeting has ended or is no longer joinable.
- SCAFFOLD
- Generated project structure pushed to GitHub after a session, grounded in meeting context.
- VAULT (ENCRYPTED STORAGE)
- Per-client encrypted JSON payloads (credentials, contracts, notes) stored as ciphertext in the database.
- PROTOTYPE EMAIL
- Client-facing email preview and send flow tied to the active meeting in the studio.
- AI BRIEF
- Structured requirements and highlights produced from meeting transcripts and notes when AI is enabled.
- TEAM WORKSPACE
- Shared delivery area for collaborators: invites with CRM access, internal tasks, team chat, and multi-team switching for studio hosts.
[DATA_PRIVACY_AND_INFRASTRUCTURE_PROTOCOLS]
- Self-Hosted Infrastructure: Your operator runs The Vault entirely on their own infrastructure; all data stays strictly within your isolated database and configured storage system.
- Media Storage: Meeting recordings require blob storage configurations (e.g., Vercel Blob) when deployed to Vercel; otherwise, temporary uploads may not persist.
- Encryption Key Requirements: Encrypted client vault items strictly require a valid
VAULT_ENCRYPTION_KEYconfigured on the server environment; without it, vault encrypt/decrypt actions remain unavailable. - Model Training Exclusions: This documentation describes raw product behavior; it does not grant third parties or external LLMs any rights to use your private meeting content for model training.