We are using a custom permission scheme, and Groups to separate user access by client. We had to remove the Browse users and groups global permission, as users where able to see other users, and in there Worked On list were able to see issues (summary only - click through said no access to issue - as desired).
However, the @mention functionality ceased to work for the users without this global permission.
Is there some way to configure via custom Project Roles or Teams or something so that we can still @mention people on the same project, but not see users and Issue Summaries from other client projects? I thought perhaps the Browse project role should be made as a Browse per Project role, but not sure it this is the right direction to go.
Any help would be appreciated:)
no there is no relationship unless something is configured wrong in a very special way (I could not even figure out how to do even if you wanted to).
Rather I expect the users that can see Issues (but should not) are listed for "Browse Project Permission" in the project. This is a total independent setting.
Could you probably please also check if "Admin Helper" for Permissions is giving a clue why there seems to be access to some issues where you expect that not to be (if everything was understood correctly)?
Cheers,
Daniel
Hello @Kurt Fairfield ,
I'm sorry, without "Browse Users and groups" permissions, it's not possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see that users and groups are visible from the permission summary. It is the Issue Summaries of projects that users have no access to that is of concern to me.
Does this permission also mean...
'Users with this permission can see the names of all users and groups on your site... AND THE ISSUE SUMMARY AND KEY OF EVERY ISSUE ON YOUR SITE'.
I can be okay with people seeing users and groups, but also see private project level information as well? I must be doing something wrong...
Your thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.