Users with dashboard editing permissions can create public dashboards (see details: 2. Dashboard module), and as the number of users increases, the public dashboards section in some projects contains a large number of dashboards that are actually invalid, abandoned, or have duplicated or unclear content. When team members review data, it is difficult to identify which dashboards are effective and accurate, greatly reducing the efficiency of data analysis.

At this point, dashboard governance is required. The main steps include the following:
(1) Cleaning up redundant and abandoned dashboards
(2) Archiving some historical dashboards (dashboards that are not regularly viewed but may be needed for future reviews, such as event dashboards)
(3) Categorizing effective dashboards
This article will introduce dashboard governance solutions step by step according to these three steps.
Comparison of results:

2.1 Cleaning up dashboards with no visits for an extended period #

Go to Project Center - Access Statistics, select "Last 30 days", "Owned by me", and "Dashboard". In the usage summary, add the filter condition "pv=0".
View dashboard information, select the dashboards, and perform batch cleanup. You can also select all dashboards on the current page for cleanup.

If you choose "Delete", the dashboards will be moved to the recycle bin and can be restored from Project Center - Recycle Bin within 15 days.
If you choose "Permanently Delete", the dashboards will be permanently deleted and cannot be recovered.

2.2 Cleaning up based on specific conditions #

You can filter out obviously useless dashboards by keywords and clean them up. For example, search for dashboards with names containing "test".

Filter by dashboard owner, such as batch processing dashboards owned by team members who are about to leave or transfer positions.

In PV/UV statistics, exclude visits from certain users or user groups to obtain the PV/UV of dashboards excluding these users, which helps determine whether the dashboards can be deleted.

Then handle the queried dashboards as appropriate.

Some dashboards are no longer frequently viewed, but may still be needed for future review, and it is unclear which folder they should be placed in.
At this point, you can create a "Dashboard Archive" folder in the dashboard interface.

Go to Project Center - Access Statistics, select in bulk the dashboards that need to be archived, click Move, and move them to the archive folder.

4.1 Categorization #

After cleaning up and archiving redundant or obsolete dashboards, only the useful dashboards remain. However, as there is no categorization, the list still appears disorganized, making it difficult to quickly locate the desired content.

It is recommended to create folders based on different business units or business domains. This way, business stakeholders only need to focus on one or a few folders when viewing. (It is recommended that this step be performed by the project's data administrator for centralized data management.)

Next, drag and drop dashboards into the corresponding folders, and you can also sort them by dragging.

4.2 Permission convergence #

To prevent users from continuing to create dashboards in the root directory and causing the dashboard list to become disorganized again, it is recommended that the project administrator converge user permissions after dashboard governance is complete.
First, for business users who do not need to create datasets or public dashboard folders, change their project editing permissions to view-only permissions to prevent them from creating dashboards in the public dashboard root directory.
In Project Center - Permission Management, select the user or user group to Permission Management
For users who need to create dashboards within their own business, enable editing permissions for the dashboard folder.

After this adjustment, users will not be able to create dashboards in the public dashboard root directory, but can create and modify dashboards within the corresponding folders.