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

# Dashboard

The dashboard is the home page of your workspace: it summarizes your GDPR compliance with one tile per module that you can reorder.

The dashboard is the first page you see when you enter a workspace. It summarizes the state of your GDPR compliance and gives access to the modules. To come back to it from any page, click **Home** at the top of the left menu.

## The areas of the screen

The screen has three areas:

* **The left menu**: the workspace selector, which also shows your roles in the workspace, then the modules grouped under **Data inventory**, **Operations**, **Governance**, **Automations** and **Resources**. The **Invite a member** button and the **Workspace settings** entry are at the bottom of the menu. A module only appears if your subscription includes it and your permissions give you access to it.
* **The central section**: above the tiles, depending on your permissions and subscription, you find the AI agent prompt (**How can I help you today?**), the card of the latest release note, the **Progression** card (the getting started guide) and the **Project presentation**, a free text that introduces the workspace to its users.
* **The community tab**, on the right of the screen: it opens the **Upcoming webinars** panel. You can collapse the panel; the tab then stays on the right of the screen to reopen it, and your choice is remembered in your browser.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d0ed791d0061f6e4d733062a1d93efd4d1c6dc55%2Fdashboard-1.png?alt=media" alt="The dashboard with the left menu, the release note card, the getting started guide and the tiles"><figcaption><p>The dashboard of a workspace</p></figcaption></figure>

## The dashboard tiles

The tiles summarize the activity of each module. By default, they appear in this order, for the modules you have access to:

* **Record of processing activities**
* **Compliance**
* **Latest news**
* **Tasks**
* **Requests over the last 90 days**
* **Last incidents**
* **Contracts & Policies**
* **AI Systems**
* **Risk management**
* **Your questionnaires**
* **Assets**

Most tiles (processing activities, tasks, requests, incidents, contracts, AI systems, risks and questionnaires) have an organizational unit filter. Use it to limit the tile to the items of one entity or department.

### Reorder the tiles

To change the order of the tiles, drag the handle next to a tile, or click the **Move up** and **Move down** buttons that come with it. The order is saved in your browser: it does not change for other 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-52b089c13a066102ee554c203e602f3cc54d188f%2Fdashboard-2.png?alt=media" alt="A dashboard tile with its handle, the Move up and Move down buttons and its organizational unit filter"><figcaption><p>A tile and its move controls</p></figcaption></figure>

## Invite a member

If you have the right to manage users, the **Invite a member** button appears at the bottom of the left menu. It opens the form to invite a new user. For the details of the fields, see [Invite users](/en/getting-started/setup/users.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-668658b8a9d28a028b24245c8dc1d6f98fe1e822%2Fdashboard-3.png?alt=media" alt="The invitation form opened from the Invite a member button"><figcaption><p>The form to invite a member</p></figcaption></figure>

## Go further

Explore the features:

{% content-ref url="/pages/-LvM7KI26TZ\_CxoNeipO" %}
[Record of processing activities](/en/features/ropa.md)
{% endcontent-ref %}

{% content-ref url="/pages/NKFSRV0hPhsNTY80KTB1" %}
[Data visualization](/en/features/ropa/visualization.md)
{% endcontent-ref %}

{% content-ref url="/pages/RSH8fdsWx5KSZkjvXf9a" %}
[Risk management](/en/features/risks.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Lw3hALWsjvX2sseOt14" %}
[Planning](/en/features/tasks.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M31ydu73LeeHMZQ4ECM" %}
[Data subject right request](/en/features/requests.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M31zD6jKngOCW1hmuCc" %}
[Incidents and data breaches](/en/features/incidents.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M31ynfUgMD579kUk9LB" %}
[Manage cookies consent](/en/features/cookies.md)
{% endcontent-ref %}

{% content-ref url="/pages/RY7aouLcykTlhn7qY0o2" %}
[Questionnaires](/en/features/questionnaires.md)
{% endcontent-ref %}

{% content-ref url="/pages/HVU4YcItwredOaZB3wrE" %}
[Advanced configuration](/en/features/settings.md)
{% endcontent-ref %}


---

# 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/dashboard.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.
