> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/step-5-analyze-interpret-and-report/compass-admin/results/dashboard-editor.md).

# Dashboard Editor

Dashboards show the most important results from a survey on one page, or give leaders at-a-glance metrics for an ongoing survey. Site Admins build them in the Dashboard Editor and share them as a webpage or a PowerPoint export.

{% hint style="info" %}
**Admin access required.** The Dashboard Editor lives on the Admin pages, which Site Admins can access. Report Viewers and Restricted Report Viewers see the finished dashboard, not the editor.
{% endhint %}

{% hint style="info" %}
**Decide the story first.** Before you configure a dashboard, decide what you want the data to say. We strongly suggest speaking with your Project Manager or consultant before you publish a dashboard for your survey results.
{% endhint %}

***

## Overview video (9m 16s)

{% embed url="<https://vimeo.com/1050048161?share=copy#t=0>" %}

***

## Build a dashboard

1. Navigate to **Admin** > **Results** > **Survey Title** > **Dashboard**.
2. Enter a title for the dashboard. It appears on the dashboard webpage and in the export.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FEp5smT0aDiQwGTPpXYxY%2Fdownload.png?alt=media&#x26;token=cb7f1a78-2222-463b-8a02-d590e7b67a16" alt=""><figcaption></figcaption></figure>

3. Click a cell type in the second column, then drag and drop it anywhere on the editor grid.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2F0fphGdBcFkjSrLNaOg76%2Fdownload%20(1).png?alt=media&#x26;token=92d3d508-bc42-4466-b395-79a0920a143b" alt=""><figcaption></figcaption></figure>

4. Click the **pencil** icon in a cell to set its size, survey dimension, title, and other options. Click the **trash can** icon to remove a cell from the grid.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FaX2MouvXrIRscVbBX9zV%2Fdownload%20(2).png?alt=media&#x26;token=7cd1189a-822f-45ab-9095-e50ebded8ac6" alt=""><figcaption></figcaption></figure>

5. Add another cell and repeat step 4 until the dashboard tells the story you planned.
6. Click **Review** to see a PowerPoint export of the results.

***

## Editor tips

* A cell with a **dashed outline** has no content yet. Click the pencil icon to edit it.
* A cell with a **red outline** overlaps another cell. Drag it until the outline turns grey. Overlapping cells do not show on the dashboard webpage or in the export.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2F4cWoqrNH7o1utqdYblPL%2Fdownload%20(3).png?alt=media&#x26;token=ba6ece19-5cfb-4e11-a1a5-ecebabd97173" alt=""><figcaption></figcaption></figure>

* Work with Compass open on two screens: the editor on one and the dashboard webpage on the other. Make a change in the editor, then refresh the webpage to see it.

***

## Dashboard confidentiality

Dashboards follow the same confidentiality rules as every other Compass report. For the full picture across reports, see [Confidentiality and Permissions in Compass](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/confidentiality-and-permissions-in-compass.md).

* **Minimum group size.** No group is reported on with fewer than 5 responses. This applies to dashboard cells as well as the Snapshot and Heatmap reports.
* **Restricted demographic fields.** A demographic field with **Restrict Access** toggled ON is hidden from Restricted Report Viewers in dashboards, as it is in every other report view. See [Hide Demographics from Restricted Users](/knowledge-base/step-5-analyze-interpret-and-report/compass-admin/results/general/hide-demographics-from-restricted-users.md).
* **Restricted Report Viewers** see the dashboard for the group they are assigned to. See [Assign Access](/knowledge-base/step-5-analyze-interpret-and-report/compass-admin/results/assign-access.md).
* **Filter-similarity blocking** is a Snapshot report control. See [How does report filter confidentiality work?](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/reporting-faq/how-does-report-filter-confidentiality-work.md).

{% hint style="info" %}
**Ranked choice questions** do not appear as a dashboard cell or in the dashboard export. See [Ranked Choice Questions](/knowledge-base/survey-design-and-deployment/creating-surveys-quick-start/ranked-choice-questions.md).
{% endhint %}

***

## Related Articles

* [Compass Reports](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports.md)
* [Bulk Export](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/general/bulk-export.md)
* [Hide Demographics from Restricted Users](/knowledge-base/step-5-analyze-interpret-and-report/compass-admin/results/general/hide-demographics-from-restricted-users.md)
* [Assign Access](/knowledge-base/step-5-analyze-interpret-and-report/compass-admin/results/assign-access.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://docs.talentmap.com/knowledge-base/step-5-analyze-interpret-and-report/compass-admin/results/dashboard-editor.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.