You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.
We should move from staff status to more complexe permissions managment system.
At least, we should consider admin (right to break everythings, including email address, url, etc), staff (non destructive operations) and reviewers (see talks and vote).
They are several way to implement this:
one ManyToManyFields per role on Conference model
a Permission model (conf, user, role)
The second method is probably better to add future new roles.
The text was updated successfully, but these errors were encountered:
We should move from staff status to more complexe permissions managment system.
At least, we should consider admin (right to break everythings, including email address, url, etc), staff (non destructive operations) and reviewers (see talks and vote).
They are several way to implement this:
The second method is probably better to add future new roles.
The text was updated successfully, but these errors were encountered: