Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

How do I set user access to only one project?

So the user can only see one project and not have access to the rest of the projects

Please explain in full

4 answers

0 votes
Jack Community Leader Dec 23, 2019

Make sure the individual is not in any role/group that has permissions to the other project. Include the user in permissions for the on project. Project settings > permissions.

0 votes
Deleted user Dec 23, 2019

Hi @سید مصطفی مرتضوی ,

First, create project permission to that specific project and add that user to the project role.

Please go through the below documentation for complete information:
https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html
https://confluence.atlassian.com/adminjiracloud/managing-project-roles-776636382.html

Regards,
Kishore Kumar Gangavath.

0 votes
Joe Pitt Community Leader Dec 23, 2019

JIRA permissions

First, by default JIRA has a horrible permission scheme that violates security best practices by allowing everyone that can logon to do just about everything.

 

JIRA works by GRANTING access. You can't restrict access. By default, it grants access to the group used to logon (see Global permissions to see the "can use" groups and admin groups).  This is where users are getting their access.

 

  1. 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.
  2. Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
  3. By using project roles, one permission scheme will cover all projects. The project admin controls project role membership
  4. If the project leads want everyone that can logon access to the project they can add the logon group to a project role with the desired permissions.

 

This may be a big effort, but it will pay off down the road by making it easy to control access.

 

Most of the 'old timers' use project roles. It meets the best practice for security and gives complete control to the project lead for access to their project. JIRA comes with many project roles, but you can add more if you have a special need.

Hi @سید مصطفی مرتضوی Jan
If these right answers aren't clear enough for you till now, you could reach me to explain it more in Persian if you need it. My Contact details are also available through my Atlassian Profile and Linkedin account.

Suggest an answer

Log in or Sign up to answer
TAGS

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