...
This is described in specific detail in Admin User Management (roles and permissions) and summarised repeated below:
...
- can view/edit People limited to Trainees and Trainers 'related' to their Trust - (Trainee → All Placements → Sites → Trusts)
- can view/edit the People L3 tabs containing Personal Details, Placements and Programme Memberships, Sensitive Data (the 4 actual Sensitive Data fields are hidden)
- cannot view/edit the People L3 tabs containing Qualifications or Assessments
- can view only / not edit Posts, limited to posts 'related' to their Trust (Post → Site → Trust)
- can view only / not edit all Programmes.
- For clarity, HEE Trust Admins will NOT have access to the TIS Admin section
...
- , Revalidation & Concerns
- For clarity, as the Trainee 'related' to their Trust includes 'All' Placements, historical and future, the HEE Trust Admin will see Trainees across a range of Local Offices.
Solution Design
...
The design includes some basic elements:
- Allocating all Trust administrators to a new role in Keycloak - one role for all Trust admins
- Linking a Trust Admin to their Trust - initially only one TrustImplementing authorisation following the existing (flawed) model as a tactical solution
- Limiting access to TIS at the top menu level - Trust Admins will only have visibility and access to People, Post and Post Programmes L1 menu items (not Programmes, Assessments, Admin)
- Limiting access to Sensitive data fields within the Sensitive data L2 menu in People - Trust Admins won't see the four sensitive data fields in People records
- Limiting access to TIS data within People and Post - the List and CRUD for both People and Posts will only show People/Posts relating to the Trust(s) of the Trust Admin
- Read Only access to Programmes and Posts, Read/Write access to all data visible in all People L2 tabs
We will return to re-implementing authorisation once a new design has been established to provide appropriately secure roles and permissions.
...
We will create a new 'HEE Trust Admin' role in Keycloak, in parallel to the existing roles - Admin User Management (roles and permissions)
Linking a Trust admin to their Trust
...
Implement standard permission constraints for in the Front End cfor 'HEE Trust Admin' to only People and Posts L1 menu items. This role should also NOT be able to see sensitive data.
Limiting access to Sensitive Data Fields
Implement standard permission constraints in the Front End to limit 'HEE Trust Admin' role to not see the 4 Sensitive Data fields that are already hidden from standard HEE Admins
Limiting access to TIS records within People and Posts
...
Trust ID can be established by navigating through a Person's placements Placements to its Post, to its Site, to its Trust. Because we expect this to be too slow to perform in real time, we're suggesting a PersonTrust table linking a PersonID to a TrustID - 1:many (1 Person can be in Many Trusts).
...