The Settings tab contains firm-wide features and data retention rules.
Meeting assets
This is where you set your firm’s retention policy for meeting recordings and transcripts.
Auto-delete transcripts and recordings: When enabled, Vega permanently deletes meeting transcripts and recordings once they reach the age you set.
Delete after: The retention window is 0, 7, 14, 30, 60, 90, 180, or 365 days. Zero days means transcripts and recordings are not kept at all.
Include preparation and analysis: By default, only transcripts and recordings are deleted. Turn this on to delete meeting preparations and meeting notes on the same schedule.
Deletion is permanent and cannot be undone, so we recommend agreeing on a retention window with your compliance team before turning this on.
Compliance reviews
Compliance reviews: When enabled, Vega runs a compliance review on meetings and sent emails, and sends flags to your firm’s compliance contact email (set on the Information tab).
Copy the user: Copies the user on the flag emails sent to your compliance contact.
Client deliverables are always reviewed, whether or not this setting is on, and those flags stay on the deliverable itself.
Compliance reviews run for users on Pro. Turning the feature on does not review meetings or emails from users who are not on Pro. During a trial, everyone is on Pro, so it covers the whole firm (read article: Core vs Pro).
Client enrichment
Client enrichment: When enabled, Vega builds a living story for your contacts and households and keeps it up to date as new information comes in.
Contact living story: A template that guides the layout of living stories for individual contacts.
Household living story: A template that guides the layout of living stories for households.
Both templates are optional. Vega has sensible defaults, and clearing a template restores the default. Use them when your firm wants living stories to follow a specific structure.
Like compliance reviews, client enrichment applies to users on Pro. Turning it on does not enrich contacts or households belonging to users who are not on Pro; during a trial it covers every client (read article: Core vs Pro).
Other
Claude MCP connector: When enabled, users at your firm can connect Vega to Claude through MCP (Model Context Protocol). Claude can then work from the same client context they see in Vega, so they can prepare for a review from past meeting notes, find what a client said about a goal, gather open action items before a call, or draft follow-ups grounded in the client's history. This setting is off by default.
Once the setting is on, each user connects their own account in Claude:
In Claude, open Settings > Connectors, click Browse connectors, and search for Vega. You can also go straight to claude.ai/directory/vega.
Click Connect and sign in with your Vega account.
Click Allow on the Vega consent screen.
If your firm uses a Claude Team or Enterprise plan, an owner of your Claude organization may need to enable Vega in Claude's admin settings before users can connect. Users can disconnect at any time from Claude.
What Claude can access: Client and household profiles and living stories, meetings, AI notes, transcripts, meeting preparations, action items, client documents, and your Knowledge Center.
Read-only: Claude cannot create, edit, or delete anything in Vega or in your CRM.
Same permissions as Vega: Claude only sees what the connected user can already see in Vega. Your firm's sharing and team permissions apply to every request.
Turning the setting off cuts off Claude's access right away for everyone at your firm, including users who have already connected. Users who try to connect while it is off are asked to contact their firm admin.
The Claude MCP connector is available to all Vega users, whether they have a Core or Pro seat.