You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi Derek, you can make a project private by limiting it's users & roles. If you're a JIRA admin, you can access these settings by clicking on the gear icon in the top-right, then selecting 'Projects'. Once the page loads, click on the project you want to update, and go to the 'Users and roles' section of the project settings. From here you can add a new user to a specific role by selecting the 'Add users to a role' option in the upper-right, enter the desired user and select the appropriate role, then click 'Add'. You can also remove users/roles from the list of existings users/roles by hovering over the user/role and clicking the trashcan icon.
Here's a couple of help articles that should give you further details on this process:
I'm spinning up a new team to manage a new ATS contract.
We've begun the procurement process and are starting to build a backlog or requirements.
One of the bidders is our current provider, for obvious reasons i need to ensure they do not have access to the new board.
I've created a new board and tried to ensure that only a few can access it. I've run a few tests and so far everyone can access it.
I've followed your advice from this post and others that I've found in this community, but I've been unsuccesful.
I believe the basic process still applies to cloud, but the admin sections may have changed names/labels on things since I provided my original answer.
If you are using a "classic software" project then the 'Users and roles' section is now called 'People'. If you are using a "next-gen software" project then the 'Users and roles' section is now called 'Access'.
The links I provided in my original answer should have been updated to reflect any changes in cloud, as those are maintained by Atlassian.
@Stefanie SullivanSorry, I'm not sure I follow your question. Permission schemes are required for Jira projects, as they determine who can access the project & what they can do.
For scalability on permission schemes, best practice is to use Project Roles to assign permissions, and then add Groups to said Project Roles, and then Users to said Groups. This makes it so that when adding/removing users, you do not need to alter the project's settings to add/remove individual users, and instead can add/remove a user to/from a group to maintain permissions.
Hope this answer helps, but if you still have questions please feel free to ask.
If you have a scheme that has most of the permissions you want, starting with a copy of that would be fine...but yes, generally you would start with a blank scheme and add users/groups/roles to permissions as needed for said project.
The browse permissions determines who can see said project, so limiting that to a group would mean only members of that group can see it (aside from admins who would be able to see it on the admin backend). However, best practice for permission schemes would be to set permissions based on project roles, and then add groups instead the appropriate roles, and users into groups. This makes it so you have less project administration to do later, as you simply have to add/remove users from specific groups to gain/remove access, rather than needing to maintain group/user permissions on each individual project. This article may help: https://community.atlassian.com/t5/Agile-articles/Best-Practices-Restricting-Projects-in-Jira/ba-p/654535
Roles are a globally managed item, so they can be used across projects...and they are definitely available for standard projects as they've existed long before next gen projects were a thing.
Roles come into use on a project when they've been assigned in a scheme or other settings that allow roles. So while you manage them globally across your whole Jira instance, they won't actually be used unless you specify the one(s) that should be used in each project.
As for creating new roles, I would say that depends on what makes the most sense for your teams & terminology. There is no difference between various roles other than names, so it's all in how & where you use them that determines the differences between them. So if the default role names don't make sense for your usage, then creating new roles is always an option.
This article should help give a better overview of roles and their uses: https://confluence.atlassian.com/adminjiracloud/managing-project-roles-776636382.html