Issue 

In Pega Platform 25.1.1, deletion of a public Explore Data dashboard cannot be limited to the dashboard creator. Any user who has access to the dashboard can delete it, even if that user did not create it. 

Description 

Users want to grant dashboard deletion rights exclusively to the dashboard creator. 

Pega Platform 25.1.1 does not provide a native capability to enforce creator-based deletion permissions for public Explore Data dashboards. 

Symptoms and impact 

A user who did not create a public Explore Data dashboard can delete it. This behavior can result in a dashboard being deleted by a user other than its creator. 

Steps to reproduce

1. Create a public dashboard insight.
2. Sign in as a different user.
3. From the Actions menu, select Delete.
   
   
   
   Result: The user can delete the dashboard even though the user did not create it.

Root cause 

This behavior is a product feature gap. Pega Platform 25.1.1 does not provide an out-of-the-box capability to restrict dashboard deletion based on creator ownership. The behavior is expected.

Solution

As a workaround, perform the following steps: 

1. Create a persona for a user who did not create the dashboard (for more information, refer to Creating personas
   
   
    
2. Use Access of Role to Object configuration to prevent dashboard deletion at the server level. 
3. Create a new "Access of Role to Object" instance (for more information, refer to Create an Access of Role to Object rule)
   • In the Label field, enter the label of the previously created persona.
   • In the Role Name field, enter the role name of the previously created persona.  
   • In the Access Class field, enter Rule-UI-Insight. 
4. Set the deletion access for the relevant dashboard class to 0, which means Do Not Grant Access.
   
   

This workaround applies the restriction through role-based access. It does not limit deletion specifically to the dashboard creator. 

The workaround prevents the deletion request from being completed. However, the Delete option remains visible in the user interface. A user might therefore see the option even though the server prevents the deletion.

References

• Creating personas
• Create an Access of Role to Object rule