Connected sources
Ground learning in Google Drive, Microsoft Teams, and Notion content.
Your knowledge does not all live in files you can upload. Connectors let Vidext search and read content where it already lives, so modules can be grounded in living sources.
Available connectors
Read-only access to your Drive. Vidext can search files by content and read documents — including Google-native formats — as planning and building context.
Basic read access to the teams and channels you belong to, so institutional knowledge in Teams can inform generation.
Workspace access to search pages and read their content — wikis and process docs become usable sources.
How connecting works
Connections are made per person, per organization — start one from Settings → Connectors or from the chat composer's add (+) menu, then authorize through each provider's standard OAuth consent. You authorize with your own account; Vidext receives read-oriented scopes only.
- Credentials are encrypted at rest and never shown again after connection.
- You can revoke a connector at any time from Settings — and from the provider's side too.
- A connection belongs to you in this organization; it is not shared with other members.
How connected sources get used
Once connected, Vidext can search your sources and read specific items while planning and building — pulling in the relevant policy page or process doc as grounding without you exporting and re-uploading it. Connected content is read on demand; Vidext does not bulk-copy your Drive, Teams, or Notion.
What about SharePoint, our CRM, our HRIS?
Deeper connections to systems like SharePoint, CRM data, and HR/LMS platforms are on the roadmap, not available today. The current connector set is Google Drive, Microsoft Teams, and Notion — plus uploads and website import.
Last updated on