Access to this content denied based on report_view ACLs

DushanthaB
Tera Expert

hi Team
I have a user in the system whose landing page is set to the self-service portal, which includes two gauges: "My Active Incidents" and "My Requested Items."

DushanthaB_0-1737944223579.png

 

Whenever the user logs in, the page shows the message 'Access to this content denied based on report_view ACLs' under those widgets.

DushanthaB_1-1737944763998.png

 

I reviewed the ACL 'report_view', which specifies that a role must be assigned. I’ve already added the required role, but the issue persists.
Much appreciate an advice.



 

1 ACCEPTED SOLUTION

DushanthaB
Tera Expert

@Sandeep Rajput

Thank you for the valuable tip—it seems really helpful. However, my instance version is Washington DC. I’ve actually resolved the issue using a different approach. Since the underlying table for the report is [incident], I’ve verified the security rules. My main concern was the ACLs with the operation "report_view," which allows report_view access for records in the incident table for users with the role sn_incident_read. Once the mentioned role was assigned to the user through a dedicated group, the issue was resolved.

View solution in original post

2 REPLIES 2

Sandeep Rajput
Tera Patron
Tera Patron

@DushanthaB I recommend you to use Access Analyser to analyse which ACL is preventing the users from accessing the widget.

 

For more information please refer to https://www.servicenow.com/docs/bundle/xanadu-platform-security/page/integrate/identity/concept/acce...

 

Hope this helps.

DushanthaB
Tera Expert

@Sandeep Rajput

Thank you for the valuable tip—it seems really helpful. However, my instance version is Washington DC. I’ve actually resolved the issue using a different approach. Since the underlying table for the report is [incident], I’ve verified the security rules. My main concern was the ACLs with the operation "report_view," which allows report_view access for records in the incident table for users with the role sn_incident_read. Once the mentioned role was assigned to the user through a dedicated group, the issue was resolved.