Best practice to prevent accidental dashboard edits by end users

[brian_good_alli]

We had a user who accidentally reordered the tabs on a dashboard, by dragging and dropping. The dashboard was shared for editing with this user by the dashboard owner. But the dashboard in question was one developed by a central team, and we would like to restrict the possibility of such accidents in the future.

If I look at the ACLs that control tab order, for example, they are on a table called pa_m2m_dashboard_tabs. But the OOTB ACLs on that table are scripted to an extent that modifying them does not seem to be a good practice.

Is there a more straightforward way to prevent these kinds of accidents, or prevent the sharing of dashboards for editing by the owner?

For example, is it possible to remove the "Can edit" option when a dashboard owner shares dashboards?

[Tsura Andreeva]

When sharing the dashboard to a person - use the "Can View" instead of the "Can Edit" 

[brian_good_alli · Accepted solution]

The feedback I got from ServiceNow is that it is not really possible to restrict what users can edit when a dashboard owner shares a dashboard with them and uses "Can edit."

In the Next Experience dashboards, a "Save" step has been added... this should prevent accidental updates to dashboards.

[cynlink1]

Has any updated the Dashboard Permissions in bulk via the the pa_dashboards_permissions table versus updating the Share(s) one-by-one? For instance, setting the Write field to 'false' from the pa_dashboards_permissions table by updating the list column.