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

# Share the record of processing

Learn how to share the record of processing.

A sharing link gives external users read access to your record of processing activities, or to some of its processing activities, without a Dastra account. Sharing requires the **Advanced configuration** permission.

{% hint style="info" %}
The sharing link is publicly visible: anyone who has it can open it until it expires. Be careful about how you distribute it, and for security reasons, keep an eye on the sharing links exposed in your workspace.
{% endhint %}

## Sharing the entire record

From the **Record of processing activities** module, click the arrow next to the **Create data processing** button, then **Share**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-91125ec0abbaf92ab72639cd7d68c361e24277f7%2Fropa-share-1.png?alt=media" alt="Share entry in the Create data processing menu"><figcaption><p>The Share entry of the Create data processing menu</p></figcaption></figure>

The **Whole record sharing link** window opens:

1. Select the **Expiration time of the link**.
2. In **Do you want to notify users?**, choose **Yes** to send the link by email, then enter the **Recipient e-mails** and, optionally, a **Personalized message**.
3. Click **Create link**.

The sharing only includes the processing activities with the "Published" status. Draft processing activities are not shared with this function: to share a draft processing activity, share it individually (see below).

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-b1c6ed9e646d1339e6b01addb2c3816629b8e5ea%2Fropa-share-2.png?alt=media" alt="Whole record sharing link window"><figcaption><p>The Whole record sharing link window</p></figcaption></figure>

The available lifetimes of the links are:

* 2 days
* 30 days (default)
* 120 days
* Unlimited

Once the link is created, it is copied to your clipboard. The window then offers two sections:

* **Direct link**: copy the link with **Copy link**, or open it with **Link**;
* **Integration (embed)**: set the **Embed width** and **Embed height**, then copy the code to embed the shared record in another website, such as your intranet.

Click **Close** to close the window.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-65f7aeafc69bd893400309e5c0fa398ab58a0ff9%2Fropa-share-3.png?alt=media" alt="Sharing link created, with the Direct link and Integration sections"><figcaption><p>The sharing link once created</p></figcaption></figure>

## Generation of a sharing link for data processing

To share a single processing activity, open the action menu at the end of its row in the list, then click **Share**. The **Sharing link generation for 1 element** window opens: proceed as described above.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-99c69d596c4e468477465c9db6f358a4e0116828%2Fropa-share-4.png?alt=media" alt="Share entry in the action menu of a processing activity"><figcaption><p>The Share entry of the action menu of a processing activity</p></figcaption></figure>

You can also share a processing activity from its record: click the arrow next to the **Save changes** button, then **Share**.

To share several processing activities, select them in the list, click **Select a batch action**, then **Share**.

Processing activities shared this way can be shared whatever their status (published or draft). Processing activities in the recycle bin cannot be shared.

## Manage share links

All the sharing links created in your workspace are centralized in the workspace settings, under **Sharing links**.

For each link, the list shows the link itself (which you can copy), the user who created it, the type of shared items and their number (**All** for a whole record), the creation date, the expiration date and the recipient emails. You can filter the list by **Type**, and click **Delete** to remove a link that should no longer be used.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a731837f1589d084b2c7bfc6bed6aad19c3e57e4%2Fropa-share-5.png?alt=media" alt="Sharing links in the workspace settings"><figcaption><p>The Sharing links settings</p></figcaption></figure>


---

# 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/ropa/share.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.
