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
Hey, so an team member accidentally posted a Goal update for something they aren't an owner of (the contents of the update was for one of their projects - might've been a case of tab confusion).
Which prompts two questions:
1. why aren't there any permissions for goal updates?
2. why can't goal updates be deleted by the goal owner?
Thanks for the feedback - those are both great questions! As we've rolled out Atlas we've kept the permissions model very simple for now, but it's clear that we need to add much more fine-grained permissions to prevent scenarios like the one you experienced above. I'll work with the team to get this prioritised.
Likewise, there's a lot more CRUD operations for things that we need to add, such as making it possible to delete an update. I suspect we'd want to introduce permissions first before we introduce deleting updates, to prevent any unwanted accidents.
Apologies that Atlas has neither of these capabilities yet today.