> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/settings/integrations-onedrive-google-drive.md).
# OneDrive/Google Drive integrations
## Why use custom cloud storage?
By default, Dastra's [document management system](https://github.com/Dastrateam/dastra-doc-en/tree/main/features/gestion-de-documents-ged/README.md) relies on Azure Blob Storage: files are encrypted, scanned for viruses, and redundantly stored on a secondary server. For more details, see the [security documentation](/en/security/general.md).
In some organizations, this storage duplicates an existing cloud file system (SharePoint/OneDrive, Google Drive). Dastra integrates natively with both providers to avoid this duplication.
Files can be stored in Dastra, OneDrive, or Google Drive
## Connection type: user OAuth
{% hint style="warning" %}
This integration uses **OAuth authentication with a user account's credentials**. It is not an application-level connection via the Microsoft Graph API or the Google API.
In practice, this means:
* The connection is established **on behalf of the user** who configures the integration
* Access to files depends on **that account's permissions**
* If the account is deactivated or its tokens revoked, the integration stops working until it is reconnected
* It is recommended to use a **dedicated service account** (non-personal) to configure this integration
{% endhint %}
## Setting up the integration
Go to **Workspace Settings > Integrations**, then click on **OneDrive** or **Google Drive**.
Click **Add integration**. You will be redirected to the provider's login page, where you will be asked to authorize access to your storage.
### Choosing the root drive (OneDrive only)
After authentication, Dastra asks you to choose which drive to use as the root:
| Option | Description | Recommendation |
| ----------------------- | ------------------------------------------ | ------------------------------------------------------------------------------- |
| **Root site / Dastra** | Organization's SharePoint site | ✅ Recommended for enterprise use — shared space, not tied to a personal account |
| **Your personal drive** | Personal OneDrive of the connected account | ⚠️ Avoid in production — grants access to all personal drive files |
{% hint style="info" %}
If you use a personal drive, it is strongly recommended to use a dedicated service account that does not contain personal files. You can also create a [dedicated SharePoint site](https://learn.microsoft.com/en-us/sharepoint/create-site-collection) to isolate Dastra files.
{% endhint %}
Dastra automatically creates an **Applications\DastraOneDrive** directory on the chosen drive, which it uses as the root for all files.
## Attaching cloud files to a Dastra entity
From any entity (processing activity, task, actor…), you can attach files stored in your cloud:
1. Open the file panel of the entity
2. Select the **data source** at the top left of the panel
3. Browse your drive via the file manager
4. Click **Select from manager** to attach the file
You can also upload new files directly from Dastra to your Drive.
## Limitations
### OneDrive
* The connection uses user OAuth — not the Microsoft Graph API. If the account that set up the integration is deactivated, the connection is interrupted.
* Dastra only has access to the **Applications\DastraOneDrive** directory on the chosen drive.
* For enterprise environments, prefer the SharePoint site ("Root site / Dastra") over a personal drive.
### Google Drive
* Only files **created from within Dastra** can be added or modified in Google Drive. Dastra does not have access rights to files created directly in Drive — this is a limitation of the OAuth connector.
* Files created in Dastra can be shared with other collaborators without restriction.
---
# 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://doc.dastra.eu/en/features/settings/integrations-onedrive-google-drive.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.