Platform Analytics Dashboard Shows "Access Restricted" for RITM-Based Widgets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Team,
We are facing an issue with a Platform Analytics dashboard in ServiceNow.
Scenario
- The dashboard data source is Requested Item [sc_req_item].
- Users can successfully access and view all RITM records related to SOC Change Request from the Requested Item list.
- A custom role (soc_change_request_viewer) has been created and assigned to the required groups.
- ACLs were reviewed, and the Query Business Rule controlling RITM visibility was updated accordingly.
Issue
Although users can view the underlying RITM records, the Platform Analytics dashboard widgets display "Access Restricted" and do not show any data.
Administrators can view the dashboard data without any issue.
Validation Performed
- Users can access the dashboard.
- Users can view the underlying sc_req_item records.
- The following roles have been tested:
- report_user
- pa_viewer
- sn_request_read
- sn_request_approver_read
- soc_change_request_viewer (custom role)
- ACLs have been reviewed.
- Dashboard sharing and visualization sharing have been verified.
- Access Analyzer previously identified a Query Business Rule restricting access. After updating the Query Business Rule, users can now view the relevant RITMs, but the dashboard widgets still show "Access Restricted" and no data is displayed.
Request
Has anyone encountered a similar issue where users can access the source records but Platform Analytics widgets still display "Access Restricted"?
Are there any additional Platform Analytics permissions, data collection configurations, indicator source permissions, or widget-specific access controls that should be reviewed?
Any guidance would be appreciated.
Thank you.
#ITSM #ServiceNow #dashboard #ACL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @rohith_fed,
List access and Platform Analytics access are evaluated differently, so passing the list test does not clear the widget. In Platform Analytics a data visualization checks three separate layers, and 'Access Restricted' is shown if any one of them fails:
1. Field-level ACLs, not just table read. The widget needs read access to every field it displays, groups by, or filters on - not only sc_req_item read. A user can open a RITM form/list restricted to a few columns and still fail a widget that groups by, for example, a field added for SOC reporting. Impersonate an affected user, run Access Analyzer against sc_req_item for one failing record, and check it field-by-field for all fields used in the widget, including fields on related/dot-walked tables. Add read ACL coverage for soc_change_request_viewer on any field that fails - do not just add another table-level read ACL.
2. Sharing on each visualization itself. In the Platform Analytics experience, sharing the dashboard does not cascade to every visualization on it, and sharing a visualization does not grant the underlying data. Open each failing widget in the Visualization Designer, use its Access / sharing settings, and confirm soc_change_request_viewer (or the group) is explicitly allowed there as well as on the dashboard (par_dashboard). Do the same check for the data source if the widget is built on a data source rather than directly on sc_req_item.
3. Re-check the Query Business Rule as the widget would run it. PA aggregations run as a query - if the QBR adds conditions based on, for example, the interactive session, a reference field, or gs.getUser().getMyGroups() in a way that returns no/denied rows for a count query, the list (single record) can still open while the aggregate is blocked. Temporarily log the encoded query the QBR produces for an impersonated user on sc_req_item and run exactly that query as that user.
Test in this order with one impersonated user and one single-score (count) widget first, because a count widget removes most field issues: if the count widget works after step 2 but a grouped widget does not, it is a field-ACL issue (step 1); if even the count widget is still restricted, it is the visualization sharing or the QBR (steps 2-3).
Admin working is consistent with all three - admin bypasses ACL and QBR checks that the custom role does not.