> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/analyze-with-dashboards/analytics/pinning-and-unpinning-reports.md).

# Pinning and unpinning reports

## Introduction

{% hint style="info" %}
**A note on terminology:**

A **report** on the Chord platform can refer to either a **dashboard** or a **Look** (which also known as an **explore**). A\*\* dashboard\*\* is made up of a collection of **Looks** (**explores**).
{% endhint %}

Shared folders and report pinning enables streamlined access to reports and efficient collaboration, especially when managing complex data needs across teams. The **Pinned Reports** page allows users to store and view key reports, making it easy for all stakeholders to access vital company reports in one central location. With report pinning, users can easily denote high-priority reports so that the most mission-critical reports.

Together, these features support Chord’s mission of empowering e-commerce brands to make informed, data-driven decisions faster and with greater confidence.

## Getting started

You can pin personal reports that have been added to your company’s shared folder or any of the quickstarts offered on our data platform.

To create a new report, follow these instructions: [Creating Custom Reports](/analyze-with-dashboards/custom-explores/creating-custom-reports.md).

### Pin a report

To pin a report, you can find the relevant report you’d like to use under **Shared Reports** or **Quickstarts**.

Click the **Pin** button to place the desired dashboard or Look to your organization’s **Pinned Reports** page. The reports will be organized and displayed alphabetically on the **Pinned Reports** tab.

**Note that you cannot pin reports directly from your personal folder** (**My Reports**). To pin a report that is currently in your personal folder, you must first promote and share that report to your organization’s\*\* Shared Reports\*\*.

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-a8064f6264a6b80da5a83937cbbe9d81128d3b12%2Fpinning-and-unpinning-reports-1.png?alt=media)

### Unpin a report

To unpin a report, find the relevant report you’d like to remove on the **Pinned Reports** page. Click on the **Unpin** icon to remove the report from the **Pinned Reports** page.

You can also choose to unpin a pinned report via **Shared Reports** and **Quickstarts** as well.

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-2dea969c669ada374efc8c78e1be4ffb62ef80f4%2Fpinning-and-unpinning-reports-2.png?alt=media)

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-d8604a4434f0e56d3448a474a62547c25e58fcd8%2Fpinning-and-unpinning-reports-3.png?alt=media)

## FAQs and troubleshooting

* **Question: Am I still able to publish reports in My Reports?**
  * No. With the introduction of pinning and unpinning reports, we are no longer supporting the publishing (and unpublishing flow). You can now share any dashboard or Look you want from your personal reports folder into your organization’s shared reports folder.


---

# 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.chord.co/analyze-with-dashboards/analytics/pinning-and-unpinning-reports.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.