Product guide
Files & storage
File shares, cloud drives and the wikis your team writes in — Google Drive, SharePoint, Dropbox, S3, Notion, Confluence and more, each set up field by field.
Sources →
A source is a place your knowledge lives. The built-in “Uploaded documents” source holds files you upload here; you can also connect a Google Drive,…
Google Drive →
The usual setup is sharing a folder with a “service account” — a robot Google account your company creates for itself in a few minutes. No approval…
OneDrive / SharePoint / Teams →
This source runs on your company's OWN Entra app credentials — three values your IT admin creates once (about ten minutes), with no vendor approval…
Microsoft OneNote →
Bring your OneNote notebooks in — each page becomes a searchable document, tied to its notebook and section. Microsoft offers no app-only door to…
Dropbox →
Dropbox is connected through your own Dropbox “app” — a credentials container you create in a couple of minutes; nothing is installed and nobody else…
Box →
Connect Box to sync a folder — or everything shared with the app's service account. Files sync with exact change detection (Box's own checksums), so…
Amazon S3 →
In the AWS IAM console create a user (or role) with programmatic access.
Azure Blob Storage →
Connect an Azure Blob Storage container (or a prefix within one). Every blob becomes a document; later syncs re-read only blobs whose ETag changed.…
Nextcloud / WebDAV →
Works with Nextcloud, ownCloud and any other WebDAV server. Best practice is a dedicated account (or an app password) that can read just the folders…
SFTP / FTP server →
Connect a folder tree on an SFTP or FTP(S) server — the classic file drop. Every file under the chosen path becomes a document, and later syncs…
Notion →
Notion access works through an “integration” — a robot member of your workspace. You choose exactly which pages it can see; everything below those…
Confluence →
Connect Confluence to make the company wiki searchable — every page (and optionally blog post) becomes a document, so “how do we onboard a customer”…
Coda →
Connect Coda to make your docs searchable — every page of every doc the token can see becomes a document. Read-only.
Guru →
Connect Guru to make your verified knowledge cards searchable — each card becomes a document with its collection and verification state, so verified…
GitBook →
Connect GitBook to make your docs spaces searchable — every page of every space becomes a document. Read-only.
Outline →
Connect your Outline wiki — self-hosted or getoutline.com — and every document the token can see becomes searchable, with its collection. Read-only.
MediaWiki →
Connect a MediaWiki wiki — the engine behind countless internal engineering and company wikis. Every article becomes a document, rendered to clean…
BookStack →
Connect a BookStack wiki and every page becomes a document carrying its book and chapter, so answers point back to the right shelf. Drafts are left…
Document360 →
Connect a Document360 knowledge base — every published article becomes a document carrying its category path. Hidden and draft articles are left out.…
Was this page helpful?
Last updated 28 Aug 2026