I'd suggest we start the discussion about how we use user roles and see if we can streamline the process for requesting upgraded permissions.
Review of roles
Currently, we have:
| Role |
Throttling |
Forwarding |
| Citizen |
Strict rate |
❌ |
| Researcher |
No throttling (I believe) |
✅ |
| Admin |
No throttling |
✅ |
I'd suggest that we have an intermediate role for allowing forwarding and keep throttling active (name to be defined):
| Role |
Throttling |
Forwarding |
Backups |
| Citizen |
Strict rate |
❌ |
❌ |
| Contributor |
Strict rate |
✅ |
❌ |
| Researcher |
Less strict rate (still throttled) |
✅ |
✅ |
| Admin |
No throttling |
✅ |
✅ |
Automated requests
In addition, it'd be a great addition, although I understand it won't be a priority, to reduce the manual work on updating roles manually via the rails console. Currently, the workflow involves the user sending us an email, us going into rails, and doing the change manually. I'd suggest we revise that as it is quite a bit of cumulative work.
I'd suggest we start the discussion about how we use user roles and see if we can streamline the process for requesting upgraded permissions.
Review of roles
Note
Related #425
Currently, we have:
I'd suggest that we have an intermediate role for allowing forwarding and keep throttling active (name to be defined):
Automated requests
In addition, it'd be a great addition, although I understand it won't be a priority, to reduce the manual work on updating roles manually via the rails console. Currently, the workflow involves the user sending us an email, us going into rails, and doing the change manually. I'd suggest we revise that as it is quite a bit of cumulative work.