Access to this content denied based on report_view field ACLs

[Pinky_setso]

Hi everyone. After upgrading Dev and Test to Australia, I noticed an odd change on the CSM portal view when impersonating a customer admin. The pie chart report that is supposed to be displayed under the My Satisfaction Survey widget is now blocked by the "Access to this  content denied based on report_view field ACLs."

I have tried to troubleshoot this error by checking all the ACLs related to report-view operation under the metric result table which is the source of the report not displaying and followed all the other shared know articles but still not getting this fix right. Any help on this will be appreciated.

Thanks.

[Ankur Bawiskar]

@Pinky_setso 

this is default behavior after Australia upgrade

check below links

Access control: When users can't see what they should

User cannot see dot walking field in report (user have ACL on base table), Error: "Access to this co...

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Pinky_setso]

Hi Ankur,

I have seen these articles already during my troubleshoot and have tried the solution but still not able to get it work. This is a real blocker as I cannot upgrade production until I have managed to make it work. 

[sachinvic]

Hi Pinky

Ankur is spot on—this is default platform hardening behavior introduced in the Australia release.

Starting with this version, report_view ACLs now actively evaluate every single field used in the report's filters, group-by, conditions, and dot-walked paths. If your user has standard table access but lacks a report_view rule for even one field or referenced table in that chart, the whole widget blocks.

Since you've already tried the standard articles, follow these quick steps to find the exact bottleneck:

1. Find the Culprit: Navigate to System Diagnostics > Session Debug > Debug Security. Impersonate the impacted user, refresh the dashboard, and check the logs. Look for the Red line showing exactly which field or table is failing the report_view check.
2. Apply the Fix: Once you identify the specific field or dot-walked table from the logs, create a new ACL for it:
   • Type: record
   • Operation: report_view
   • Name: Select the target table and the specific field (or * for all fields).
   • Requires Role: Add the role assigned to your Customer Admins.

Note: Make sure your report_view ACL relies strictly on Roles. Scripts or advanced conditions are not supported for this operation type and will be ignored.

Give the security debugger a quick run to find the failing field, add the role to it, and you should be good to go for your production upgrade!

[Tanushree Maiti]

Hi @Pinky_setso 

Please check the ACLs on the table where the reports are created.

If a Report View ACL already exists, verify which role is configured in the ACL. You can resolve the issue by either of the following methods:

1. Add the appropriate role to the Report View ACL based on the end user's role (for the user who is unable to view the reports).
2. Assign the role specified in the Report View ACL to the affected user.

If a Report View ACL does not exist, create one, add the required role to it, and assign the same role to the user.