Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,458,170
Community Members
 
Community Events
176
Community Groups

Best practice for Bamboo permission management

cathy
cathy Nov 11, 2020

Hi 

I understand that Bamboo permission is additive. So if we define permission at project level, also set plan inheritance, then all plans will have the same permission.

 

Some personal plans are not meant to be seen by others. But because permission inheritance, they will be visible to others. What is the best practice to manage personal plan and public plans?

 

 

Answer
Watch
Like Be the first to like this
198 views

0 answers

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS

Atlassian Community Events

See all events