Lead Service Manager: Joanne Watson
Description
The Trust User Interface (UI) is the web application that Trust admins working with HEE, use to interact with TIS. It includes stories covering generic elements or crossing multiple other components, but doesn't include UI functions which are specific to a single component, e.g. Menus and Navigation stories can be found here, but the screens to manage Programmes would be found in the Programmes and Curricula component.
TIS-623 - Getting issue details... STATUS
Initial Discovery
IN SCOPE
- Placement - VIEW & LIMITED EDIT
- view all placements associated with them
- edit requires second level of approval to become final
- People - VIEW & EDIT (non-sensitive only)
- view for trainees associated with them
- edit trainee supervisor information
- view/edit for supervisors associated with them
- Programmes - VIEW & LIMITED EDIT
- view all programmes associated with them
- edit requires second level of approval to become final
- Posts - VIEW & EDIT
- view all posts associated with them
- edit requires second level of approval to become final
- Leave Management
- View and Edit all trainee / supervisor, excl OOP
- Second level of Approval required for any edits to become final
- Expense Management
- View and Edit all trainee / supervisor
- Reporting - VIEW & LIMITED EDIT
- view all trainee & supervisor related content
- create reports
- Courses & Event VIEW & LIMITED EDIT
- view all trainee & supervisor related content
- limited edit of events content
- General Admin
- view / edit supervisor documents
- view only trainee documents
OUT OF SCOPE (not MVP)
- Assessment - TBC during engagement with Trust UI SMLs and colleagues from other local offices*. Need to understand if trusts in any local offices use the ARCP functionality to input their FP trainee ARCPs. Again though if access to this functionality is required it will be through roles and permissions.
- Case Management
- Revalidation
- Approvals
*Local offices are asked to complete a table to indicate if any of their trusts have read or read/write access to functions
Recommendation: users are given the appropriate permissions to allow them access the relevant systems as indicated above.
- Users within a role type will all be given the same access pathways
- Further information can be found here
0 Comments