All documentation

Workspace administration

Connect your company knowledge

Scope and verify SharePoint, Drive, Slack, Teams, Gmail, Outlook, HubSpot, Salesforce and Zoom.

Implementation guide, not a guarantee that every connector is enabled or validated for your workspace. Confirm the deployed version, provider scope and rollout status with the Vera team. Older release notes and newer implementation differ for Slack and Teams; this guide describes the current code with that qualification.

On this page

Start with an approved scope

Open Integrations in your signed-in workspace. Select the provider and review its connection details. An administrator may need to grant provider permissions.

  1. Agree which content should be available and who should have access.
  2. Complete provider authorisation using an approved company account.
  3. Review the scope, roles and groups shown in the settings.
  4. For sync-capable connectors, run a sync and review its result.
  5. Test a known question and citation with a representative user account.

Read the status, not just the connection

‘Connected but not indexed’ means Vera has a connection but no indexed documents from that source yet. ‘Healthy and searchable’ indicates indexed content is available.

Some connections support live queries or app access rather than sync. Check the capability in the connector details; do not assume all providers ingest content in the same way.

SharePoint

Indexed document sync. Configure both a drive ID and a folder item ID, then review permitted roles and groups before syncing. Only file types supported by the deployment are ingested; a connection does not make every site or library searchable.

Google Drive

Indexed document sync from an explicit folder or shared-drive scope. Only supported file types are ingested. Check the selected scope, access settings and sync result, then verify a known file through a citation.

Slack

The current implementation supports limited channel-message indexing and Q&A through the Slack app. Invite Vera to the channels it should read and review the coverage shown in the connector. The catalogue limits indexing to message text, excluding files, attachments and direct messages; do not assume complete historical backfill. Confirm these boundaries in your deployed version before rollout.

Microsoft Teams

The current implementation supports limited channel-message indexing and Q&A through the Teams app. It requires app registration, bot configuration and the appropriate Microsoft permissions. Channel file attachments require a separate SharePoint sync, and historical coverage is bounded by the configured message limit. Validate the selected teams and scope with your administrator.

Gmail

Live queries for recent Gmail context. Gmail does not sync mail into Vera’s shared knowledge base. Use it for on-demand context within the authorised scope, not as a durable indexed email archive. Confirm permissions and the query scope with your administrator.

Outlook

Live queries for recent Outlook mailbox context. Outlook does not populate Vera’s shared knowledge base. Review the authorised mailbox scope and test a representative question; do not expect archival coverage or treat a live query as a completed document sync.

HubSpot

Indexed sync of HubSpot Companies, Contacts and Deals. Other HubSpot objects are not included in this documented scope. Review access and run a sync, then check a known record before relying on the resulting answers.

Salesforce

Indexed sync of Salesforce Accounts, Contacts and Opportunities. The connector requires a valid Salesforce instance URL from authorisation. Review selected objects and access settings, then verify a known record after syncing; do not assume support for every Salesforce object.

Zoom

Indexed ingestion of recording transcripts and related text artifacts. Availability depends on recordings and transcript export formats. This does not index live meeting state or guarantee a transcript for every meeting. Verify that the expected transcript is present after syncing.

After a configuration change

Recheck the status and test affected content after changing scope or permissions. Complete renewed authorisation if the provider requires it.

Disconnecting a provider and deleting indexed content are not the same operation. Confirm the required removal process with your administrator or Vera support.

Need help with a connector? Next guidePeople, roles and access