-
Suggestion
-
Resolution: Unresolved
-
3
-
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
- is related to
-
ACCESS-1683 [Internal] Possible dupes of ACCESS-1468
- Closed
-
ACCESS-1540 Provide Organization Admins with granular control over managed Bitbucket accounts
- Gathering Interest
-
ENT-1461 Loading...
-
ENT-1770 Loading...
[ACCESS-1327] Control workspace privacy setting for managed accounts
Remote Link | Original: This issue links to "ENT-1461 (Jira)" [ 859570 ] | New: This issue links to "ENT-1461 (Hello Jira)" [ 859570 ] |
Remote Link | Original: This issue links to "ENT-1770 (Jira)" [ 859478 ] | New: This issue links to "ENT-1770 (Hello Jira)" [ 859478 ] |
Labels | New: guard-s7 |
Remote Link | New: This issue links to "ENT-1770 (Jira)" [ 859478 ] |
Remote Link | New: This issue links to "ENT-1461 (Jira)" [ 859570 ] |
Link |
New:
This issue is related to |
Support reference count | Original: 2 | New: 3 |
Support reference count | Original: 1 | New: 2 |
Support reference count | New: 1 |
Link | New: This issue is related to BCLOUD-20097 [ BCLOUD-20097 ] |