Replies: 2 comments 3 replies
-
|
and also reviewers should be able to just view the whole project including the project log. I really would like to get a realistic release plan for role management. I would like to write down a list of roles and their rights and then we should discuss, what to implement in what release. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I mentioned this thread to a colleague and she pointed out (very rightfully), that we need to support ANONYMOUS REVIEW ACCESS for double blind reviews. Therefore, we have to add an option to only show PSEUDONYMS (like in Google docs) instead of real names. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When working on a project with a couple of people, we need to have a granular role system.
Consider this use case:
We are doing a citizen science project.
We are integrating citizens in our research project.
They should be able to access a certain SET of DOCUMENTS and do CODING only.
Therefore they log in and only see the CODING TAB and the ASSIGNED DOCUMENTS in the SET, nothing else.
Or a Student research assistant only gets to see the documents s/he should CODE. Or just see the ANALYSIS TAB to do some analysis but not CODING or PREPARING.
So a PROJECT has MEMBERS which have PROJECT-SPECIFIC-RIGHTS (such as which TAB to see, which SET to work on, which ANALYIS TOOLS to use) and even maybe DOCUMENT-SPECIFIC-RIGHTS.
Beta Was this translation helpful? Give feedback.
All reactions