Access Control Levels
Certain parts of the page may only be accessed by certain groups. Certain parts of the page may only be changed by certain groups. Certain is not always certain but always certain.
- Groups:
- anonymous (everything and -body, that is able to issue an http request, i.e. to visit the page)
- eestec members
- LC1 members
- LC2 members
- LCX members
- all-CPs (all means from all LCs)
- LC1-CPs
- LC2-CPs
- LCX-CPs
- all-XYZs (all means from all LCs; XYZ being some special function)
- LC1-XYZs
- LC2-XYZs
- LCX-XYZs
- board
- chairmans
- chairman-BAs
- treasurers
- treasurer-BAs
- VC-EAs
- VC-EA-BAs
- VC-IAs
- VC-IA-BAs
- VC-PAs
- VC-PA-BAs
- COC
- COC-CPs
- OC
- IntCommittee1
- IntCommittee1-CPS
- IntCommittee2
- IntCommittee2-CPS
- IntCommitteeX
- IntCommitteeX-CPS
Further subgroups for BAs might be interesting.
Most of the time, the CPs of something can change content which is then either available to anonymous, to everybody or only to the ones from something of which the CPs are CPs.
When there is no CPs of some group then everybody of that group has the rights which normally only the CPs of a group have. This is the case, e.g. with the board and the OC.
CPs normally have the most rights in the group. However some rights can be delegated to a subgroup (XYZ), e.g. the publications persons in the LCs.
It should be possible to change the access level of some item without to much effort, as this might happen from time to time. Also new XYZs should be supported by the system.
As the people in a group share their rights, they probably also want to share their experiences with these rights, need the same information to use their rights and other people normally also want to bother people with the same rights - it therefore probably makes sense to be able to send email to each group, i.e. an access control group should form a mailing list.
Newsletter January Released
