How do I add a client to my Jira project without letting them view other projects?

Okay guys, I know this sounds simple and straightforward but I've been looking for an answer for 2 weeks and am ready to give up on JIRA if I can't solve this. The simple question is:

How do I create a client user that will be allowed to view her project and even edit the backlog, etc without seeing any other projects?


Someone referred me to this documentation and I really tried diligently to follow the steps but I don't think I've gotten what I was after.

I went through the first pre steps but they seem vague. It says the article assumes that I:

  1. Created the users in JIRA. 
  2. Populated these users into client-specific groups (i.e. all users from 'Company A' are grouped into the 'Client A' group) 
  3. Granted these groups JIRA access by adding the groups to JIRA Users global permission
  4. Removed Internal Project access to client-specific users by removing them from the default JIRA Users global permission. (i.e. removing jira-users group)

So what if I didn't do steps 2-4? I've spent a half hour trying to figure out where in settings I do this but it just doesn't make sense to me just starting with Jira. I think I may have figured out 3 but this just seems all hairy for just trying to give a client access to one project. Any other articles you could recommend to help me through these basic steps? I've already searched in the documentation myself.

I even took a 2 hour lynda course (outdated and the interface wasn't the same) and couldn't solve this. Can someone please help me out with some simple steps? I barely installed JIRA cloud, I started a project, so my settings shouldn't be too much different from other how to's shown. Is there a reason this seems so difficult to me?

2 answers

1 vote

If you don't do steps 2-4, you won't be removing their access to other projects.

You've run into the age-old problem that the default setup of JIRA is not friendly to those who want to start restricting stuff.  You need to unravel that problem first, then you'll find the rest of the process quite easy.

JIRA needs a way to say "this person can use JIRA".  The default setup is to use the jira-users group for this.  To enable the "can use", that group is added to the *global permission" for "can use".

Then (and this is where the problem is), Atlassian put jira-users into the default role of "users" in projects.  So all projects, when they are created, have jira-users listed as users.  Which grants them access to the project automatically.

You need to remove that mis-configuration first.  There are ways to do it:

  1. Create a new group for "can use", add everyone into it, put it into the global permission, delete jira-users from the global permission, then remove your clients from jira-users
  2. Go through all the projects and remove jira-users from the roles (also remove it from the default roles)

2 is a lot easier in the long run, but it is a bit of a pain up front if you have a lot of projects already

Anyway, you now have gone from "if you can log in, you can use all the projects" to "You have to be added to a project or group to be able to use it".

And the second part is simple and intuitive now -  you can take your groups (or individual users) and add them only to the projects you want the clients to see, and that's it, they'll only see those projects.

Thank you very much Nic! I'm going to try this first thing in the morning when I go into work but it all seems a little clearer now thanks to your explanation. I'll let you know what I run up against. 


Thanks again!


No problem. Although it's quite hard to explain clearly, so if you get stuck, blame my prose before you think you've missed something! Then ask, and we'll try to explain what I've written badly!

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

372 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you