-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revisit permissions given to our various roles #1060
Comments
Ravan and Datacup are too different profile to be used to validate a scenario. Ravan would have request, unrequest and cancel but aliens like Datacup would only have request. |
Does it means that I should only add task.request (manually since it is not possible through the UI) to Datacup for now? I don't get why person like Ravan can manage users, and why Datacup cannot cancel or unrequest their own tasks. |
No until we got feedback from Datacup confirming that they are using the farm.
Because there is no segregation between our recipes and aliens-created ones. |
Didn't realized you weren't in CC of the mail where they tell us they do and they have perm issues to start a task ... sorry about that |
Ah that's good news. New permission in order I believe |
Fixed by #1063 |
These are the various permissions we give by default for every roles we have in the UI:
I don't get why
editor
role has nottasks
permissions, which basically forces us to grantmanager
role to persons like Ravan or our Datacup friends so they can request, unrequest and cancel tasks. But at the same time, it given them way too muchusers
permission.Shall we also add
tasks
permissions given tomanager
role toeditor
role?The text was updated successfully, but these errors were encountered: