How To Troubleshoot "Access to this content denied based on report_view ACLs" errorsTable of Contents: Problem StatementTroubleshooting StepsTroubleshooting DemoAdditional Reference Problem Statement: The steps below will help you troubleshoot and fix the Report_view ACL(RVA) related errors. This can be used when you see the error "Access to this content denied based on report_view field ACL" on Reports or dashboards. Other similar errors: "Access to this content denied based on report_view field ACL's" "Access to this content denied based on extra security on READ ACLs" Troubleshooting Steps: In the filter navigator select "System Diagnostics --> Session Debug --> Debug Security" It will open a new debug window.Impersonate the impacted user who is experiencing the RVA error.Remove the existing logs in the new debug window which opened in Step 1 by clicking the "Clear log" button on the top rightNow click on run for the impacted report or refresh the widget on the dashboard.In the debug window you will find the report_view ACL that is blocking the user from viewing the report.Now you know which report_view ACL is blocking we can stop the debugging by "System Diagnostics --> Session Debug --> Disable All"There are a few ways to remediate the access You can grant one of the roles for the ACL you found from the debugger to the impacted user.You can create another custom RVA and grant any role that the user already has. You can also review additional documents in the Additional reference section to review all the affected reports in one go. Troubleshooting Demo: Additional References: Enabling Report View ACLsManage Report ACL assessmentsChanges made in Utah