> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/administration/dashboards-administration.md).
# Dashboards
Manage all the dashboards in your organization’s Phocas site.
{% hint style="info" %}
User permission: Administration > Dashboards
{% endhint %}
Users create dashboards to monitor KPIs. As an administrator, you can manage dashboards created by anyone in your organization.
Click **Administration** > **Dashboards** to open the **Dashboards** page.
The icon next to each dashboard's name identifies its type:
*  Outline gauge: A dashboard created in the new Dashboards experience.
*  Filled gauge: A dashboard created in Dashboards (Classic).
The list shows details such as the folders and owner of each dashboard. You can also see when a dashboard was last opened, which can help you decide whether it's still needed.
To find a dashboard, enter a keyword in **Filter by keyword** or use the filters under **Folders** or **Owner**. The list updates as you search or change the filters. Open the menu at the end of a dashboard's row to see its available actions. Actions depend on your access and the dashboards selected.
### Share a dashboard
1. On the **Dashboards** page, open the menu at the end of the dashboard's row and select **Share**.
2. Select the required sharing options, then click **Save**.
The sharing options depend on the dashboard type:
* For dashboards created in the new experience, select **Specific users** or **Everyone with access** and choose **Can view** or **Can edit** access.
* For Classic dashboards, share with individual users or folders.
{% columns %}
{% column %}
Sharing options for a dashboard created in the new experience
{% endcolumn %}
{% column %}
Sharing options for Classic dashboards
{% endcolumn %}
{% endcolumns %}
For more information, see [Share a dashboard](/basics/dashboards/use-dashboards.md#share-a-dashboard) for the new experience or [Sharing and folders](/basics/getting-started/sharing-and-folders.md#sharing-dashboards) for Dashboards (Classic).
{% hint style="success" %}
You can control whether users can share favorites, alerts, and dashboards through their [**Collaboration** user permissions](/administration/users/add-update-user/user-permissions.md#collaboration-sharing-permissions-for-dashboards-and-favorites).
{% endhint %}
To manage an individual user's Classic dashboards, open their [user account page](/administration/users/add-update-user/user-account-page.md) and click the **Dashboards** tab.
### Manage subscriptions
You can't currently manage users' subscriptions from the **Dashboards** administration page.
Users can still manage their own dashboard subscriptions from their homepage.
### Change the owner of a dashboard
You can't currently change a dashboard's owner from the **Dashboards** administration page.
Users can still change the owner of their own Classic dashboards. Unlock the dashboard, then click **Share**. In the **Edit dashboard** window, select another user from the **Owners** list.
### Delete a dashboard
You can permanently delete a dashboard if it's no longer required. This action can't be undone.
On the **Dashboards** page, open the menu at the end of the dashboard's row, select **Delete**, then confirm the deletion.
To delete multiple dashboards:
1. Select the rows you want to delete. You can select separate rows or click and drag across adjacent rows.
2. Click **Delete** in the floating action bar at the bottom of the page, then confirm the deletion.
---
# 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.phocassoftware.com/administration/dashboards-administration.md?ask=&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.
