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

# Filerskeepers

Filerskeepers integration to synchronize the retention periods of your Dastra datasets with your Filerskeepers repository.

### What is Filerskeepers?

[Filerskeepers](https://www.filerskeepers.co/) is a service that provides **ready-to-use data retention schedules**, covering legal retention requirements from all around the world.\
It helps companies **determine how long to keep or delete each type of data** in order to remain compliant with applicable regulations.

### Prerequisites

* Have a paid Dastra license
* Have a Filerskeepers account. If you don’t have one yet and you are already a Dastra customer, you can [contact our sales team](https://meetings-eu1.hubspot.com/yann-forveille/rendez-vous-avec-un-expert?message=Filerskeepers+Integration), who can offer you preferential pricing.
* Have set up a data retention repository (“Schedule”) in the Filerskeepers software. The integration requires this repository to access your catalog data.

{% hint style="info" %}
Using the connector is subject to the Filerskeepers terms of use. The data provided by Filerskeepers is for internal use only within your organization: it cannot be copied, exported, shared or used commercially. Filerskeepers credentials can only be linked to one Dastra organization. If the service ends, you must delete all Filerskeepers data. Dastra is not responsible for the content or updates coming from Filerskeepers.
{% endhint %}

### Installation

The installation follows the common integration flow (see [Connections, use cases and field mapping](https://doc.dastra.eu/en/features/integrations/connections.md)):

1. Open **Workspace settings** > **Integrations** and select **Filerskeepers**.
2. On the datasets use case, click **Add integration**.
3. In the **Connection** step, choose **Add a connection**. Enter the **Email** and the **Password** of a Filerskeepers administrator account, then click **Connect**. Dastra uses these credentials to get an access token for the Filerskeepers API.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d437faf093f100042bfa1cc2bca274b5d72ac2e6%2Fintegrations-filerskeepers-1.png?alt=media" alt="The Connection step of the Filerskeepers installation, with the Email and Password fields"><figcaption><p>Connecting to Filerskeepers</p></figcaption></figure>

4. In the **Configuration** step, select the Schedule to synchronize with Dastra. This step is required to finish the installation.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2FhXLAhAAh5IYBVIXGKXIA%2Fimage.png?alt=media&amp;token=4a46bbf1-e3b4-4442-8581-e8cf742fd977" alt="The Filerskeepers Configuration step"><figcaption></figcaption></figure>

### Configuration

Reopen the configuration from the use case menu, **Project configuration** entry.

* **Select the filerskeepers Schedule you would like to sync** (required): the Filerskeepers schedule to synchronize with Dastra.
* The switch that keeps the retention periods synchronized: when on, the datasets synchronized with Filerskeepers are updated once a day.
* **Users to notify in case of creation/update of datasets** (required when synchronization is on, 10 at most): these users receive an email listing the datasets that were created or updated.
* The switch that creates the missing datasets: when on, it creates a dataset for every data type declared in your Filerskeepers account.
* The optional jurisdiction selector, shown when dataset creation is on: it chooses the jurisdiction synchronized for the created datasets. When no jurisdiction matches, Dastra uses the reference retention period (Golden standard).

{% hint style="warning" %}
If you turn on dataset creation, a large number of datasets are created automatically in your workspace.
{% endhint %}

#### Run a synchronization

To synchronize without waiting for the daily run, open the use case menu and click **Run synchronization now**. A synchronization started by hand creates the missing datasets, even when the creation option is off.

**View logs**, in the same menu, lists the past runs and their result.

### Selecting the retention policy

The Filerskeepers connector offers several modes of operation:

* Display of the retention period selector based on your Filerskeepers retention repository (called “Schedule” in the software).

From now on, when you open a dataset in Dastra, in the “Retention Policies” section, a button to select a retention policy will appear.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2F8d0ZJmwoS4AyrDD2d2ON%2Fimage.png?alt=media&amp;token=840b92a0-8644-48e6-b0ea-61e97b25c19b" alt="The Pick from filerskeepers schedule button in the retention period editor of a dataset"><figcaption><p>Picking from the Filerskeepers schedule</p></figcaption></figure>

By clicking this button, you can directly select a dataset from your Filerskeepers repository. **This retention period will be automatically synchronized** with Dastra if you enabled this option in the integration configuration.

Select a dataset by clicking the **"Select"** button.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2F2c5km5mVf99PCF5NT92c%2Fimage.png?alt=media&amp;token=78a0fc12-a9aa-4af0-9dd6-511f4fd1e2cb" alt="The table of retention periods of the Filerskeepers schedule, with a Select button on each row"><figcaption><p>Table of retention periods in the schedule</p></figcaption></figure>

Once you have selected the retention period, the window will close and the retention period details will be displayed.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fo1hzI2MsrBRs1dqcAp8b%2Fimage.png?alt=media&amp;token=aad4a548-a4d3-4ca1-9d28-48641d859903" alt="A retention period synchronized with Filerskeepers, with its last update date"><figcaption><p>A synchronized retention period</p></figcaption></figure>

{% hint style="info" %}
Only retention periods related to active data stores will be synchronized.
{% endhint %}

### How are data synchronized between Dastra and Filerskeepers?

A number of fields from Filerskeepers are automatically mapped to your retention period:

* **The retention duration** (from)
* **The description of the retention policy**
* **The legal justification, link, and jurisdiction**, which are concatenated into the justification field


---

# 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/integrations/filerskeepers.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.
