Currently, roles for viewing Automation Analytics exist only in the Hybrid Cloud Console (HCC). Our non-administrative users, who operate exclusively within their local Ansible Automation Platform (AAP) instances, have no native way to view analytics reports. To grant them this visibility, we are forced to create and manage user accounts and permissions for them in a separate system (HCC).
This approach has two significant drawbacks:
It creates a disjointed user experience, forcing our teams to leave their primary work environment (AAP) to view data about that very work. 
It introduces a security and governance challenge, as we need a foolproof way to ensure these users can only see analytics data for their specific AAP organization and are not exposed to data from other teams. This does not appear to be possible today in HCC.
Proposed Enhancement:
We request the introduction of new RBAC roles directly within Ansible Automation Platform to provide local, scoped access to analytics. For example, a new built-in role like "Organization Analytics Viewer" could be created.
This role would be assigned to users or teams at the Organization level within AAP. A user with this role would gain access to an "Analytics" tab or dashboard directly within the AAP UI. The data presented in this view would be automatically and strictly filtered to show analytics (job success/failure rates, savings reports, etc.) for only the organization(s) to which they are assigned. This would provide the necessary insights without requiring access to HCC.

Describe the impact to you or the business
Business Justification:
Simplifies Identity and Access Management: Allows platform administrators to manage all permissions—execution, credentials, and analytics viewing—from a single control plane: AAP. 
Improves User Experience: Provides a seamless, integrated experience by keeping users within the AAP interface for both running and analyzing their automation.
Strengthens Security: Offers a simple and secure method for delegating analytics access, guaranteeing data segregation between different teams without complex configurations in HCC.