Idea / Enhancement Request
Oracle FDI should support subject-area-level separation between consume/read access and author/write access for the same user or role.
Today, FDI security does not appear to provide a supported way to let a user consume reports from one subject area while restricting their authoring access to a different subject area only.
Example Requirement
A user should be able to:
- View existing reports built on HCM – Workforce Compensation.
- Create or edit reports only using HCM – Workforce Core.
- Not create or modify reports using HCM – Workforce Compensation.
Current Limitation
Based on Oracle’s response, this type of differentiated subject-area access is not currently supported as a standard FDI security configuration. Access to subject areas for consumption and authoring is not granular enough to enforce this split cleanly for the same user.
Requested Enhancement
Please provide a supported security model that allows administrators to configure, by subject area:
- Read-only / consume access.
- Author / create / edit access.
- Visibility of subject areas during report creation.
- Enforcement so users cannot author reports on restricted subject areas.
Business Justification
This is needed for least-privilege access. Users may need to consume sensitive or controlled reporting content from one subject area, while only being allowed to build or modify analytics in another approved subject area. This would reduce the risk of unauthorized report creation while preserving required reporting access.
