Business Requirements
Functional Requirements
| Ref | Requirement |
| BR1 | When an active staff member role is given access on eAuthorisations to any application, the user will automatically be added (if they're not already in it) to the Launchpad access group in OpenAM, which means that they will be able to access Launchpad |
| BR2 | When an active staff member role is added to a user in eAuthorisations, the user will automatically be added (if they're not already in it) to the Launchpad access group in OpenAM, and the user will automatically be added to the eFin access group in OpenAM, which means that the eFin access icon will appear in Launchpad. |
| BR3 | When a staff member has their active staff role removed in eAuthorisations the user will automatically be removed from the eFin access group in OpenAM, which means that the eFin access icon will disappear in Launchpad. |
| BR4 | When an active staff member role is given access to FPM or Online Banking within eAuthorisations the user will automatically be added (if they're not already in it) to the relevant access group in OpenAM, which means that the access icon will appear in Launchpad. |
| BR5 | When a staff member has their access removed from FPM or Online Banking within eAuthorisations the user will automatically be removed from the relevant access group in OpenAM, which means that the access icon will disappear in Launchpad. |
| BR6 | Launchpad access to in-house applications (e-Expenses, eITS, eStores, eTime & WebFirst) is already controlled directly between eAuthorisations and the relevant application, so no changes are needed. |
Non-Functional Requirements
None specified