- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2025 03:59 AM
( im a student so please dont be mad for not knowing)
i made a report and added it as a widget to the portal ESC and the graph looks great and all but everytime i switch from SYS Administrator to someone else like abel tutor by impersonating the Dunut graph disappers and im met with an error that says "Access to this content denied based on report_view ACLs." the problem is i made sure to set the graph to public so I dont understand what exactly is the issue and how to solvde it please help
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2025 05:14 AM
Hi @MariaRivkin ,
Go to the ACLs and filter the ACLs related to your report's table (name starts with your table name)
And check if there is any ACL with operation=report_view and check the roles and add the suitable role
If you don't find any report view ACL then create one and assign the role
Regards
Chaitanya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2025 10:44 AM
Hi @MariaRivkin
Don’t worry at all — your question is a good one, and it’s great that you’re exploring things hands-on! Even though you’ve set the report to public, the issue comes from the report_view ACLs, which are tied to the data the report is showing. When a non-admin user (like Abel Tutor) tries to view the donut chart, ServiceNow checks if they have permission to read the data from the underlying table (like incident, task, etc.). If there’s an ACL restricting that access, the report will be blocked even if it’s public. To fix this, you’ll need to check the read ACLs on the table used in the report and make sure users like Abel have permission to read from it. You can do this by either modifying the existing ACL to include their role, or assigning them a role that has the right permissions
If this helps kindly accept the solution.
Kind Regards,
Mohamed Azarudeen Z
Developer @ KPMG
Microsoft MVP (AI Services), India
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2025 05:14 AM
Hi @MariaRivkin ,
Go to the ACLs and filter the ACLs related to your report's table (name starts with your table name)
And check if there is any ACL with operation=report_view and check the roles and add the suitable role
If you don't find any report view ACL then create one and assign the role
Regards
Chaitanya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2025 10:44 AM
Hi @MariaRivkin
Don’t worry at all — your question is a good one, and it’s great that you’re exploring things hands-on! Even though you’ve set the report to public, the issue comes from the report_view ACLs, which are tied to the data the report is showing. When a non-admin user (like Abel Tutor) tries to view the donut chart, ServiceNow checks if they have permission to read the data from the underlying table (like incident, task, etc.). If there’s an ACL restricting that access, the report will be blocked even if it’s public. To fix this, you’ll need to check the read ACLs on the table used in the report and make sure users like Abel have permission to read from it. You can do this by either modifying the existing ACL to include their role, or assigning them a role that has the right permissions
If this helps kindly accept the solution.
Kind Regards,
Mohamed Azarudeen Z
Developer @ KPMG
Microsoft MVP (AI Services), India