> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/crm-analytics/manage-dashboard.md).

# Manage Dashboard

The Manage Dashboard option provides various features to manage, customize, save, and organize dashboards according to user requirements. It allows users to create copies of existing dashboards, modify dashboard layouts, access saved dashboards, and manage dashboard settings.

<figure><img src="https://3382165395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LlJChpzcxtwOYGcBd1q%2Fuploads%2F4EFLZqLUxWiVVgn3Hn7W%2Fimage.png?alt=media&amp;token=dcbb6e9f-91df-4d44-8642-e5a07ba67c00" alt=""><figcaption></figcaption></figure>

The Manage Dashboard section provides a set of features that allow users to filter dashboard data, refresh reports, create and customise dashboards, and manage dashboard settings.

#### Filter by Hierarchy

Allows users to filter dashboard data based on the available organizational hierarchy, such as teams, departments, or reporting levels. This helps users view information relevant to a specific organizational unit or hierarchy level.

#### Date Range

Allows users to select a specific date or time period for viewing dashboard data. The reports and charts can be filtered according to the selected date range, helping users analyze data for a particular period.

#### Refresh

Refreshes the dashboard data to display the latest available information. This helps users keep reports and charts up to date without navigating away from the dashboard.

#### Actions

Provides a menu of dashboard management options that allow users to create, save, edit, access, and manage dashboards. The available actions are described below.

Clone : Creates a copy of the current dashboard, allowing users to reuse an existing dashboard as a starting point without affecting the original.

Save Current Dashboard : Saves the current dashboard configuration, including its layout and settings, so users can preserve their dashboard setup for future use.

Edit Dashboard : Allows users to modify the dashboard, such as updating its layout, configuring widgets, or making changes to its components, depending on the available editing options.

Saved Dashboards : Provides access to previously saved dashboards, allowing users to view and manage their saved dashboard configurations.

Full Screen View : Displays the dashboard in full-screen mode, providing a larger viewing area for charts, reports, and other dashboard components.

Set as Default : Sets the current dashboard as the default dashboard, allowing users to access their preferred dashboard by default, according to the application's behaviour.

\
Dashboard Log : Provides access to dashboard-related activity logs, helping users review recorded actions or changes associated with dashboard management.

Delete : Deletes the current dashboard when it is no longer needed. Users should verify the selected dashboard before confirming deletion to avoid removing the wrong dashboard.

#### Add Report

Allows users to add reports to the dashboard. Users can customise the dashboard by including relevant reports and visualizations, helping them monitor important data and performance indicators in one place.

<br>


---

# 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://help.pickyassist.com/setting-up-guide/crm-analytics/manage-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.
