<h2>When a dashboard is created in the HR Scope, users will not be able to access it without creating new ACLs</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Description</h3><section><div><span style="font-size: 14pt;"><strong>Why do users not have access to dashboards created in this scope?</strong></span></div> <div> </div> <div>For scoped-admin enabled applications, ACLs for global metadata tables (including pa_dashboard) will default to scoped admin (for HR Core this is sn_hr_core.admin out of box). Thus, the global ACL logic that grants read access to a user that a dashboard is shared with will not run and not be evaluated.</div> <div> </div> <div><span style="font-size: 14pt;"><strong>Should it be a PRB?</strong></span></div> <div> </div> <div>This is considered to be a configuration issue rather than a potential PRB for the HR team. This is because we <span id="section_tab.6fea3264879b90c0957bb3aeef434d07"><span id="section-6fea3264879b90c0957bb3aeef434d07">do not provide any 'out of the box' PA Dashboards in our HR Core scoped app.</span></span></div> <div> </div> <div> </div> <div><strong><span style="font-size: 14pt;">What is the workaround?</span></strong></div> <div> </div> <div>1) Create a record in the sys_scoped_admin_acl_inheritance table with 'Human Resources: Core' Application for table 'pa_dashboards' (this will allow the global ACL rules from global to work for the HR Core scope) </div> <div> </div> <div> </div> <div>Attached to this knowledge article is a sys_scoped_admin_acl_inheritance record which can be imported into your instance. This has been tested and has worked successfully for other customers.</div></section></div></article></div>