> 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/integrations/document-management/sharepoint.md). # SharePoint With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from SharePoint and, when **Write** access is enabled, perform approved actions in SharePoint. Connect SharePoint when client documents are stored in Microsoft 365 sites and document libraries. Filed can access only the SharePoint content that the Microsoft account you authorize can already open. Site membership, library permissions, sensitivity labels, conditional-access policies, and Microsoft 365 administrator controls remain in effect. ## Before you connect Use a firm-managed Microsoft 365 account with access to the specific SharePoint sites and document libraries your team intends to use. Confirm the account can: * Open the relevant SharePoint site and library in a browser. * View the client folders and files you expect Filed to use. * Create or edit files in those libraries if write actions will be enabled. * Complete your organization's Microsoft sign-in, multi-factor authentication, and conditional-access checks. For a Microsoft 365 tenant with strict app controls, ask a Microsoft administrator to confirm that the Filed OAuth application and its requested Microsoft Graph permissions are allowed. A successful sign-in does not override tenant consent or site policy. ## Create the connection 1. Open **Plugins & integrations** and select **SharePoint**. 2. Give the connection a clear, durable name, such as `US Tax SharePoint` or `Acme Client Library`. 3. Review the connection permissions: * **Read** is always enabled and allows Filed to retrieve information from SharePoint content the authorized account can access. * **Write** is enabled by default. Clear it to make the connection read-only. You can change it later from the connection settings. 4. Select **Continue** to begin Microsoft authorization. ## Authorize Microsoft 365 1. Sign in with the Microsoft work account that has the required SharePoint access. Do not use a personal Microsoft account unless the relevant SharePoint content is intentionally owned there. 2. Complete your organization's multi-factor authentication or conditional-access steps. 3. Review and accept the requested permissions if your organization permits the application. 4. Return to Filed and wait for the connection to verify as **Active**. If Microsoft shows an administrator-approval message, send that request to your Microsoft 365 administrator. Do not try to work around it with a broader or unrelated account. ## Verify the connection After the connection is active, check a known site and document library that the authorized account should be able to open. For any workflow that writes content, test in a non-production folder first. SharePoint permissions can differ at the site, library, folder, and file levels. Verify the exact target location rather than assuming that access to one site provides access to all sites. ## Manage write access Turn off **Write** in the connection settings to make the connection read-only. Filed can still retrieve information from SharePoint, but it cannot use write capabilities such as creating, uploading, moving, renaming, updating, or deleting content. Use read-only access for document discovery, review, or context gathering. Enable write only when your firm has approved Filed to change SharePoint data and the connected account has the required permission in the target library. ## Reconnect or remove the connection Use **Reconnect** after Microsoft authorization is revoked, a password or multi-factor method changes, the user's role changes, or the connection shows pending or failed. Reconnect with the correct firm account and verify the intended site afterward. Use **Remove** only when the connection should no longer be used in Filed. Removing a connection never deletes SharePoint sites, libraries, or files. ## Troubleshooting ### Microsoft says administrator approval is required Your Microsoft 365 tenant requires administrator consent for the application or its requested permissions. Ask a tenant administrator to review the request. The person approving should understand the intended sites and data scope before granting consent. ### The connection is active but a SharePoint site or library is missing Open the site and library as the authorized Microsoft user. If it is not available there, Filed cannot access it. Add the user to the site or grant the correct library permission, then reconnect or retry the operation. ### Filed can read files but cannot change them Confirm that **Write** is enabled in Filed. Then check the connected user's permission in the exact SharePoint library or folder. Read-only access, a restrictive sensitivity label, retention policy, or a library-specific permission can prevent changes even when the user can browse the site. ### A personal Microsoft account opens instead of the work account Sign out of Microsoft in the authorization window and restart the connection. Choose the organization's work account. If the browser keeps selecting the wrong account, use a private browsing window or ask the user to clear the active Microsoft session. ### The connection fails after a policy or role change Conditional-access policy, tenant consent, site membership, or licensing may have changed. Reconnect after the Microsoft administrator confirms the user still has both app authorization and access to the intended SharePoint locations. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding SharePoint information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with SharePoint data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the SharePoint folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. --- # 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/integrations/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.