> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/document-management/sharepoint.md). # SharePoint ## What this integration does The SharePoint integration gives Filed direct access to client documents stored in a SharePoint site, without manual uploads. You designate one folder within a SharePoint drive as the root; sub-folders inside it map one-to-one to client records in Filed. Once clients are imported, Filed can read, organize, and write files within each client's SharePoint folder, so your team can file documents back to SharePoint directly from Filed. SharePoint is the most capable of the five DMS integrations. Beyond the standard file lifecycle actions, it adds: * **Version history** with the ability to restore earlier versions of a file * **Granular permission management** on individual items * **Sharing links** scoped to view, edit, or embed access During the connection flow, Filed requests these Microsoft OAuth scopes: * Read and read-write access to SharePoint sites and all files (`Sites.Read.All`, `Sites.ReadWrite.All`, `Files.Read.All`, `Files.ReadWrite.All`) * Basic user profile access (`User.Read`) * Offline access so tokens can be refreshed without repeated sign-ins (`offline_access`) ## Before you start You need a Microsoft account with at least contributor-level access to the SharePoint site and the folder containing your client sub-folders. Read-only access is not sufficient: filing documents back to SharePoint and managing permissions require write access. The top-level folder must be organized with one sub-folder per client at the immediate first level. ## Connecting SharePoint to Filed {% embed url="" %} {% embed url="" %} ## Importing clients from SharePoint ## What Filed can do with SharePoint Once connected, Filed exposes the following actions against your SharePoint site: **Browsing and finding files** * List available drives on the SharePoint site * Retrieve metadata for a specific drive * Browse the children of any folder within a drive * Search for items across a drive by name or keyword * Retrieve metadata for a specific file or folder **Managing files and folders** * Download the content of a file * Upload a file to a folder * Create a new folder * Copy a file or folder to another location * Update a file or folder's name, description, or parent folder * Delete a file or folder **Version history** * List all saved versions of a file * Restore a file to a previous version **Permissions** * List permissions on a file or folder * Add a permission granting a user or group access to an item * Update an existing permission * Remove a permission from an item **Sharing links** * Create a sharing link for a file or folder, scoped to view, edit, or embed access, and limited to anonymous or organization-level recipients These capabilities power binder creation and update: when Filed prepares a client's binder, it uses this action set to retrieve source documents from SharePoint and to file completed documents back. ## Troubleshooting **Connection error on the DMS page.** Verify that the Microsoft account you used still has contributor access to the SharePoint site. Read-only accounts cannot complete the permission grant that Filed requires. Disconnect and reconnect, signing in with a contributor-level account. **Clients are not appearing after import.** The top-level folder you selected must contain sub-folders at exactly one level deep, one per client. If the folder structure does not match, reconnect and select the correct folder. **Permission errors when filing documents back.** Verify that the connected Microsoft account still has write access to the relevant SharePoint site. If your organization's SharePoint permissions were changed after the initial connection, you may need to reconnect with an account that holds the required access level. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/plugins/document-management/sharepoint.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.