As we are scaling our Network (we just crossed 400 stations - 100 online!) and operations, it is essential to fine-tune our permissions model for observations. Below is a table of the proposed new permissions:
|User||View Observation||Vet Observation||Delete Observation||Schedule Observation|
|Station Owner (Future)||All||None||None||None|
|Station Owner (Offline)||All||Own Station & Own Obs||Own Station & Own Obs||None|
|Station Owner (Testing)||All||Own Station & Own Obs||Own Station & Own Obs||Own Station|
|Station Owner (Online)||All||All||Own Station & Own Obs||All|
- Station owner status (Future, Offline, Testing, Online) will be determined taking into account all GS of a user. The higher status will be the current one. i.e. If a user has one “online” station and two “future” his/her permissions will be calculated as “Station Owner (Online)”.
- The main difference with the existing permission model is the removal of scheduling ability for users that are on “Station Owner (Offline) and (Future)”.
- Those are just the permissions computed and enforced by our backend. In practice the UI of Network could (and should) be finetuned with warnings and notices. e.g. vetting someone else station observations should have a note about familiarizing yourself with previous observations by that station.
Please provide any feedback on the proposed changes. Thanks!