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.

This category covers everywhere files, folders and internal wikis already live: cloud drives (Google Drive, OneDrive/SharePoint, Dropbox, Box), raw object storage (Amazon S3, Azure Blob Storage), on-premises or NAS file shares (Nextcloud/WebDAV, an SFTP or FTP server), Microsoft OneNote notebooks, and the wikis teams actually write in — Notion, Confluence, Coda, Guru, GitBook, Outline, MediaWiki, BookStack and Document360. Whatever already holds your documents, there's almost certainly a source for it here.

Every one of them takes a single read-only credential you create yourself, in that provider's own console — a service account key, an app registration, an API token, or a key pair — pasted in once. None of them can write back: nothing done here changes a file in Drive, a page in Confluence, or an object in a bucket. Each source then syncs on its own schedule and whenever you press Sync, picking up only what changed since last time.

Start from where the documents already sit. Already storing files in Google Drive, OneDrive/SharePoint (this covers Microsoft Teams files too), Dropbox or Box? Connect that directly — it's the least setup. Reach for Amazon S3 or Azure Blob Storage for a raw bucket a developer or an export job writes to; a Nextcloud/WebDAV server or a plain SFTP/FTP connection for an on-premises file drop or an older NAS box that speaks one of those protocols. For a company wiki or knowledge base, pick whichever tool the team actually writes in — Notion and Confluence are the two most common; Coda, Guru, GitBook, Outline, MediaWiki, BookStack and Document360 cover the rest. A plain shared network drive with none of those protocols still needs your provider to connect it as a folder source.

The connectors

• SourcesA 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, a OneDrive/SharePoint library (including Microsoft…
• Internal docsInternal docs is the built-in source for what your organisation writes inside Naxis Assistant itself: notes, decisions, procedures, meeting write-ups, an AI agent's own memory — and files kept beside…
• Google DriveThe 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 from anyone else is involved, and the only…
• OneDrive / SharePoint / TeamsThis source runs on your company's OWN Entra app credentials — three values your IT admin creates once (about ten minutes), with no vendor approval involved and no personal sign-in to break. By…
• Microsoft OneNoteBring your OneNote notebooks in — each page becomes a searchable document, tied to its notebook and section. Microsoft offers no app-only door to notebooks (they are always read as a signed-in user),…
• DropboxDropbox is connected through your own Dropbox “app” — a credentials container you create in a couple of minutes; nothing is installed and nobody else approves anything. Three values end up pasted…
• BoxConnect Box to make a folder — or everything shared with your own Box app — searchable: every file the app can see becomes a document, and because Box lists each file's own checksum, a re-sync…
• Amazon S3An Amazon S3 bucket, or a prefix within one — or any S3-compatible store such as MinIO, Wasabi or Backblaze B2. Every object becomes a document, and a later sync re-downloads only the objects whose…
• Azure Blob StorageConnect an Azure Blob Storage container — or a prefix within one — to make its files searchable: every blob becomes a document, and because each blob's ETag comes with the listing, later syncs…
• Nextcloud / WebDAVWorks with Nextcloud, ownCloud and any other WebDAV server. Every file in the folders the account can reach becomes a document, re-read on each sync. Read-only: nothing is written back.
• SFTP / FTP serverConnect 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 re-read only files whose size or modification time…
• NotionNotion access works through an integration — a robot member of your workspace. You choose exactly which pages it can see; everything below those pages, sub-pages and database entries included,…
• ConfluenceConnect Confluence to make the company wiki searchable — every page, and optionally blog posts, becomes a document, so “how do we onboard a customer” answers from the page your team already wrote.…
• CodaConnect Coda to make your docs searchable — every page of every doc the token can see becomes a document. Read-only.
• GuruConnect Guru to make your team's knowledge cards searchable — every card the token's account can see becomes a document carrying its collection and verification state, so the team's verified answers…
• GitBookConnect GitBook to make your docs spaces searchable — every page of every space the token can see, in every organisation it belongs to, becomes a document, so product docs, handbooks and internal…
• OutlineConnect your Outline wiki — on your own server or getoutline.com — and every published document the key can see becomes a document here, carrying its collection and author, so the team wiki answers…
• MediaWikiConnect a MediaWiki wiki — the engine behind Wikipedia and countless internal engineering and company wikis. Every article in the chosen namespaces becomes a document, rendered to clean text;…
• BookStackConnect a BookStack wiki on your own server and every page the token can see becomes a document carrying its book and chapter, so answers point back to the right shelf. Drafts are left out. Read-only.
• Document360Connect a Document360 knowledge base — every published article across the project's versions becomes a document carrying its category path, so the help centre the team already writes answers…

Where these credentials live

Every credential above is created and owned by you, in the provider's own console — Google Cloud, the Entra admin center, Box's or Dropbox's developer console, each wiki's own API-token settings page. This deployment never asks for your organisation's main password, and there's no vendor approval to wait on: creating the credential and pasting it in is normally a same-day job for whoever administers that tool.

Last updated 20 Sep 2026