You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
great product from what I see so far. I know that "open company, no bullshit" is one Atlassian's your core values but I'm not sure whether that applies to "ALL" projects, especially when sensitive information should be shared, but not with the entire organization.
So the question is: Is there a way to restrict access to individual Team Central projects, have I just missed it, or is this not going to ever happen?
Use case: I would like to track a project that would include info that must not be shared outside of the organization (bound by NDA). To reduce the risk, I need to share the info with just a few people (that have signed the NDA). What would be the alternative approach? Keep that info in a dedicated Team central instance/org? The thing is, I would love to have updates on the project in my Monday morning digest, but if we can't restrict it, we need to track status elsewhere.
Thanks for any kind of thought,
Christian Czaia _Decadis AG_
Executive board member
230 accepted answers