Oracle FDI – HCM security

Rajendraprasad N

Hello Everyone,

We have a requirement to restrict all access to C-Level executive data (e.g., CEO, CFO, CHRO, etc.) within Oracle Fusion HCM FDI Analytics. This restriction needs to apply across all subject areas and attributes, ensuring that both consumers and authors cannot view or interact with any data related to C-Level users.

We attempted to implement this via semantic model extensions by applying filters based on user attributes. However, the filters are only taking effect on specific subject areas and selected attributes—not across the board.

We are looking for guidance on the following:

What is the recommended approach to enforce global-level filtering of C-Level data in Oracle FDI?
Can this be achieved using row-level security (RLS), authoring privileges, or semantic layer restrictions?
How do we ensure the restriction is comprehensive across all existing and future subject areas?
Is there any Oracle-delivered best practice or reference configuration for such use cases?
Our goal is to ensure compliance with internal data governance policies by completely blocking access to any C-Level data for unauthorized users.

Any advice, documentation references, or examples would be greatly appreciated.

Thank you!

Alex van Gulijk

Is the C-Level data already restricted within the HCM UI? If so, you can leverage the same group role that enforces that restriction and apply it to your Application Roles in FDI.

For example, we’ve created custom “View All” roles and assigned them to the relevant Application Roles so users can access the same content levels they see in the HCM UI. Similarly, “Except Self” roles function correctly in both the HCM UI and FDI, as long as they are included in the FDI Application Role and mapped to the appropriate subject areas.