Skip to main content
Agents read from two kinds of storage. Knowing the difference helps you decide where a given piece of information belongs.

​
Doc Store — your files

A Doc Store holds unstructured documents: PDFs, spreadsheets, payroll registers, project logs, prior workpapers. It’s what the File Explorer shows. End users just call this “files.”
A Doc Store in File Explorer, showing unstructured files an agent can read, grouped into a workstream-scoped document store
You fill a Doc Store by connecting a source and running a sync:
  1. Connect a Connector (Google Drive, SharePoint, File Upload, Amazon S3).
  2. A File Sync brings the files in and lands them in the Doc Store.
  3. The agent reads from the Doc Store when it runs.
A Doc Store is scoped to its client (workstream), and access to it is granted to specific workstreams and agents.

​
Data Store — structured tables

A Data Store table holds structured data an agent can query — for example a client-management table with columns like client_name, industry, primary_contact, arr, status. Standard columns (id, created_at, updated_at, is_deleted) are added automatically.
The Data Store — named, structured tables an agent can query, each with a row count and scope
A Data Store is optional. Use it when the agent needs to look something up in a table rather than read it out of a document.

​
Scope choices

When a builder creates a Data Store table, they pick a scope — the same two axes as everything else in Adopt:
  • Global — org-wide; every workstream and agent can read it. Use for reference data that isn’t client-specific.
  • Workstream-based — row-scoped per client (row-level security). Each client only sees its own rows. This is the safe default for client data.
  • Workstream + Agent — per client, and only readable by specifically tagged agents. The tightest scope.
End users never see this choice; on the Quick setup path a sensible default (workstream-based) is applied automatically.

​
Which do I use?

​
Next steps

  1. Connecting a data source
  2. Create a Data Store table
  3. Access scoping