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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Would like to grant access to a project to an external user. Want this user to view only this project and should be able to create/view issues on this project. This user should not be able to view any other projects in my JIRA account.
Couldn't find a straightforward way to achieve this.
Dear @Vivek Chandraprakash ,
make sure that
Then open the configuration of your one project and grant your external user explicit project access:
Depending on your entire site configuration (which I don't know) other ways are possible.
So long
Thomas
Dear @Vivek Chandraprakash ,
was my answer useful? Then I would be happy when you click on the "green accept answer" button.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What's the point of creating the new group: external-jira-access and adding the new user to the group. Your steps do not include using the new group. Are we missing something?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Thomas that was super helpful! It set me off on the right direction :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Thomas Deiler this is helpful. However, on Cloud I noticed that when I added a user to a role on a project they did not have access, but when I added them to a group with the same permissions, then added the group to the role on the project, it did work. Do you know of any bugs with adding users to project roles instead of groups?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ben Upham It seems to be the natural expected behavior, that mapping users directly to a role should work. Otherwise it makes no sense that you can perform this action, or? Without knowing the details of your site configuration, I suggest to open a support ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using a free Jira and did everything as mentioned, nothing happend. Is it a problem with a free Jira maybe? Also, I am suspicious about the:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian community!
As documented here you cannot modify project permissions when you are using the Free plan. You cannot configure permissions to limit a users visibility to projects.
What is the Free Jira Cloud plan?
Permissions, roles, and issue-level security
Project permissions, roles, and issue-level security aren't customizable in Jira Work Management and Software Free.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the project a Team Managed project or a Company Managed project?
Do you have both types of projects in your instance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the project you want the user to access a Company Managed project or a Team Managed project?
Is the project a Work Management project, a Software project, or a Service Management project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, for the quick response. Company-managed software, a software project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will explain how to you might accomplish your goal of granting a user access to limited Company Managed projects, but first I want to bring up the other issues that can arise because you also have Team Managed projects.
The access management for Company Managed projects is handled through User Groups defined for your site, Permission Schemes assigned to the projects, and the Project Roles for the project.
Access management for Team Managed projects is entirely different. Refer to this document for details:
Typically access on Team Managed projects is set up as Open or Limited, which gives all licensed users of your JIRA instance some level of access to the projects. That would include this external user for whom you want to limit their access/visibility to only one project.
In order to prevent the user from seeing your Team Managed projects, each of those projects will have to have its Access set to Private, and then for each of those projects the users who actually need to access the project are going to have to be added to those projects directly, either individually or through User Groups.
Given that, is it still realistic to go to the effort of hiding the Team Managed projects and setting up the access to the one Company Managed project for this one external user?
To grant a user access to only specific Company Managed projects you need to
1. Grant the user product access to your JIRA instance.
2. Assuming your Global Permissions and Permission Schemes leverage the jira-software-users User Group to grant access to the projects, then remove the user from that User Group.
3. Create a new User Group for the user being granted access.
4. Modify the Permission Scheme for the target Company Managed project to grant permissions to that new user group.
(If you anticipate having other users that also need limited access, and that access may be to different projects, then I would extend this concept using Project Roles and additional User Groups, as I discuss in my response to this post.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.