# Notifications

### 🧭 Overview

Notifications in Dastra keep you informed of important activities related to your processing activities, questionnaires, tasks, or data subject requests.

There are **two types of notifications**:

1. **The notification centre** — built directly into the application
2. **Email notifications** — customisable according to your preferences

***

### 🔔 Notification centre (in-app)

The notification centre groups all alerts accessible via the **bell icon** at the top right of your screen.

* Accessible to all workspace users
* Not customisable (shared across the workspace)
* Contains general notifications about recent activity: creation, modification or deletion of elements

<figure><img src="/files/MmntxVq9nChHxwpkUcCI" alt=""><figcaption><p>Notification Centre</p></figcaption></figure>

{% hint style="info" %}
Example: "A new processing activity has been created in your workspace."
{% endhint %}

***

### ✉️ Email notifications (customisable)

Each user can choose which notifications to receive by email from their user profile.

#### 🔧 How to customise your notifications

1. Click on your **avatar** at the top right of Dastra
2. Select **Notification Centre**
3. Enable or disable categories according to your needs
4. Save your preferences

<figure><img src="/files/4SehdQ7r0vZR0XlUfYV1" alt=""><figcaption><p>"Notification Centre" button</p></figcaption></figure>

{% hint style="info" %}
Email notifications are ideal for being alerted to actions requiring a quick response (questionnaires, requests, data breaches, etc.)
{% endhint %}

***

**🔐 Prerequisite: the "Notification" permission in the role**

Email notification customisation only works if the user's role allows it.

In the role configuration (**Settings → Roles**), each module has a **Notification** checkbox. If this box is not checked, users with that role will receive no email notifications for that module — regardless of their personal preferences.

{% hint style="info" %}
The role opens or closes the right to receive notifications. The user can then refine their preferences — but only within the limits of what their role allows.
{% endhint %}

### 📚 Notification categories

Email notifications are organised by **categories**. Each category contains several individually configurable event subtypes.

| Category                         | Example notification                            | Customisable? |
| -------------------------------- | ----------------------------------------------- | ------------- |
| **Processing activities**        | A processing activity has been modified/deleted | ✅             |
| **Data subject rights requests** | A new request has been assigned to you          | ✅             |
| **Data breaches**                | A breach has been reported or closed            | ✅             |
| **Tasks**                        | You have been assigned to a task                | ✅             |
| **Questionnaires**               | A response has been validated or rejected       | ✅             |
| **Questionnaire templates**      | A template has been updated                     | ✅             |
| **Comments**                     | Someone has mentioned you (@)                   | ✅             |
| **Cookie consent**               | A change has been made to the consent banner    | ✅             |
| **Reports / analyses**           | A new report is available                       | ✅             |
| **Marketing / Push**             | Product communications or Dastra news           | ✅             |

For each category, you can also configure the specific event subtypes. For example, for processing activities:

* Modification of a processing activity
* Change of status of a processing activity
* Deletion of a relationship to a processing activity

<figure><img src="/files/t9cZvk65OZBkttlALn8E" alt=""><figcaption></figcaption></figure>

And for questionnaires:

* Questionnaire response rejected
* Questionnaire response validated
* Invitation to respond to a questionnaire
* Questionnaire annotation added

<figure><img src="/files/8Qv8MKZajiKUCA3tzKdE" alt=""><figcaption></figcaption></figure>

***

### ⚠️ Automatic notifications

Some notifications are considered **systemic**: they are sent automatically, even if you have disabled the corresponding category.

These notifications are deemed essential to collaboration:

* Invitation to a **questionnaire**
* **Assignment** to a task or request
* **Direct mention** in a comment (@your-name)
* Invitation to complete a **processing activity record**
* Immediate sending of a **scheduled invitation** (if the option is enabled)

***

### 💬 Best practices

* Enable emails for activities requiring action on your part (questionnaires, DSR, data breaches).
* Check the **bell** regularly for overall workspace monitoring.
* Check your **"Notifications" folder** in your mailbox if you think you are no longer receiving certain messages.
* For a DPO: enable all categories.
* For a contributor: prioritise tasks, comments and questionnaires.

***

### ❓ FAQ

#### I am no longer receiving my notifications — what should I do?

Check your preferences in your **user profile → Notification Centre**. Also make sure that Dastra emails are not being redirected to your "Promotions" or "Spam" folder.

{% hint style="info" %}
Note: you do not receive notifications for actions that you perform yourself.
{% endhint %}

#### Can I receive a monthly summary?

You can receive a monthly summary of your workspace activity. Click on the notification: **Preferences: subscribe to the monthly report**.

***

### 🔗 See also

* [Manage roles and permissions](/en/features/settings/roles-et-permissions.md)
* [Monitor your questionnaires](/en/features/audit.md)


---

# Agent Instructions: 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:

```
GET https://doc.dastra.eu/en/features/settings/notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.