Access to Content Denied Based on Extra Security on READ ACLs ErrorIssue Access to this content denied based on extra security on READ ACLs.: com.glide.processors.json.ACLException: Access to this content denied based on extra security on READ ACLs.: com.glide.report.js.ReportUtil$SecurityCheck.canReadView(ReportUtil.java:470)com.glide.report.js.ReportUtil.canViewReport(ReportUtil.java:159)com.glide.processors.report.run.SingleScoreRunProcessor.processRequest(SingleScoreRunProcessor.java:27)com.glide.processors.report.run.ReportRunProcessor.process(ReportRunProcessor.java:48)com.glide.processors.XMLHttpProcessor.processJavaAJAX(XMLHttpProcessor.java:168)com.glide.processors.XMLHttpProcessor.process(XMLHttpProcessor.java:121)com.glide.processors.AProcessor.runProcessor(AProcessor.java:779)com.glide.processors.AProcessor.processTransaction(AProcessor.java:326)com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:187)com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:175)com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:58)com.glide.sys.Transaction.run(Transaction.java:2790)com.glide.ui.HTTPTransaction.run(HTTPTransaction.java:35)java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)java.base/java.lang.Thread.run(Thread.java:840)ReleaseXanaduCauseThe root cause of this error is that the user is landing on the `pa_dashboard.do` page, but the dashboard or report they are trying to access is not accessible to them due to extra security on READ ACLs.Resolution1. Impersonate the user and land on the `pa_dashboard.do` page.2. Identify the dashboard or report that is not accessible by checking the sys log for the audit entry.3. Try accessing the identified dashboard or report yourself. If you cannot access it, either provide the user with access to the report or remove it from their dashboard view.4. If you are unsure which role is required to access the report, run debug security rules and impersonate the user to access the report. This will help you identify the failing ACLs.5. Once you have provided the user with access to the necessary reports, the error should no longer occur.