Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

When we add a new JIRA User to JIRA cloud site, does he/she sees all the projects in that site?

Hansika Wijenayake
Contributor
September 30, 2021

Hey all,

Hope all of are doing well and staying safe. I am going to raise a very basic but a paining question for me

When we add a new JIRA User to JIRA cloud site, does he/she sees all the projects in that site? 

Our main requirement is to invite new users to JIRA site, but they should not see any projects with the first visit till relevant projects leads add them to relevant projects

 

Cheers,

Hansi

2 answers

2 accepted

1 vote
Answer accepted
Callum Carlile _Automation Consultants_
Community Champion
September 30, 2021

Hi @Hansika Wijenayake 

Users in Jira can only view the projects which they have permission to, which is dictated by each project's permission scheme. So as long as there is a particular group/project role added to the Browse Projects permission of all of the permission schemes for all projects which should be 'hidden' to the new user, then they will not be able to view the project as long as the new user isn't a member of that group/role (unless they are made a Jira admin, in which case they would be able to see all projects)

Hansika Wijenayake
Contributor
September 30, 2021

Hey Callum,

Thanks a lot for the prompt response. I am trying to further understand the scenario

 

In our team, we have internal team members and external sub contractors who want to access JIRA. But only internal team members should have read/write access to all projects to all internal projects, but sub contractors should only be invited (s they should not see any projects) and later on, there PMs can add them to just few specific projects that they should use. Permission schemas will be same for all the projects

 

So, for internal users, there will be a user group called "Internal" and for sub contractors, there is will be another user group called "sub contractors". Our permission schema will be defined with below rules

 

1. Users in "Internal" user group will have browser permission to all projects

2. Users in "Sub contractors" user group will not have browse permissions for all projects, but if they are added to a specific project, then they will have access just for that project

Is this possible and does this make sense with my scenario?

 

Cheers,

Hansi

Callum Carlile _Automation Consultants_
Community Champion
October 1, 2021

Hi @Hansika Wijenayake 

This mostly sounds like it will work, however I would consider using a project role rather than a group for the external users for the browse projects permission in the permission scheme - as you said above, if the permission schemes are to be the same for all projects, then by adding an external user to the external group, they would have access to all projects.

However if you use a project role for the browse issues permission, the PMs would be able to add these users to specific projects by adding them to the role in the project, after which they will have access to the project.

The groups will work fine for internal users as all users have all project access.

Hope this makes sense!

Hansika Wijenayake
Contributor
October 5, 2021

Thanks a lot Callum. I will try this out

Like John Funk likes this
0 votes
Answer accepted
John Funk
Community Champion
September 30, 2021

Hi Hansika - It will depend on the Permission Scheme for each project. The user needs Browse project permissions to see the project.

Hansika Wijenayake
Contributor
September 30, 2021

Hey John,

Thanks a lot for the prompt response. I am trying to further understand the scenario

 

In our team, we have internal team members and external sub contractors who want to access JIRA. But only internal team members should have read/write access to all projects to all internal projects, but sub contractors should only be invited (s they should not see any projects) and later on, there PMs can add them to just few specific projects that they should use. Permission schemas will be same for all the projects

 

So, for internal users, there will be a user group called "Internal" and for sub contractors, there is will be another user group called "sub contractors". Our permission schema will be defined with below rules

 

1. Users in "Internal" user group will have browser permission to all projects

2. Users in "Sub contractors" user group will not have browse permissions for all projects, but if they are added to a specific project, then they will have access just for that project

Is this possible and does this make sense with my scenario?

 

Cheers,

Hansi

Like John Funk likes this
John Funk
Community Champion
October 5, 2021

Yes, that makes sense and is a good plan.  :-)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events