The mega nav needs to contain the following:
1.People
2.Posts
3.Programmes
4.Placements
5.Revalidation
6.Cases
7.System Admin– includes Role Creation, Permissions Management, Password Management
8.Data Admin
The following will be in the top navigation, but not part of the meganav - tbc if they are all in scope:
9.Settings – includes Password Management (own), e.g. Notifications Preferences
10.Notifications
11.Help
Design specifications can be found here - TIS_ Megamenu specs
Field labelling is discussed in the attached:
For Discussion
| # | Question | Comment | Owner |
|---|---|---|---|
| 1 | an the security model be applied at the 2nd level? i.e. exclude certain functionality from particular user types? | Alex Dobre (Unlicensed) | |
| 2 | will the team managing ref tables be central v local? | Alistair Pringle (Unlicensed), Joanne Watson (Unlicensed) | |
| 3 | will the team managing users be central v local? | Alistair Pringle (Unlicensed), Joanne Watson (Unlicensed) | |
| 4 | could there be an overlap of the two roles? | Alistair Pringle (Unlicensed), Joanne Watson (Unlicensed) | |
| 5 | how many groupings should there be (roughly) for reference tables and what are they? | Alistair Pringle (Unlicensed), Joanne Watson (Unlicensed), Ashley Ransoo |
Add Comment