nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I add a user and allow them access to only one project?

Morgan_Thompson

I just want this user to be able to login and see the one project. However, the new group I created has no ability to login so I have to add him to the default jira-user group but then that lets him see all projects which is not what I want.

As this user is the only user in this new group, how do I grant this group login permissions so I can then add that group as a user in the one project?

Accepted answers

Ivan Tovbin

Hi Morgan,

The best way to do this, is to add this user (or group) to a project role. After that grant that project role proper permissions within your project. Also please note that by default Jira already has some project roles configured and all new projects come with a default permission scheme which grants different permissions to these roles. So you might wanna check the existing project roles and their permissions for a given project first.

All comments

Ivan Tovbin

Hi Morgan,

Morgan_Thompson

Thank you I finally got it to work. What I wound up doing was:

Create new user.
Create new group.
Grant new group login permissions.
Add the new user to the new group.
Remove the new user from the default jira-user group.
Add new group to User roll within the desired project.

John Stephens

I tried these exact steps. It makes no difference. The user see all projects.

Joe Pitt

JIRA works by GRANTING access. You can't restrict access. By default (BAD idea) it grants access to the group used to logon (used to be jira-users but may be different on your version). This is probably where you're getting the access from.

The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission. Then I suggest you setup user roles for the various functions like, tester, QA, Browse Only, etc. Then you can create one permission scheme to cover almost all projects. The project admin controls which users are put in the roles. This may be a big effort, but it will payoff down the road by making it easy to control access.

John Stephens

That's the thing, we didn't grant anything. The user just automatically has global access. This has to be a bug.

We're expecting a similar experience to every other permission system, create user, give specific permission. Done.

Joe Pitt

As I said, it is the default

John Stephens

So yes, I agree that jira-users having global access is an alarmingly bad decision, but we removed the user from that group as specified in the above steps, but...

The user still has access to all other projects. This is the bug.

Sergey Podaru

@Nic Brough -Adaptavist- Hello. I also have this problem. And i think it's problem with Jira Settings. Maybe u can show me pictures how see your settings? Because i'm in stumped

Nic Brough -Adaptavist-

Pictures would take too long, and would vary by version. So:

Check in "manage applications" to see what groups have "access" to Core/Software/Service Desk
For each permission scheme you have, remove any mention of those groups for the "browse" permission, replacing it with other roles or groups as required to let existing people in.
For each permission scheme you have, remove any mention of "anyone" for the "browse" permission, replacing it with other roles or groups as required to let existing people in.
For each permission scheme you have, remove any mention "any logged in user" for the "browse" permission, replacing it with other roles or groups as required to let existing people in.
For each project you have, check all the roles, removing any mention of those groups, replacing it with other groups as required to let existing people in.
Now add your new user into the group that gives them access, then add them into the right role(s) in the project you want them to have singular access to.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

project

permission

group