I'm sorry, this is probably a VERY easy thing to do, but I am lost in how to give a user access to just one project in our Jira + Confluence OnDemand. I've been reading several of the documentation links, but I'm confused about the difference between groups, roles and permission schemes when it comes to this. Where to I start?
As an example, I need to set up a user (from another company) connected to a specific project. He can do anything within that project, but not see anything concerning other projects, including on his dashboard. I've set up a test-user to see how things work, but I'm not capable to find the answer myself. What documentation link is my recipe?
Grateful for any help.
It really isn't as bad as other people make it out to be.
1. Copy the default permission scheme to another like "Project-Client-Permissions"
2. Create a group, "Project-Client"
3. Add that group only to the perimissions you want them to have. For me, it is Browse Project, Create Issues, Edit Issues, Resolve Issues, Add Comments, Edit Own Comments, Delete Own Comments, Create Attachments, and Delete Own Attachments
4. Apply that Permission scheme to the project
5. Add a user and add them only to the Project-Client group (they should also be in jira-users by default so they can login)
Hmm. Doesn't seem to work for me. As soon as I give them jira_user they have access to all other projects as well. Did you have to change the other permission schemes? I tested this out myself by creating a bogus user and adding that user to both Jira_user and the new group that i created. Once I did that, the bogus user was able to access all other projects as well.
@Nereida Lark - I had the same problem and managed to solve it after reading the answer on this page: https://answers.atlassian.com/questions/180111/how-do-i-add-a-user-and-allow-them-access-to-only-one-project In short, you can add (via global permissions) the permission "JIRA Users" to the created group (group "Project-Client" in the above example). Then, you can remove the users from the "jira_user" group, and they'll still be able to login to JIRA, as long as they still belong to the "Project-Client" group.
that was it! "Any logged in user".
Oh my gosh, I've been screwing around with this all day trying to figure this out.
In the end what worked was to go into the Default Permissions scheme and change Browse Projects, from "Any logged in user" to "jira-software-users"
Now, using the steps above, I was able to add a user to a group "Client X", Create a Permissions Scheme called "Client X Permissions", set the permissions I wanted. And update the project to use the Client X Permissions scheme.
I also had to go to System > Applications > Application Access and add the "Client X" group to 'JIRA Software' and tick the checkbox for "can sign in"
Very confusing. Really should be easier to do this. Still trying to setup an Account Manager role for a specific project. This person should only have access to Project XYZ and should only be able to do limited create issue, add comments, add attachment, etc.
1. Created Account Manager role.
2. Project Permissions. You can't assign more than one permission scheme to a project. So I copied default permission scheme and added the (extra) specific permissions I wanted for project role: Account manager.
3. Associated this new permission scheme to Project XYZ.
4. Created test user and assigned test user to role Account Manager.
5. WTF! A user has to be assigned to a group. Groups have global permissions. So I removed account manager from users and cannot login. Created account-manager group and assigned user to account-manager group. It can login but gets blank dashboard with login link.
Hey Atlassian, could you make this any more difficult?
Ok, found the answer here:
You need to set/give/mummify this new group (account-managers) the Jira Users something or other so it can login. then everything works. It sort of makes sense but I took a lot of hallucinogens in college ;-[
OMFG, this is so damned confusing. Really, Atlassian, I want the normal security groups, except I want to limit which projects a user sees and can access. Why is this soooo complicated? This is unreal.
What did I expect to find? In the user record, a set of checkboxes in a tab. One is for access to all projects, If you uncheck that, then you choose which projects the user has access to, one per checkbox.
It's incredible how complicated a process you guys turn this into. Been pulling my hair for more than an hour on this now, it looks like I a large chunk of my day will go into this insanely complicated task.
"This user can access only this project" -> Are you all dumb in Attlasian and you did not figure out that that would be most common user request? Really? Have you bumped your head?
I can not f**** believe how much hassle is required to achieve this ... UNBELIEVABLE!!!
"It really isn't as bad as other people make it out to be." -> yes it is.
If you can describe a use case scenario is as "User can access project", that means that UIX should follow this scenario with "Chose project, choose user, assign" - not to do "just this 27 simple steps". That is bad UIX design by itself.
Ideally - it would be great if you could simply click a button 'Add User to this Project' somewhere in the project panel. If this button was very obvious then at a minimum it could help to start the process. I could see something like: 1. Create a new project. 2. Click the 'Add User to this Project' button (which is very easy to see) 3. Auto-type User name and select. 4. Assign User Role or accept default. Done.
This is related to Browse Projects in the Permissions Scheme settings. So, I believe that you'll be able to do it using a single Permission Scheme settings and an user group for the related project.
In other words, as an example, you'll have to:
1. Add this user to a single group
2. Change the related project role using the new group
3. In a new permission scheme, just change the Browse Projects value with the related group
4. Enable this new permission scheme in the related project.
After that, only the users members of the related group will be able to access that project. So, to avoid the access to other projects, perhaps you should review all the procedures and try to apply this kind of approach to other projects.
Also, this is the documentation related to this:
In case of further assistance, try to raise a new support ticket,
you could start by readin this
i prefer setting up Permission Schemes that are based on Project Roles so the Project Admin can easily choose which users should have access to browse the project and wich users should be able to assign and be assigned
besides you may create a sketch for your self and plan any kinds of permissions
I've been banging my head on the wall over this issue for the past few days. I have multiple projects, and multiple external teams working on different projects. I want to limit access and visibility of specific teams to specific projects and confluence spaces. The security/permissions scheme design on Atlassian platform is not only non-intuitive, and extremely laborious, it is plain stupid.
@Logostech Atlassian Support Is there any way of achieving project level access control without going through such a laborious process for each project? How about a tabular representation of the permission scheme where I can edit all cells without having to click through Add for each and every permission item?
At the and, I have managed to achieve mentioned.
However - if I have to do all those steps: http://blogs.2i-it.com/how-to-configure-confluence-and-jira-to-grant-a-group-of-users-access-to-specific-spaces-and-projects/ in order to achieve simple: this users/groups can access/see this project than really, someone is really stupid here, either me which requires for most common operation to be executed in as less clicks as possible, or people behind this functionality which in 6 versions of this product could not figure out the common need of the users and force them to spend an f**** hour to achieve the same.
I don't know if this has changed with versions, but it seems to be quite easy to do this now...
How about these steps:
I don't think you need to mess with permission schemes at all.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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