Enhancement to Row Level Security For HESA Reporting Pages (Doc ID 2804480.1)

Last updated on SEPTEMBER 07, 2021

Applies to:

Goal

Does row level security for HESA processing pages exist?  Access should be restricted to other institutions' data within the HESA Reporting menus located at Records and Enrollment-> HESA Reporting.

For example, within the following options within at Records and Enrollment-> HESA Reporting:
• Extract Processing
• Extract Data
ensure that an institution only has access to their own institutional data and no other institution's data.

However, some staff may require access to the all institutions' data. For example, ensure that Institution A staff would have a default of Institution A in the Academic Institution field and not allow Institution B or Institution C data be be accessed.  Conversely, allow some staff who require access to Institution A, Institution B, and Institution C data to access the data.

This is a requirement due to General Data Protection Regulations (GDPR),   A data sharing agreement is in place to facilitate some shared usage.

Traditional row level security delivered with Campus Solutions 9.2 does not limit access to the data on these pages by Academic Institution.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.