I have a case where we are wanting to allow vendors to get accounts on our jira instance and have access to just some projects.
The problem is that most of our projects have permission schemes with 'any logged user' used quite heavily. I'm trying to find the best way to remove the wide open access we have now and break users into 'employees' and 'vendors' and modify the permission schemes.
My thought was to:
1) at user creation time put a user in the group either 'employee' or 'vendor'. I'm assuming this would have to be a manual process doe after user creation since by default everything just goes into jira-users group. it seems like this would have to be post user creation, so it would create a small window where vendors could see everything.
2) Edit each of the permission schemes to :
a) remove all references to 'any logged in user'
b) replace the removed 'any logged in..' permissions reference with a pair of permission rules 1) group(employees) and 2) role(Vendor)
This way I get to keep the global access that we need as a company, but keep vendors out of them unless they are added to the Vendors role of that project.
I don't want project admins to have to pick all employees for a role ad then keeping having to update it as new hires come on, so this is why I used a group for employees
I'd like to remove the need for IT to remember which group to have to put a new user into, is there any jira setup configs that would let me add an option from the products to pick, Jira -Employee or Jira - Vendor.
Or, is there a a better/simpler way to accomplish this?
HI @Jay Keck
in my opinion you will for sure have to remove all the "any logged in users" permissions from crucial topics.
And the idea with External / Internal groups is what I know as "common" and easier to manage. For sure you now have the one-time-effort to reset all the groups.
Perhaps a Security Scheme per project could help additionally!?
https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html
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.