...
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 Trust
- Implementing 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 Programmes L1 menu items (not 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 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
...