Difference between revisions of "PrivilageSystem"
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Update}} |
||
| + | |||
==Potential Improvments to the privilage system== |
==Potential Improvments to the privilage system== |
||
| Line 18: | Line 20: | ||
*Remove validation by qualification status and replace with privilages<br> |
*Remove validation by qualification status and replace with privilages<br> |
||
eg. Sign up as a DM is done by privilage to sign up as DM not by qualification status of DM |
eg. Sign up as a DM is done by privilage to sign up as DM not by qualification status of DM |
||
| + | |||
| + | |||
[[Category:Website]] |
[[Category:Website]] |
||
Latest revision as of 23:25, 9 February 2019
 | This article needs to be updated. |
Potential Improvments to the privilage system
- Separate privilage groups from qualification status
- Qualification Status groups can be members of a privilage group
eg. Trainee DMs, New DMs and Full DMs are all members of the DM privilage group
- Individuals can also be made members of a privilage group
eg. Web developers can be members of the web_developer privilage group
This would allow a sub group of the IT team who do web development
- Individuals can be given individual privilages
- As already permitted
- Privilages assigned by qualification status can be expired when crew membership is revoked however individual privilages and privilage groups can be retained.
- This would allow people who maintain an active interest in WSC to access things like the gallery, but if they no longer actively participate they don't need rota access
- Remove validation by qualification status and replace with privilages
eg. Sign up as a DM is done by privilage to sign up as DM not by qualification status of DM
