---
sourceDocument: Brazil Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/now-intelligence

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Fallback ACL evaluation

# Fallback ACL evaluation {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
When a data visualization is run, report_view access control lists (ACLs) are evaluated on the table and table fields that the report is based on. If no report_view ACL exists, there is a fallback check on
table-level read ACL roles.

If no report_view ACL for a table or table field exists, evaluation is conducted against the read ACL. Users can only view the visualization if they pass the read ACL.  
Note:  
Before Zurich, it was possible to change the fallback read ACL behavior through the system property glide.report.report_view.read_acl. This change is no longer possible. Read ACLs are always enforced in the absence of a report_view ACL.

As with report_view rules, the fallback table-level read ACL check applies only roles and security attribute conditions. No other conditions are evaluated.  
Important:  
Read ACLs only apply to read operations. Therefore, they do not affect access to the contents of visualizations that only show an aggregate, such as single-score visualizations. This limitation led to the development of report_view ACLs.