Expand my Community achievements bar.

Latest Community Ideas Review is Out: Discover What’s New and What to Expect!

Private Updates

Avatar

Level 5

3/16/17

It would be nice to make updates that you choose to be private with other colleagues and that not everyone can see them until you choose for them to.

16 Comments

Avatar

Level 3

10/22/19

We would really like this. Sometimes there are ideas posted in the update stream, or conversation, that should be captured but not be visible to the internal customer who originally requested the project.

Avatar

Level 3

12/17/19

Having more privacy options under the Updates section instead of just the "Private to my Company" being the only option is a LOT more pressing if you use groups instead of companies to represent the org chart in Workfront. We have recently consolidated the majority of our companies into one to allow our group admins to manage accounts of auto-provisioned/unallocated users, however, in doing so we have effectively rendered the private updates feature useless as vast majority of our users are now in the same company. It feels like the update privacy feature could use an update: for example, instead of the trigger say "Private to my Company" it could say "Make this update private", and when tripped, it would reveal several options:

  • private to one or more named users,
  • private to select teams,
  • private to select groups, or
  • private to a user's company


Avatar

Level 2

7/30/20

We need this to. We work within internal projects. We would need to have a feature where we can share notes that are only visible to one particular team, for various reasons such as QA, technical notes, and questions that are not meant to be seen by any other team.

Avatar

Employee

1/10/24

Thank you for the submission! We think this is a good enhancement to the Workfront platform overall and this product area in particular!

 

Workfront currently prioritizes large-scale, foundational enhancements such as the new Reporting experience and changes to the core data model, so this item does not fit in our near-term roadmap. As such, I am marking this as Declined now, but we'll keep this in our backlog for the improvements for this area so that we can revisit the decision in the future.

Status changed to: Declined