Platform Analytics - How to enforce few Best practice rules, how to control access

[RaniK3666699030]

Hello! 

Under the Platform Analytics (Australia version):

1. Governance / Checklist Enforcement
We are looking to implement governance controls at the time of report and dashboard creation—for example, ensuring every dashboard has a clearly defined purpose, target audience, and follows naming conventions.

Beyond providing guidance documentation, is there a way to technically enforce these requirements during the creation of data visualizations and dashboards?

---

2. Restricting Dashboard & Data Visualization Creation
We would like to limit the ability to create data visualizations and dashboards to a smaller group of users (e.g., ITIL-licensed users).

In the Australia version of Platform Analytics, it appears that all roles currently have the ability to create new artifacts (reports and dashboards). Is there a way to restrict this capability to users who will have ITIL role?

---

Appreciate your input—thank you!

[Its_Azar]

Hi there @RaniK3666699030 

Platform Analytics currently relies mostly on process controls, naming standards, documentation, and role-based governance rather than mandatory creation-time validations. but, you can introduce custom controls such as UI Policies, Client Scripts, Business Rules, or Flow-based validations to enforce required fields, naming conventions, ownership details, or approval checks before dashboards 

For restricting dashboard and visualization creation, access can typically be controlled through roles, ACLs, workspace permissions, and delegated developer/reporting roles. Many organizations restrict creation capabilities to a smaller reporting or ITIL user group by removing broader authoring permissions and assigning creator roles only to approved users.