Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1327

Control workspace privacy setting for managed accounts

XMLWordPrintable

    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

              Unassigned Unassigned
              57b7f67f3625 Ben
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: