howto assign project rights for non-members
|Category:||Permissions and roles|
I think "non-member" and "anonymous" should be (dynamic) groups rather than roles.
It would be practical because then you could select what permissions anonymous users and non-members have on a per-project level rather than as a whole for the entire Redmine installation.
It also makes much better sense on a conceptual level.
#1 Updated by Martin Kos over 11 years ago
We have the same problem over here. As we are using a federated single sign-on system (shibboleth), all people from our community have a login, so they can create issues for public projects, even if anonymous users are not allowed to create issues. but some people from outside the community should also be able to create issues and add comments, event without a login. but we should make the decision if anonymous users are allowed to create issues on a per-project level.
hope this feature will be added to the to-do-list :-)
#2 Updated by Marc Dequènes over 10 years ago
I makes sense. This feature is really needed as you may wish to allow anonymous or non-member to open tickets on specific projects while having visible (not private) but member-only projects. Currently you have to give more rights than necessary to achieve the former, so this a security issue.
#5 Updated by Stanislav German-Evtushenko about 10 years ago
- project 1: anonymous is a reporter
- project 2: anonymous is a viewer
- project 3: non-member is a reporter
- and so on ...