Assumptions
Revalidation will act as a proof of concept for the new user management process & permissions model to be rolled out across TIS.
Note: A revalidation admin user shall only be given just one role.
Planned roles DRAFT
Role name | Permissions | TIS Function | Location | Comments |
---|---|---|---|---|
Old: RevalSiteAdmin New: |
| All functions | All local offices / designated bodies |
|
HEE Admin Revalidation |
|
| Without this Role, No access to reval. Something TIS team to look into. | |
Old: RevalSuperAdmin New: Not required as it’s a combination of HEE User Admin and Reval Approver. |
| All functions | All local offices / designated bodies |
|
Old: RevalTISAdmin1 New: Reval Approver |
| Single function i.e. Revalidation | Single local office / designated body - can be multiple (London) |
|
Old: RevalTISAdmin2 New: Reval Admin |
| Single function i.e. Revalidation | Single local office designated body - can be multiple |
|
Old: RevalTISAdmin3 New: Reval Observer |
| Single function i.e. Revalidation | Single local office designated body - can be multiple |
|
RevalTrust - out of scope for Revalidation |
| TBC | Single local office |
|
Alistair Pringle (Unlicensed) Adewale Adekoya Ashley Ransoo can you please review the above and confirm that it would work for other areas of TIS (non-Trainee related)
Note that interactions are defined per area in the relevant confluence page.
User Management & Permissions Model DRAFT
The below illustrates the overall user management model to be implemented.
Data Flow Diagram DRAFT
User Flows DRAFT
<PROCESS FLOW TBC>
Permissions Management - request & update flow DRAFT
In order to request and update permissions and roles, this process illustrates what needs to be included.
Alistair Pringle (Unlicensed) Adewale Adekoya Ashley Ransoo can you please review the above and confirm that it works for you?
0 Comments