Citations and grounding
Answers surface citations when evidence exists, and Vera labels partial or missing evidence instead of guessing.
Proof surface
Chat transcript, evidence drawer, and grounding states
Product reality, not brochureware
Grounded answers from your workspace knowledge,with evidence when Vera has it.
Vera is built for teams that need fast answers without hiding the source of truth. The shipped product supports grounded responses, role-aware access, audit evidence, and clearly different connector modes without pretending every rollout is equally validated.
CitationsRBACIdentity rolloutAudit evidenceConnector tiers
Grounded answerEvidence drawerRole-filtered
app.vera.so
What are the cancellation terms in our enterprise contracts?
Grounded answer · Contract_Terms.pdf · Page 12
Vera keeps the answer attached to source context instead of replacing the source of truth.
Ask Vera anything...
Send
What Buyers Can Verify In Product
The front door now matches the strongest shipped surfaces.
These are not aspirational claims. Each one maps to product behavior that already exists in the repository and avoids promising release proof that still depends on live validation.
Role-aware access
Workspace, document, and integration access are scoped by tenant, role, and optional group restrictions.
Proof surface
RBAC, custom roles, and group-based controls
Identity rollout controls
MFA and passkeys are in product, and SSO configuration/testing exists for staged rollout with your own IdP.
Proof surface
Login, MFA, passkey, and admin SSO setup surfaces
Audit evidence
Admins can review audit events and export audit evidence without pretending deployment proof is already complete.
Proof surface
Audit log review and export surfaces
Connector Modes
Not every provider works the same way, and the UI says so.
Vera already distinguishes between syncable providers, live-query providers, and app-surface connectors. Buyers should be able to understand utility at a glance instead of guessing from a generic “connected” label or assuming every provider has the same validation depth.
Indexes into KB
Syncable connectors
Selected providers can import content into Vera's searchable knowledge base when configured, scoped, and validated for that rollout.
Live query only
Live-query connectors
Gmail and Outlook answer on demand from recent mailbox context. They help during a live question, but they do not populate the shared KB.
App access only
App-surface connectors
Slack and Teams extend Vera into chat surfaces. Treat them as rollout-sensitive app integrations, not shared knowledge-base ingestion.
Honest first-run path
The real product flow is now the story: create the workspace, verify the admin email, sign in, connect knowledge, then invite the team. Identity rollout and commercial rollout can follow later if needed.
Choosing the Enterprise plan does not pretend procurement is already finished. Self-serve signup still creates a trial workspace first; custom contracting and rollout happen outside that flow.
01
Create the workspace and verify the admin email.
The signup flow already creates the workspace admin, starts the trial, and holds access behind email verification when configured.
02
Sign in, connect the first source, or upload starter documents.
Onboarding is strongest when it focuses on real setup states: no integrations yet, no KB documents yet, or sources connected but not indexed.
03
Invite teammates and start identity rollout only when you actually need it.
Invites, admin access controls, and identity rollout live in the product, but they should appear as next steps instead of false defaults.
Start with the product you can actually defend in a buyer meeting.
Create the workspace, walk through the real onboarding path, and show connector behavior exactly as it works today.