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

# Set up a data subject right request widget

Add a customizable data subject request form to your website: appearance, fields, languages, texts and integration modes.

The Dastra widget adds a data subject request form directly to your website. In the application, you manage it under **Requests** > **Forms**: click **Create form** to add one.

You can customize it in five ways:

* **General settings**: the request types offered, redirections and the privacy policy link.
* **Visual customization**: colors, logo, background image, icons, font and progress bar.
* **Fields**: standard and custom fields, required or optional.
* **Integration modes**: in a page, in a modal window (popup), in an iframe or on a dedicated web page.
* **Multilingual**: translate and adapt every text of the widget.

***

## Integration workflow

The diagram below shows how a data subject request widget works in Dastra:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2FRy0rRcI6zGkrb9cmXXku%2Fimage%20(98).png?alt=media&amp;token=f6dec31c-7301-4834-86c6-315bc026b191" alt="Sequence diagram: the data subject submits a request through the widget and validates their email address, then Dastra notifies users, who process the request and reply in the requester space"><figcaption><p>The journey of a request collected through the widget</p></figcaption></figure>

The process is as follows:

1. The data subject submits a request through the widget.
2. The request is sent to Dastra and recorded.
3. You are notified and can qualify and process the request in the platform.
4. The data subject receives an answer in the requester portal.

***

## General settings

Open a form and go to the **Settings** section. You define:

* The **Name** of the widget and its **Organizational unit**.
* The available request types, with the question **Which rights are concerned?**: **Default rights**, **Specific rights** (you then pick the types in **Choose specific request types**) or **No rights (simple form)**, which does not ask the person to choose a request type.
* The links **Redirection link in case of success (after the identification phase)**, **Redirection link in case of an error (e.g. validation link expires)** and **Link to the privacy policy**. All three links are optional.
* **Enable phone validation**, shown only when [requester verification by SMS](https://doc.dastra.eu/en/features/requests/advanced/requester-space.md#verify-the-requester-by-sms) is on in the workspace: the phone field becomes required and the number is verified by SMS after the email address is validated.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-7322a61c68a2a0688388042a32fcd0bedb715e74%2Frequests-widget-2.png?alt=media" alt="Settings section of a form: name, organizational unit, request types and redirection links"><figcaption><p>Widget settings</p></figcaption></figure>

***

## Customizing the appearance

The **Templating of the form** section adapts the form to your brand. The preview updates as you edit.

Available options:

* **Logo**, and **Background image** (offered with the **Background image** header layout or with the dedicated web page mode).
* Colors: **Primary color**, **Secondary color** (with the **Default** header layout), **Titles color**, **Color text** and **Muted color**.
* **Header layout**: **Default**, **Flat**, **Background image** or **No header**.
* **Box shadow**: **Large**, **Standard** or **No shadow**.
* **Icon layout**: **No icons** or **Standard icons**.
* **Display progress bar**.
* **Font family name**: the name of a font installed on your website.
* **Custom CSS**, for advanced users.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d63a2a38dbe588dd2a9620982fd2825371e9073f%2Frequests-widget-3.png?alt=media" alt="Templating of the form section with the form preview and the customization options"><figcaption><p>Adapt the appearance of the widget</p></figcaption></figure>

***

## Customizing the fields

The **Form customization** section lists the **Active fields** on the left and the **Available fields** on the right. Click an available field to add it, drag the active fields to change their order and click an active field to edit it.

* The email address is always present. By default, the form also asks for the first name, the last name, the reference of the requester and the message.
* You can add standard fields: **Phone number**, **Address**, **Zip code**, **City**, **Country code**, **Request files** and **Category of data subject**.
* You can add your own **custom fields**, created in the custom fields of requests.
* Each field has a **Required** switch.
* For the **Category of data subject** field, click **Configure categories** to choose the categories offered to the person.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-969470b3f336ca9da09c402260d80b3b3e00c409%2Frequests-widget-4.png?alt=media" alt="Form customization section with the active fields and the available fields"><figcaption><p>Customize the fields available in the widget</p></figcaption></figure>

***

## Conditional logic (skip logic)

For each field, you choose when it is displayed: **Display always**, **Afficher en fonction du type de demande** or **Custom display conditions**. With custom conditions, a field appears only if the answer to a previous question meets a defined condition.

The operators offered depend on the field type, as in workflow rules:

* comparisons (less than, greater than and their inclusive variants) for numbers and dates;
* "is in" and "is not in" for drop-down lists and radio buttons;
* "contains all", "excludes all", "is empty" and "is not empty" for checkboxes;
* presence or absence of a value for optional fields.

The form preview applies these rules. They are interpreted dynamically on the respondent side: the form adjusts in real time as answers are entered.

You can then:

* Show or hide fields depending on the type of right exercised, the nature of the request, or any previous answer
* Manage multiple scenarios within a **single widget**, without creating and maintaining a separate form for each variant
* Reduce maintenance overhead when content evolves or compliance requirements change

***

## Installing the widget

The **Installation** section offers four integration modes, chosen with **Choose the layout of the widget**:

* **Block (recommended)**: an HTML snippet to place where the form should appear.
* **Modal**: a button opens the form in a window.
* **Page (With url)**: Dastra hosts a page and you share its URL, for example in your privacy policy.
* **Embedded in an Iframe**: an iframe to place in your page. The **Resize iframe automatically** option avoids a scroll bar; otherwise the height is fixed at 1000 px.

The code provided is an HTML snippet and a JavaScript script to insert on your site or in a tag manager (for example Google Tag Manager). For advanced options (language, prefilled fields, several widgets in one page), see [Technical integration](https://doc.dastra.eu/en/features/requests/integration.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-97c3ffc004792924e71b5c50e35f5f7afac82ec8%2Frequests-widget-5.png?alt=media" alt="Installation section with the four integration modes and the code to copy"><figcaption><p>Installation guide</p></figcaption></figure>

***

## Texts and translations

The widget is multilingual: in the **Texts and localizations** section, add languages with **Add a language** and customize the translations.\
The first language in the list is the default language: Dastra uses it when the person's browser language is not available.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-b78e5bb2fd03240ec4b083e62dbee0ed444aab99%2Frequests-widget-6.png?alt=media" alt="List of the widget languages with the default language"><figcaption><p>Customize the texts of the widget</p></figcaption></figure>

For each language, click **Edit** to open the texts, grouped in four sections (**General settings**, **Types of right**, **Contact form** and **Custom fields**). You can edit:

* The page name (for the dedicated web page mode).
* The messages shown before the privacy policy links.
* The text of buttons and instructions.
* The translation of data subject categories and custom fields (label, description, placeholder and options).

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0b4fb5a2dc1d77daa42e235c65222ecdbad47fc3%2Frequests-widget-7.png?alt=media" alt="Editing the texts of one language of the widget"><figcaption><p>Change part of the texts</p></figcaption></figure>

***

## Result for the data subject

Once configured, the widget lets data subjects select the type of right they want to exercise and submit their request.\
The form adapts to the configuration (languages, appearance, fields).

At the end of the form, the requester receives an email with a validation link and a 6-digit code, and enters the code in the form: **Enter the 6-digit code sent via email.** The request is only taken into account once the address is validated. See the [FAQ](https://doc.dastra.eu/en/features/requests/faq.md).


---

# 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/requests/widget.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.
