Hey everyone,
i'm wondering if this is a good and more efficient way of managing my permission scheme. We have a lot of groups so I was thinking I can give all my groups the 'Browse projects' permission. For everything else rather than adding in each group can I just use the 'Application - any logged in user' permission?
If they are already in the group that has the browse permission they should be able to access all the other permissions if it has the 'Application - any logged in user' permission right?
My other question is if I'm not part of the group that doesn't have the 'Browse projects' permission. I won't be able to do anything inside that project even if the same permission scheme has the 'create issues' permission has the 'Application - any logged in user' permission right?
Hi @Hoc without browser project permission, User can only create issues, but they can't see that issue after creation nor they will be able to edit that issue or any other issues. When they try to view there created issue they get an error message :-
If user is having Browser project permission and you set Any logged in User in Create/Update issue permssion, in this case user can create/update/edit issues. Able to access all permission.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.