ワークスペースへの参加、またはワークスペースの作成 | Bitbucket Cloud

To join or create a workspace, you need an individual Bitbucket account. Once you have created your Bitbucket Cloud account, you can join an existing workspace by accepting the invite sent to your email inbox or contact your Bitbucket Cloud administrator to get access.Whoever creates the workspace automatically has administrative access. That user can also specify admin access for other members of the workspace, giving them the ability to administer the team. Any admin can update the workspace's plan and credit card details.Create a workspaceBitbucket Cloud is now in Atlassian Administration, which means you can manage your Bitbucket users and groups within the same organization where your Jira site and Confluence space are administrated. The information below can also be accessed at Add a new Atlassian app or collection to your organization | Atlassian Support.Add Bitbucket Cloud to your organization and create a workspace in your organization in Atlassian AdministrationIf you already have Atlassian apps and/or an organization in Atlassian Administration, you can now create a Bitbucket Cloud workspace in your organization.Go to the following URL: admin.atlassian.comLog-in to your Atlassian Administration account.Select Atlassian apps in the left navigation.Select the Add app button.Select Bitbucket from the list of apps.Name your workspace. Workspace ID is auto-created in accordance with your workspace name.Select the Agree and add button to create your workspace in Atlassian Administration and agree to the Atlassian Cloud Terms of Service and Privacy Policy.You should now have a workspace in Bitbucket Cloud for your organization within Atlassian Administration.Workspace creation may be restricted If your organization has set restrictions on workspace creation, you will have to request access to the workspace you created and an administrator within your organization will have to grant you access to that workspace. If access is granted by the org admin, you will receive a notification email where you can accept the invite to your new workspace.Access your new workspace in Atlassian AdministrationLog-in your Bitbucket Cloud account.Select the Settings cog on the top navigation bar.Select User management under the Atlassian Admin heading in the Settings dropdown. This lands you on the Users page in your workspace in Atlassian Administration.For more information on administering your users and groups in Atlassian Administration, check out our collection of help documentation: Manage your organization’s users.Wikis and Issue tracker are not available in workspaces administered in Atlassian AdministrationWiki and Issue Tracker features are not supported in workspaces administered through admin.atlassian.com. These features will be disabled if you create or following a transfer to a workspace administered through admin.atlassian.com. If you have already transferred the repository, you can transfer it back to the original workspace to regain access to the wiki and issues. Wikis can be exported via cloning since they are stored as a separate repository. Issues can be exported as a zip file or migrated to Jira.For information on how to add members or groups to your workspace or to grant access to existing repositories in your workspace, refer to Grant access to a workspace. Update your Workspace settingsYou can update your Workspace settings only if you have administrative permissions. If you think you should have admin permissions, ask another administrator to grant you access. If you have admin permission, find your Workspace settings with the following steps:From your profile avatar, select the workspace or All workspaces for a full list.Select the Settings cog on the top navigation bar.Select Workspace settings from the Settings dropdown menu.The Workspace settings page opens by default.Navigate between multiple workspacesBitbucket Cloud is scoped to provide you (a member of the workspace) all the content you have permission to access within a single workspace. If you work in or are a member of more than one workspace, you can switch between workspaces.Select Your profile avatar in the upper-right corner of the top navigation bar.Select a workspace from the Recent workspaces list, or select All workspaces to display a list of all the workspaces in which you are a member and select the appropriate workspace from the list.Workspace privacy settingsSelect either Public or Private depending on how your organization or team wants to maintain the privacy of your code and content in your workspace.Public: This means that the workspace URL is visible to and can be accessed by anyone.Private: This means that the workspace URL can only be accessed by workspace members, but may still contain public content, meaning there could be a project or repository in the workspace that contains public code or other content.Workspace privacy enforcementPREMIUM FEATUREPrivacy enforcement for your workspace is a Bitbucket Cloud Premium feature with the following security benefits:Requires all projects and repositories to be private which means no public content can exist in the workspaceEnsures your organization’s Bitbucket content is secure and privateLearn more about Bitbucket PremiumIf you have a Premium plan, you can enable the Do not allow public content inside this workspace setting to require all content in the workspace to be private.Select the checkbox associated with the Do not allow public content inside this workspace setting.If there is public content in the workspace, the This workspace contains public content dialog will be displayed.Select the Manage public content button to open a list of projects containing public content in the workspace.Make any public content in the projects private. This could mean making repositories within the projects private as well as setting the project to private. You can also remove any public content, if that is necessary or fits better into your organization’s policies or workflows around privacy.For more information on setting repository privacy, refer to Set repository privacy and forking options.For more information on setting privacy for your issue tracker, refer to Make the tracker private or public.For more information on setting privacy for a wiki, refer to Make a wiki private or public.To query any public Bitbucket issues or wikis, use the following API call: https://api.bitbucket.org/2.0/repositories/{workspace_slug} ?fields= +values.wiki_private, +values.issues_private &q= (has_issues=true AND issues_private=false) OR (has_wiki=true AND wiki_private=false)For more information on the encoding of ‘+’ in the provided API call and any other field parameters associated with this, refer to the field parameters syntax section of our developer documentation.For more detailed information on this API call, refer to our REST APIs developer documentation. If you would like to review or clean up any public content prior to enabling the Do not allow public content inside this workspace setting, you can select the ‘# of publicly visible projects’ link in the Private setting’s description.Repository forking policyAs a workspace administrator, you can prevent the forking of repositories outside of the private workspace.Prevent forking outside the workspaceSelect the checkbox associated with the Do not allow forking of private repositories to other workspaces repository forking setting.Select the Update workspace button to update your workspace settings.If enabled, forking to other workspaces is not allowed on private and public repositories. If disabled, forking to other workspaces is allowed on public and private repositories. Forking within the workspace is allowed depending on what forking policy is enabled in the repository's settings. Signed system commitsA workspace administrator can enable signed system commits at the workspace level, Bitbucket Cloud will use a system public GPG to automatically sign the commits that it creates. This includes pull request merge commits, commits made by editing files in the browser, and accepted code suggestions in comments.Bitbucket-signed commits will have a verified status. Using Bitbucket-signed commits will prevent failures and errors when you’re checking commits for signatures, having all signed commits merged into subsequent pull requests, or verifying commit signatures through your local Git installation. So you can be sure that you comply even with the strictest security and compliance standards.Enable signed system commitsYou must be a workspace admin to enable and disable signed system commits.Select the Settings cog on the top navigation bar.Select Workspace settings from the Settings dropdown menu.The Workspace settings page opens by default.Select the Automatically sign commits made through Bitbucket checkbox.Download the system GPG keyYou can use the system public GPG key to do local verification of commits signed by Bitbucket.The GPG key is available to download at:https://api.bitbucket.org/2.0/workspaces/{workspace}/settings/gpg/public-key/Disable signed system commitsTo disable signed system commits, uncheck the Automatically sign commits made through Bitbucket checkbox.