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

# Internal discussions

Internal discussions let you talk with the users of the platform, with mentions, quotes and notifications.

Internal discussions work like a chat attached to an element of Dastra: processing activity, data subject request, task, data breach, stakeholder, asset, dataset, data field, control point, risk assessment, contract, AI system, compliance project or audit, questionnaire response. Each element has a single conversation.

## How it works

1. Open the record of the element concerned.
2. Click the **Internal discussion** button, a speech bubble with the number of messages. The thread opens in a panel on the right.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-cc383c0c43a83b2c9d597f0d5f153ef555b6a157%2Fgeneral-discussions-1.png?alt=media" alt="Processing activity record with the Internal discussion button and the discussion panel open"><figcaption><p>The Internal discussion button and the discussion thread of a record</p></figcaption></figure>

3. Click the **Write a message** area and type your message. The **Add an attachment** button attaches a file, by click or by drag and drop.
4. Click **Send**, or press **CTRL+Enter**.

An unsent draft is kept in your browser and restored when you reopen the panel. You can edit or delete your own messages from their menu. An edited message shows **Last edit** followed by the date.

## Message layout

Messages are laid out like a chat, in the internal discussions as well as in the exchanges of a data subject request, on your side and in the requester space. Your own messages are on the right, in a light-blue bubble, with **Me** above. The name of another author is above their bubble, in the color of their avatar. The date and time of each message are under the bubble.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a06f2245cffff9018ce783202a91bd67b8bce129%2Fv3-interface-discussions-1.png?alt=media" alt="An internal discussion with messages in bubbles: own messages on the right in light blue, other authors on the left"><figcaption><p>The message layout in an internal discussion</p></figcaption></figure>

In the exchange with the requester of a data subject request, the requester's messages are headed **Data subject**. See [Requester space](https://doc.dastra.eu/en/features/requests/advanced/requester-space.md).

## Mentions

Mention the users concerned with the **@** character. A list of the users of your workspace appears and narrows as you type.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-cf6034a99fa0c406bd25a3fdce1f3934a2672d21%2Fgeneral-discussions-2.png?alt=media" alt="List of users suggested after typing the @ character in the message area"><figcaption><p>The list of users suggested after @</p></figcaption></figure>

A mention triggers an immediate notification to the user concerned.

## Quotes

You can reply directly to a specific message, to keep the context readable in a long thread.

1. Hover over the message you want to reply to and click **Reply**. This button is available on other users' messages.
2. A **Replying to** banner with the author's name appears above the text area, with a preview of the quoted message. Its author is mentioned automatically in your reply, which triggers their notification.
3. Type your message, add any attachments, then click **Send**.

To remove the quote while keeping your message in progress, click the trash icon of the banner. You can also remove the mention if you do not want to notify the author.

{% hint style="info" %}
A message can only quote one message at a time. The quote is kept if you edit your message afterwards.
{% endhint %}

Once published, the quoted message appears in a banner above your reply. If the quoted message is deleted later, the banner shows **This message has been deleted**: your reply stays visible.

## Notifications

For each new message, Dastra notifies:

* the users mentioned in the message, immediately;
* the people responsible for the element (for example its owner, its operator or the person it is assigned to, depending on the element type), except the author of the message.

The **Notified users** line under the input area shows how many people will receive your message and lists them. How each user receives notifications depends on their preferences: see the [Notifications](https://doc.dastra.eu/en/features/settings/notifications.md) page.

{% hint style="info" %}
If you use Slack, mentioned users can also be notified by the Dastra bot in Slack, provided their Dastra email address is the same as in Slack. See [Integrations](https://doc.dastra.eu/en/features/integrations.md).
{% endhint %}

## Opening and closing the conversation

As soon as a message is sent on an element with no ongoing conversation, or after a closure, the conversation is open. The **Internal discussion** button then shows a small red dot.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-e697b8cc4c18f56790d1c2ddf1fe30050e417150%2Fgeneral-discussions-3.png?alt=media" alt="Internal discussion button with a red dot for an open conversation and a green dot for a closed conversation"><figcaption><p>The red dot flags an open conversation, the green dot a closed one</p></figcaption></figure>

When the exchange is over, click **Close the discussion** at the bottom of the thread. This button is reserved for users who have the **Discussions** permission in their role. The dot turns green, and the thread shows **Discussion has been closed by** followed by the person's name. A user with the same permission can click **Cancel** to reopen the conversation.

## Conversation hub

The hub gathers all the conversations of your workspace. You can answer your users' questions there while accessing the records concerned.

To open it, click the speech bubble icon (**All discussions**) in the top bar. A red badge shows the number of open conversations.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-c7b26252cff22c9b93b44cd23248735e9e9ee350%2Fgeneral-discussions-4.png?alt=media" alt="Top bar with the All discussions icon and its badge, and the conversation hub page"><figcaption><p>The All discussions icon and the conversation hub</p></figcaption></figure>

On the hub page:

* the left column lists the object types that have conversations; select one to filter;
* turn on **Display closed discussions** to include closed conversations;
* each conversation is shown as a card with the name of the element, a link to its record, its latest messages and a reply area.


---

# 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/general/discussions.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.
