Documents & files
Libraries, shared drives and network folders, re-read every night: only what changed is processed again.
- SharePoint
- Google Drive
- Box
- Dropbox
- Windows network shares
- Server folders
- S3 storage
- Upload from your computer
Connectors
Documents, conversations, tickets or databases: DeepView connects to the tools where your information already lives, and answers by citing the original source.
Supported sources
Libraries, shared drives and network folders, re-read every night: only what changed is processed again.
Threads, emails and documentation pages, with the files they share.
Tickets, requests and customer records, with their history and comments.
Queried live and read-only: filters, counts and totals are computed by the database, never estimated.
Your internal or public websites, and any tool exposed through the MCP protocol, allowed function by function.
Two ways to connect
Documents, pages and conversations are analysed and indexed inside your environment. Sources are re-read automatically; only what changed is processed again.
Databases and MCP tools are queried when a question calls for them, read-only. Nothing is copied.
Who connects what
Once for the whole organisation. Secrets are encrypted and stay in your environment.
They sign in with their own account, pick the library, folder or table, and share it with their project.
Without needing rights on the original tool. Other projects see none of it.
Access is granted as narrowly as possible: site by site for SharePoint, team by team for Teams, mailbox by mailbox for email. A restricted page stays invisible to anyone who cannot see it.
Formats
Tables, table notes, diagrams and charts are understood with their layout; figures are described so that search can find them.
The other way round
A project can be opened to an MCP-compatible AI assistant: your teams query DeepView without leaving the tool they work in.
Tell us which one: we will work out with you how to connect it, through a dedicated connector or through MCP.