Hi team,

We have had a user raise a request for the Atlassian Access product to be able to have granular control over managed personal workspaces and allow them to prevent users from having their workspaces set to "Public" and also preventing users from setting any repo's to public/fork strategy to public.

The goal is to prevent any user with a managed account to create a public repo against their owned workspace.
As of right now, we do not have a way to prevent users with managed accounts from creating individual workspace and publish any data on there, public or private

I am linking this ticket to the existing ticket logged in BCLOUD:
https://jira.atlassian.com/browse/BCLOUD-20097

Cheers,
Ben