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; } } }

Guest access to JIRA

nils_grashorn

Hello,

we have quite a large user base in our company's JIRA system and everything is set up in that way that a new user who is granted application access will be able to view all boards and their stories (the default user has these rights).

We now want to invite guest users on specific projects. These should be restricted to be able to view and edit only a certain project.

Can this be done without restructuring the whole access system?

Accepted answers

Nic Brough -Adaptavist-

You would find it better to remove the "application user can see everything", but there is a slightly higher maintenance way to do what you want.

Create a new group for "guests". Give that group access to *only* the project(s) they should have. Add that group into the "can use application" global permission, but not the old "can use" group.

This is higher maintenance because you're going to have to remove the guest users from the old "can use" group every time you create a new guest.

unknown

Hi Nils,

I think that some aditional info can help:

Can you use only one role, or a small quantity of them for all your customers with the same permission scheme for all your projects? If not, would it be too difficult to achieve?

Have you a too large quantity of permission schemes that would take a lot of time to change them?

A basic approach would be to create a new permission scheme with the browse permission only for internal workers and guest users (role) and then change the permission schemes in your projects.

All comments

Nic Brough -Adaptavist-

You would find it better to remove the "application user can see everything", but there is a slightly higher maintenance way to do what you want.

Create a new group for "guests". Give that group access to *only* the project(s) they should have. Add that group into the "can use application" global permission, but not the old "can use" group.

This is higher maintenance because you're going to have to remove the guest users from the old "can use" group every time you create a new guest.

unknown

Hi Nils,

I think that some aditional info can help:

Can you use only one role, or a small quantity of them for all your customers with the same permission scheme for all your projects? If not, would it be too difficult to achieve?

Have you a too large quantity of permission schemes that would take a lot of time to change them?

A basic approach would be to create a new permission scheme with the browse permission only for internal workers and guest users (role) and then change the permission schemes in your projects.

nils_grashorn

Both answers helped actually. I set up a new group for guests, granted them application access and then edited the permission schemes for the previous projects as well as creating a new scheme for including guests to a project.

Thanks a lot for the help!

Bruce Fint

@Nic Brough -Adaptavist-, does this add users? I would like to permit 'management' to see status of issues/projects via a custom dashboard, but they have no interest in doing any work in JIRA. It would be read-only for them.

Nic Brough -Adaptavist-

Adding users is done in manage users, then you add them to the group.

Bruce Fint

Yes, I'm familiar with how to add a user. I wasn't sure if 'create a new group for guests' was somehow different.

You're still burning user licenses and paying the JIRA fees and the add-on fees per user.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software