Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restrict Browse Projects to anyone except user of a specific group


i have a situation like that:

We use JIRA Software company internal with a very open and transparent environment.

Therefore i applied for the most projects the "Browse Project" also for "anyone in the web".

Due to the fact, that jira is running within the corporate network that should be fine.

Now we also got some external companies working on specific projects.

What is the best way to limit their access only on projects they are added but keep it open for all the other user.

I think i must get rid of the "anyone in the web" but i have no idea how to achieve something like "anyone except..."



1 answer

1 vote

Jira does not do "restrictions", it is permissive.  If you want someone to see or do something, you explicitly give them the right to do it.  If you want to prevent them seeing or doing something, then you do not give them the right to do it.

What you need to do is remove "browse project" for "anyone on the web", then re-add your internal users via a different rule like "browse project = user in role developer" (the add them to the project developers role as individuals or via some groups)

Then you can add your external users to the projects they need to see, without them getting access to otheres.

thank you for the answer, that is exaclty what i try to avoid :D

cause therefore i eighter have to add the user to all projects which is quite some kind of labor intense ;-) 

or i must create a group and add them there, which results also in a very labor intense job, cause there is no bulk add afaik

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

193 views 6 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you