> 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/onedrive.md).

# OneDrive

With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from OneDrive and, when **Write** access is enabled, perform approved actions in OneDrive.

## Connect OneDrive

1. Create a **OneDrive** connection and name it for the Microsoft user or department.
2. Sign in with the user who owns, or is shared on, the required files.
3. Approve Microsoft consent and return to Filed for verification.
4. Test a known file before allowing write actions.

OneDrive access is limited to the connected user's files and items shared with them. Use SharePoint instead for files stored in a team document library.

## Verify the connection

After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm file ownership and sharing access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow.

## Manage permissions

Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying OneDrive data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change.

## Troubleshooting

**The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has file ownership and sharing access.

**The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review file ownership and sharing access, then reconnect if the account or environment was wrong.

**The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem.

## Using this integration with Filed Chat and Routines

Use **Chat** for one-off questions and guided work on a client, such as finding OneDrive information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with OneDrive 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 OneDrive 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/onedrive.md?ask=<question>&goal=<endgoal>
```

`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.