Limit project updates to specific people

[Orlando Kelly]

Is it possible to use groups to allow project updates to a specific set of people.

In general the open approach to team central is great for disseminating information to everyone in the system.

However we have been asked if it's possible to limit project updates on specific projects to a specific group. 

Some projects are confidential and only certain people need to be updated on it, rather than a wide audience. 

Is is possible add some sort of RBAC to projects to limit who can see the updates

[Mary Raleigh · Accepted solution]

@Orlando Kelly , looks like @Paul Benario beat me to it! 

Your use case makes total sense, you need privacy settings so certain project updates are limited to a set audience. 

Stay tuned as we share features to meet your use cases at our annual customer conference, Team 22, in April. 

I'll be share to post updates after the event in this community group too!

[Orlando Kelly]

Looking forward to see what you have at the conference. 

[Rachel Lin]

Hi Orlando! I'm Rachel - a product manager on the Team Central team. Thanks for the feedback :) 

Can you share more about your use case - what specifically would you like to restrict? What is RBAC?

[Orlando Kelly]

Hi Rachel, basically in some cases we want the ability to assign a group to a project in team central, only members of that group can see the updates etc

[Rachel Lin]

Hi Orlando, I hope you are doing well. I'm coming back to this conversation as we are now exploring private projects and we would love to get your feedback on a few designs. Your input will be really valuable to getting this feature shipped in a way that solves your use case. If you're open to it, can you please send me an email rlin2@atlassian.com so we can coordinate some time to chat? Thanks.

[Paul Benario]

My understanding is that permissions/restrictions do not exist at this time, but they are planning to add that functionality to mirror Jira's permissions setup (or be similar at least)