There is a requirement to demonstrate and further evaluate the ability to restrict users from downloading or exporting data from Out-of-the-Box (OOTB) reporting content, while continuing to provide them with appropriate view-only access.
An OOTB Viewer role, for example FAW Licensed HCM Viewer Role, is available and is intended to provide more restrictive access, preventing users assigned to the role from downloading data from reports. However, the role is not currently configured OOTB in a way that enables this capability to be readily demonstrated across the standard Oracle-delivered content.
For custom-developed content, the Viewer role can be configured and used to provide the required level of access. However, applying an equivalent configuration to OOTB content is constrained by the access restrictions associated with the "Oracle" folder, which contains the Oracle-delivered content. As a result, it is currently difficult to demonstrate a consistent Viewer experience across both custom and OOTB reporting content.
The desired outcome would be to enable the Viewer role to access the appropriate OOTB content in a similar manner to the existing Consumer role, while retaining the additional restriction that prevents data download or export.
This would provide a clear and meaningful business scenario where two different user populations can be demonstrated and validated:
- Viewer users would be able to access and interact with authorised OOTB reports and dashboards but would not be permitted to download or export the underlying report data.
- Consumer users would continue to access the relevant OOTB content with the ability to download or export data, subject to their existing permissions.
Enabling this capability would allow the business to test and validate the effectiveness of role-based data download restrictions using representative OOTB content rather than relying solely on custom-developed reports. It would also provide a clearer demonstration of how different access profiles could be applied to different business user groups based on their data consumption requirements.
From a governance and security perspective, this would support a more controlled approach to information access by distinguishing between users who need to consume information within the analytics platform and those who have a legitimate business requirement to extract data for further analysis or offline use.
The requested enhancement is therefore to allow the OOTB Viewer role to be configured with access to the relevant OOTB content, comparable to the Consumer role, while preserving the restriction on downloading or exporting data. This would enable the functionality to be demonstrated to stakeholders, tested with representative business users, and assessed for potential wider adoption.
