Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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.

Reval Roles

Role name

Permissions

TIS Function

Location

Comments

Old: RevalSiteAdmin

New: HEE User Admin (existing role)

  • manage users / permissions

All functions

All local offices / designated bodies

  • For TIS team & Support teams

HEE Admin Revalidation

  • Login

  • Login

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.

  • Manage users / permissions

  • read

  • write

  • approve

  • submit*

All functions

All local offices / designated bodies

  • For Senior HEE admins / RO

  • approval relates to other Admin actions as part of workflow

  • submit relevant for sharing data beyond TIS

Old: RevalTISAdmin1

New: Reval Approver

  • read

  • write

  • approve

  • submit*

Single function i.e. Revalidation

Single local office / designated body - can be multiple (London)

  • For HEE admins

  • approval relates to other Admin actions as part of workflow

  • submit relevant for sharing data beyond TIS

  • Append user role with relevant section of TIS i.e. TISAdmin1_Reval

  • Possible to add multiple functions (by adding additional role)

  • Possible to add multiple locations

Old: RevalTISAdmin2

New: Reval Admin

  • read

  • write

Single function i.e. Revalidation

Single local office designated body - can be multiple

  • For HEE admins

  • Append user role with relevant section of TIS i.e. TISAdmin2_Reval

  • Possible to add multiple functions (by adding additional role)

  • Possible to add multiple locations

Old: RevalTISAdmin3

New: Reval Observer

  • read only

Single function i.e. Revalidation

Single local office designated body - can be multiple

  • For HEE admins

  • Append user role with relevant section of TIS i.e. TISAdmin3_Reval

  • Possible to add multiple functions (by adding additional role)

  • Possible to add multiple locations

  • Role appears redundant currently as HEE Admin Revalidation is required to login and provides read only access

RevalTrust - out of scope for Revalidation

  • read only

TBC

Single local office

  • non-HEE users

  • no requirement for HEE email address

  • password reminders required every <XX period>

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?

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.