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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,659
Community Members
 
Community Events
185
Community Groups

[Access Level] Restrict access to all "open" or "limited" projects for some users

Hello, 

I would like to restrict the visibility to ALL ( already existing or future) "open" or "limited" projects for some users. 

Example:

I have the following users:

  • user1@aaa.com
  • user2@aaa.com
  • user3@aaa.com
  • foo1@bbb.com
  • foo2@bbb.com
  • foo3@ccc.com

 

What I need is to let only users belonging to "@aaa.com" to browse "open" or "limited" projects (already extisting projects or future projects).

So @bbb.com, @ccc.com and @whatever.com must never see/browse"open" or "limited" projects (already exsisting or future projects).

 

Thanks

 

1 answer

0 votes
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 28, 2021

Hi @Pietro Luise and welcome to the Community,

I noticed this is quite an older question, but it never got answered. Possibly, you already found an answer in a different way. Yet, still: the only way to restrict access to projects in the way you describe, is by changing the access level of your projects to private and explicitly specify who can access each project separately.

As I mentioned, hopefully you found a way around this already. If not, hope this helps!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events