I have a requirement from leadership to limit edit access for users as we introduce Atlas to our company. Is there a way to manage user permissions for Atlas so that only the core project team can create Goals and Projects, but all users can read Goals and Projects?
This seems to be a big gap in the Atlas product. Right now its all too easy for people to accidentally make changes to other peoples items, archive them etc. And as Atlas has no audit log there is no way to know who even made the change.
Adding to Jesica's question - I note that only the project owner and contributors can post project updates which is great. However, this level of security/control can be circumvented by a user changing the owner of an Atlas project (to themselves for example) or adding themselves as a contributor, opening the way for them to add post project updates.
Similar comment for goals - having free reign to edit goals created by anyone else in the organization makes me slightly nervous!
@Rachel Lin@Daniella Latham Are there plans to introduce a more granular permissioning model?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.