Skip to content
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

"Behavioural Quality Control" and "Imaging Quality Control" modules should have distinct permissions #5718

Closed
johnsaigle opened this issue Nov 21, 2019 · 1 comment · Fixed by #6041
Labels
Beginner Friendly PR or Issue appears to be easy for someone to use to familiarize themselves with LORIS Category: Feature PR or issue that aims to introduce a new feature Category: Security PR or issue that aims to improve security

Comments

@johnsaigle
Copy link
Contributor

Currently both use a single permission "quality_control". It would be better to have two separate permissions to allow for more granular configuration of a project.

Neither of them appear to have any editing functionality so I think it's safe to have a single "view" permission and no "edit" permission, but let me know if I'm wrong on this point.

@johnsaigle johnsaigle added Category: Feature PR or issue that aims to introduce a new feature Category: Security PR or issue that aims to improve security labels Nov 21, 2019
@racostas
Copy link
Contributor

strongly agree @johnsaigle.

@driusan driusan added the Beginner Friendly PR or Issue appears to be easy for someone to use to familiarize themselves with LORIS label Nov 26, 2019
AlexandraLivadas pushed a commit to AlexandraLivadas/Loris that referenced this issue Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Beginner Friendly PR or Issue appears to be easy for someone to use to familiarize themselves with LORIS Category: Feature PR or issue that aims to introduce a new feature Category: Security PR or issue that aims to improve security
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants