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

# File manager

Centralize in the Dastra file manager the documents that prove your compliance: document creation, folders, access rights and cloud storage.

Dastra natively integrates a file manager, also called GED (electronic document management) in French. It centralizes and shares access to all the documents associated with your work in Dastra. You find the module under **Resources** > **File Manager** in the left menu.

This is where you can store all the documentation that helps prove your GDPR compliance.

{% hint style="info" %}
**Focus on GDPR documentation**

The documentation requirement stems from the **accountability principle** set out in Article 24 of the GDPR.

In practice, this goes beyond the record of processing activities and includes (non-exhaustive list):

* Internal procedures for creating new personal data processing activities
* DPIA methodology and completed assessments
* Written data protection policies
* Data mapping and inventory procedures
* Training records for staff involved in data processing
* Data subject rights management procedures
* Internal complaint handling mechanisms
* Data breach management and notification procedures
* Internal or external audit reports and findings
* Contract documentation for processors and joint controllers
  {% endhint %}

## Accepted file formats

Many formats are supported:

* PDF
* Word (.docx)
* Excel (.xlsx)
* Images (JPG, PNG, etc.)
* Archives (.zip)
* And more

If a format is not accepted, put the file in a `.zip` archive and upload that instead.

## Create a document

You can write a document directly in Dastra, for example to take notes. In the file manager, click **Write a document**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-6118ea0c386c0fb04a7be2d4039640d38718ddc3%2Ffiles-1.png?alt=media" alt="The file manager toolbar with the Write a document button"><figcaption><p>The Write a document button</p></figcaption></figure>

Enter the label of the document, then its content in the Markdown editor. The document is saved in Markdown format (.md).

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0181a97f71ef0bdec4f896b7dc7359b3983e7073%2Ffiles-2.png?alt=media" alt="The document editor with the Generate with AI button"><figcaption><p>The document editor</p></figcaption></figure>

### Generate a document with AI

The AI assistant can **generate a document** from a description and, if needed, files or a website address provided as context.

To use it, click **Write a document**, then **Generate with AI** in the editor. Briefly describe the document you need (type, purpose, expected content) and optionally add files to enrich the context. The generated text appears in the editor: review it, edit it and save it. The button is only active if the AI assistant is available in your subscription.

{% hint style="info" %}
This feature is useful to draft a first version of a data protection policy, an internal procedure or any other compliance document.
{% endhint %}

## Create a folder

Organize your documents in folders so you can find them. Click **Create folder**, name it and choose its location: sub-folders are supported.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-b90664aa781432d4aa7a1ee4ed60d98cc0f0fb59%2Ffiles-3.png?alt=media" alt="The folder creation window"><figcaption><p>The folder creation window</p></figcaption></figure>

## Manage access rights

You can restrict access to folders and files. Rights apply to folders as well as files. They are configured by the workspace administrator or by a user allowed to manage files.

{% hint style="info" %}
By default, no restrictions are applied to the folder tree. The permissions linked to the user's roles still apply.
{% endhint %}

On the row of a folder or a file, click the **File access** button, then add the teams and users with the permission level you want.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d7cc02afbdde90dc1e8daf572d43e4c3db681289%2Ffiles-4.png?alt=media" alt="The window to manage the access rights of a folder"><figcaption><p>The access rights window</p></figcaption></figure>

These permissions apply to all child elements, that is, everything the folder contains, sub-folders included.

{% hint style="info" %}
A folder with no defined permissions is accessible to all users.

If permissions are defined or inherited on an element, it is hidden from users who do not have the required authorizations.
{% endhint %}

## Files from other modules

The files attached to processing activities, assets, stakeholders and contracts can be stored in the file manager, in a dedicated folder. They are then visible to all the users allowed to view files: you need to manage access to the folders.

To choose this default behavior, click **Workspace settings** > **General**, then, in the **File manager** card, turn on **Upload files in GED by default**. If you turn the option off, files stay attached to their item and do not appear in the file manager, which can make access management simpler.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a810d69b5e04e77240b3b4d8cb0e66ef12be9078%2Ffiles-5.png?alt=media" alt="The File manager card in the general settings of the workspace"><figcaption><p>The option to upload files by default</p></figcaption></figure>

Users who can manage files have three additional commands:

* **View files not in file manager**, in the **Filters** menu of the file manager, lists the files that are not stored there.
* **Move to common file manager** moves a file into the file manager, in the folder of your choice.
* **Remove from common file manager** takes the file out of the file manager: the file is kept, but other users can no longer discover it.

## Cloud storage

By default, Dastra stores files on Azure Blob Storage: they are encrypted, scanned for viruses and redundant. You can also connect your own storage, Microsoft OneDrive & SharePoint or Google Drive, to avoid duplicating files between systems.

{% content-ref url="/pages/PegGKkTG4A3mU87iPMCC" %}
[OneDrive & SharePoint / Google Drive integrations](https://doc.dastra.eu/en/features/settings/cloud-storage.md)
{% endcontent-ref %}

## Document templates

Dastra provides ready-to-use document templates to help you build your compliance documentation.

{% content-ref url="/pages/6b59gnfGL9tmvhqPHAJV" %}
[Document templates](https://doc.dastra.eu/en/features/files/templates.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.dastra.eu/en/features/files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
