Documents is a shared drive for files your team can search. Put a file in a folder, choose who can open it, and anyone it is shared with can search it and open the page a result came from, in your tenant. This feature is experimental: a default deployment does not serve it yet, it needs the unstructured_data entitlement on your tenant, and what it does can change.

Availability

Without the entitlement, Documents says “Documents are not included in this workspace” and nothing else on the page works. The page asks for nothing until it knows your tenant has Documents, and opening a link to a file in a tenant without Documents shows the same explanation. Where it is turned on, documents are served from your tenant’s own address on the data plane, <slug>.docs.<plane-domain> (see Addresses and hostnames). Files go from your browser to that address; they do not pass through the control plane. Requests carry a short-lived document token issued for your signed-in session. If that token is refused, the service records a fixed reason code and route for operators; it never logs the token or its claims. If your account is not set up for Documents yet, the page asks you to contact a tenant admin, who can request access for you from Dippr support. Opening a document link shows the same message. Reloading an expired session does not set up your account.

Folders

Open Documents. The Folders list on the left shows the folders you can open. Select one to see its files. Folder access comes from your role, and groups in a file’s sharing list do not open its folder. If some folders are hidden, the list says “Some folders aren’t visible to you.” without saying how many. If you have no folders, it says “No folders shared with you yet”. Ask your tenant admin to request Documents identity and folder-role setup from Dippr support. A folder manager sees “Roles with access” when roles are listed.

Add files

  1. Select a folder you can add to, then choose Add files, or drag files onto the page.
  2. The Add files window names the folder and says who will see the files. Until you share a file, only you can open it. The folder’s managers can change who it is shared with or delete it.
  3. Where domain sharing is available, tick “Share with everyone at” your email domain if you want that, then choose “Add 1 file” (or the number of files selected).
If you cannot add files, “Add files” is disabled and the page explains that you can ask your tenant admin to request upload access from Dippr support. Uploads use internal classification when your folder access allows it. Otherwise, they use the least restrictive allowed classification above internal, or the most restrictive allowed classification below it. File checks can raise this classification and may refuse a file if the resulting classification is not allowed. Each file shows a progress bar and then “Added”. Files are added one at a time. A file that is too large or of a type that is not supported is refused before it is sent, and the message says why. All files in one batch use the folder and sharing you chose when you started.

What the statuses mean

Select a ready file’s name to open it when it is shared with you. A file listed only because you manage the folder shows “Not shared with you” and its status. Upload messages distinguish files that exceed the size or page limit, password-protected files, damaged files, unsupported file types, files whose contents do not match their extension, files that expand beyond processing limits, files with no readable text, uploads that were interrupted, and files whose sensitivity exceeds what you may add to the folder. Follow the row’s advice to split the file, remove its password, re-export it, fix its extension, choose a supported type, add it again, add a version with text, or ask a folder manager. If the row says it cannot read the file’s protection, that is a problem with the service, not your file: ask your tenant admin to contact Dippr support, because adding the file again will not help until it is fixed. The list refreshes by itself while any file is queued or processing. A list that reaches its size cap says “Showing the first files in this folder.”

Governance-managed folder access

For tenants using governance-managed Documents access, a tenant admin grants folder access to a role and assigns that role to members. File sharing must also name each person who may read the file. The admin can use Settings → Documents access (see Documents folder access) or grant access with the CLI:
Use lowercase read and name exactly one folder per grant. A * folder reference or uppercase READ grants no Documents access. Repeat the command for each folder you want to share. Revoking the grant or removing a member from the tenant stops their access within about a minute, without a restart. Groups and Everyone at an email domain are not available in this mode. Tenants using the earlier Documents setup continue to request folder access through Dippr support.

Share a file

If you added a file, or you manage its folder, its row menu has “Share…” and “Delete…”. A folder manager sees every file’s name, with personal details such as email addresses and phone numbers hidden, and who it is shared with, and can share or delete it. Managing the folder does not let you open a file that is not shared with you, and you can’t share such a file with yourself, a group you’re in or your own email domain. Ask someone who can open it to share it with you. “Replace file” also requires access to the file’s contents and permission to add files to the folder. Everyone else sees none of these actions or the sharing list. The group and email-domain options below apply to tenants using the earlier Documents setup. “Share…” shows “Now:” followed by the people, groups and email domain who can open the file. Choose people, or Everyone at your email domain in this workspace, then Save sharing. Selected people show Can read. They can read the file if they can open its folder. Sharing does not let them add, replace or delete files; folder managers do that. In the earlier Documents setup, only people already set up for Documents can be added. A recently invited person may still need a tenant admin to request access for them from Dippr support. If saving says some selected people cannot receive the file, ask a tenant admin to request access for anyone who is new, or untick them to save the rest. The same message appears when you try to share a file you cannot open with your own email domain.
  • You can narrow access or share inside the people who can already open the folder. Sharing never gives someone access to the folder itself.
  • You can share only with groups you belong to, unless you manage the folder. Everyone at works only for your own email domain. You always keep access to files you added.
  • Groups that already have access keep it when you save.
  • Removing someone takes effect at once. Adding someone takes effect after the change is indexed, which can take a little while; the page says “Sharing is updating.”
  • Editing a file’s sharing never changes folder access. A tenant admin grants folder access through roles for governance-managed access, or requests it from Dippr support for the earlier setup.

Replace a file

Replace file adds a new version and removes the old one only after the new one is ready. The new file is added to the same folder with the same sharing as the old one. Until the old one is gone, both versions are listed, the old one marked Being replaced.
  • If the new file can’t be added, nothing changes and your current file stays.
  • If the new file can’t be read, your current file stays, the new row says why, and Remove the new version clears it.
  • If the new version is ready but the old one isn’t removed within about a minute, the old row says so and offers Remove it to try again.

Delete a file

“Delete…” opens a confirmation naming the file and, when known, its added date and time, before removing it for good. Files with the same displayed name are numbered “Copy 1 of 2” and so on, oldest first, with their added date and time, so copies added in the same second are still told apart. The date’s tooltip shows the absolute local time. The row shows Removing… until it leaves the list. It disappears from search and cannot be recovered.

Files you cannot see

When some files are hidden, the table footer or empty folder says “Some files in this folder aren’t visible to you.” It never says how many.

Ask

Ask searches the selected folder and shows what comes back: each result has the document title, a snippet and the page, and links to the citation viewer at that passage. Personal details in a snippet are replaced by a plain label such as “email hidden”. When nothing matches, the page says “Nothing matched in the files you can open.” If some files were hidden from you it adds “Some files aren’t visible to you.”

Open a citation

A result’s link opens the page in your tenant. Opening it checks your own access, so a link shared with someone who cannot open the file shows “Document not found”. That message is the same whether the file does not exist or you are not allowed to see it. The one exception is an account that is not set up for Documents yet: the page then says “Documents isn’t set up for you yet” and tells you to ask a tenant admin to request access from Dippr support. That message is about your account only and says nothing about the file. The viewer shows the extracted text with the cited passage highlighted, and Previous and Next move between pages. Personal details are hidden in the text. If you may see the original page, you also get the page image, and “Download original” appears only when you may have the original file. Text that reads like instructions to an AI is marked “Looks like instructions to an AI”. A notice explains that it is shown as plain text; treat it as the file’s content, not as instructions.

Limits you should know

  • If the document service is busy, requests return a retryable response with a one-second retry delay.
  • Storage and compute are shared by every tenant on the data plane. A fault can affect all of them, so quotas are kept low.
  • File sharing never grants access to the folder; your role also needs access.
  • Agents read the same files with the MCP document tools search_documents and get_document. They see exactly the files you can open here, because both surfaces use the same access rules. Files are added from this page.

Documents folder access

The Settings → Documents access page works in tenants that use governance-managed Documents access. Elsewhere, Dippr support sets folder access; ask your tenant admin. If the page says Folder access for this workspace is set up by Dippr support, your tenant uses support-managed folder access. This is an access policy, and reloading the page does not change it. In governance-managed tenants, a tenant admin with permission to manage roles can choose a folder and review its direct role grants. Select a custom role and an access level, then choose Save: Identical-upload reuse requires an updated Dippr CLI. Older CLI versions continue to add a new copy when the same file is uploaded again. Built-in roles cannot be changed here. Create a custom role under Settings → Roles & permissions, then give it folder access. Give people this role opens Settings → Users, where you assign it to people in your tenant. Save replaces the selected role’s allowed access for that folder with the chosen level. An identical save changes nothing. Deny grants appear as No access and are left unchanged; if one blocks the chosen level, review it before saving. Revoke removes the selected grant. Removing View also removes that role’s Add files and Manage grants on the folder, after you confirm. The list shows direct grants, so people may also have access through another role or inheritance. Changes take effect within about a minute. Folder access lets people open files shared with them in that folder; it never opens files that are not shared with the person. Adding or managing files also requires the View grant. Access through other roles or inherited roles is unchanged. In governance-managed tenants, sharing offers people only: group and Everyone at domain choices are hidden. Where those sharing modes are available, file sharing still requires folder access. To inspect a role’s direct grants from the command line, use dip governance list --role finance_readers. Add --json to include the identifiers you need to revoke a grant later.

Add a local file with dip

Run dip doc upload policy.md --folder policies with your dip login session to add a file as yourself, into a folder you may add to. Documents must be enabled for your tenant and your login needs documents:write and separate documents:share_uploads consent. Older logins open the browser for that additional approval. Existing uploader-only credentials remain private, including after refresh. API keys cannot upload. By default, adding identical bytes to the same folder reuses your own indexed file if you can still read it, even if you rename the file. The result is unchanged with the existing document ID; its sharing and classification stay unchanged. Another person’s file is never reused. On tenants using Documents access, a tenant admin can turn off Reuse identical files added by agents for the selected Data plane for agent uploads under Settings > Documents access. Changed bytes create a separate document. If you already have a readable file with the same name in that folder, the upload says “An older document with that name exists in this folder.” This name check is case-sensitive and also applies when reuse is off. Console uploads and Replace keep their existing behavior. Simultaneous uploads can still create duplicates before either file finishes indexing. Capacity checks happen before reuse, so even an identical retry can be refused when Documents is full. Agent uploads use your default classification for the folder. On tenants using Documents access to manage folder permissions, with sharing approved, sharing is queued by default for people the folder-access policy identifies as readers at admission, then checked again before publication. Later readers do not automatically gain access. The policy projection must have been successfully fetched within 60 seconds; permission changes may take longer to appear. A tenant admin using this setup can turn this off under Settings > Documents access. Select the Data plane for agent uploads first: these preferences apply only to that plane. Review each plane separately, including planes selected by dip doc upload --plane. Folder access grants apply across the tenant. New agent uploads on the selected plane are then shared only with you while you retain folder and classification access. Existing files are unchanged. On the earlier, support-managed Documents setup, new agent uploads stay private to you while you retain folder and classification access, even with sharing approved. The upload returns a note explaining that automatic sharing is unavailable. You can choose sharing in Documents using Share… from the file’s row menu. On tenants using Documents access, new uploads are refused if the resulting audience exceeds 50 people or the reader policy cannot be read. Reusing an existing file does not share it again. Uploads are refused if their settings cannot be read. When the audience is too large on a tenant using Documents access, ask an admin to disable automatic sharing on the upload’s data plane under Settings > Documents access, or upload and share in the console. Console uploads keep their chosen sharing. For a new file, report the returned sharing note: queued sharing is not proof of publication or searchability. After publication, Documents reports whether the file is visible to eligible admitted readers, only you, or nobody, and whether the audience narrowed. Notes reveal no reader names or counts. New files are queued for indexing; confirm they can be found with dip doc search "policy" --folder policies after indexing finishes. See dip doc upload for file types and limits. To add a local file to Documents, use dip doc upload from a terminal: a chat client cannot hand MCP a local file.

What if Documents is unavailable?

If Dippr cannot verify the saved access information for your documents, it refuses reads and uploads. An unavailable response does not mean your folder is empty. Contact your tenant admin, who can ask the platform operator to restore the saved access information. Refreshing the page or uploading another file cannot restore it.