Atlassian Projects and Goals access management is now available!

[#1]

We’re excited to announce that you can soon control who can access Atlassian Goals and Atlassian Projects!

Like other Atlassian products, product access to Goals and Projects will be managed in Atlassian Administration. You can give a user or group access to both Goals and Projects, or only one.

A user who has access is allowed to view, create, and update goals or projects and browse their respective directories. A user who doesn’t have access is not able to do any of the above.

We’re rolling out to a small number of sites in early access first. Then, throughout January, we’ll roll out to all other customers who are using Goals and Projects.

If you have any questions or feedback please leave them as comments below and we’ll do our best to address them!

A note for Atlas customers

Enabling the ability to control product access for Goals and Projects allows us to start migrating Atlas customers to the new Goals and Projects experiences. We’ll notify admins before this happens to provide more information. Read our previous Atlas announcement to learn more

[Lai, Ssu-Yuan (賴思元)]

Great to see this feature being released! 🎉 It’s definitely helpful for us!

I’m wondering if there are any plans to support access control for a single Project or a single Goal in the future? I believe some teams might also prefer more granular, item-specific management.

[Filipe Vítor]

I assumed the purpose of this feature was to allow users to control who could view or manage specific goals or projects. Is that also possible now?

[Nir Nikolaevsky]

Hi @Lai, Ssu-Yuan (賴思元) @Filipe Vítor, 

This feature was specifically implemented to help admins control project and goal access on the site-level.

We're also looking at improving the access management of specific projects and goals but that will likely be worked on throughout the year.

Note that we do have private projects. Only users who are added as contributors or followers can view private projects. The work I've mentioned above will improve and expand this functionality. 

Can you tell me more about why you want project and goal specific controls and how you'd use them? Also, if you're open to chatting about this please send me your preferred email to nnikolaevsky@atlassian.com and I'll reach out when we conduct customer interviews.

Thanks and happy holidays! 

[Dirk Lachowski]

@Nir Nikolaevsky 

Note that we do have private projects. Only users who are added as contributors or followers can view private projects. The work I've mentioned above will improve and expand this functionality.

While this is good to know, it would be much more important to have private goals, eg. for financial goals. Any plans for that?

[Jean Gordon]

How can this be removed as we dont allow access across projects but you added and automatically applied.

[Darrel Jackson]

Disappointed that read-only vs. read-write roles haven't been implemented.

The use case is Goals for organisational strategy. We'd have a large number of read-only users (i.e. the whole company) but only a handful of read-write users (i.e. the corporate strategy team).

Also disappointed that deny-by-default private goals haven't been supported i.e. you need to be explicitly invited to the goal to be able to read/update it.

The use case is many goals are commercially sensitive - both in terms of the goal and the updates posted against the goal. You'd only want certain people to have access e.g. execs, account teams.

[Stijn Veer_ van der]

Great first step. What would make this perfect is differentiating betweet read and write acces. We don't want everyone being able to create new goals. This would make Goals very messy for the organizational goal structure. 

[Stephen Neil]

There will be great appetite in our org for using goals however I know our exec team won't accept use until read/write access and goal-level access control is a reality. Watching these development with interest.

[Harrison Ponce]

Great update!

I know this was standing in the way of Atlas customers being migrated to the experience. Is there a date or time period when we can expect that transition rolling out? We're very eager for this move!

Also, is the ability to switch a project or goal's visibility between public and private on the roadmap? Sometimes my clients are starting one out and pick the wrong privacy option and they are unable to change it later without recreating the whole thing and archiving the old one.