Managing organization settings

You can verify your ownership of domains with GitHub to confirm your organization's identity.

If your project or company has changed names, you can update the name of your organization to match.

To make someone else the owner of an organization account, you must add a new owner, ensure that the billing information is updated, and then remove yourself from the account.

To protect your organization's data, you can configure permissions for creating repositories in your organization.

You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.

To protect your organization's data, you can configure permissions for changing repository visibility in your organization.

You can allow or prevent the forking of any private repositories owned by your organization.

You can limit which users can approve or request changes to a pull requests in your organization.

You can enable, disable, and limit GitHub Actions for an organization.

You can manage private networking for GitHub-hosted products using network configurations in your organization.

You can create a private network configuration for your organization to use GitHub-hosted runners in your Azure Virtual Network(s) (VNET).

Learn how to use GitHub-hosted runners with an Azure private network in your organization.

Learn how to fix common issues while creating Azure private network configurations to use GitHub-hosted runners with an Azure VNET.

You can configure the retention period for GitHub Actions artifacts and logs in your organization.

Organization owners can allow certain people to delete issues in repositories owned by your organization.

You can use GitHub Discussions in an organization as a place for your organization to have conversations that aren't specific to a single repository within your organization.

You can choose the permission levels that members require to create discussions in repositories owned by your organization.

You can require users to automatically sign off all commits they make in GitHub's web interface to repositories owned by your organization.

You can allow all organization members to create teams or limit team creation to organization owners.

You can get reminders in Slack for all pull requests that teams in your organization have been requested to review.

You can set the default branch name for repositories that members create in your organization on GitHub.

You can customize the labels that are included in every new repository in your organization.

You can allow members of your organization to see a comment author's profile name in private repositories in the organization.

You can manage the email address that receives updates from accounts your organization sponsors.

You can control whether organization members can publish GitHub Pages sites from repositories in the organization.

You can archive an organization to make it read-only and indicate that it's no longer actively maintained. You can also unarchive organizations that have been archived.

You can delete your organization account at any time.

It's not possible to convert an organization into a personal account, but you can create a new personal account and transfer the organization's repositories to it.

Organizations can upgrade from the Standard Terms of Service to the GitHub Customer Agreement.

Organization owners can turn off organization-wide projects, organization-wide projects (classic), and repository-level projects (classic) in an organization.

Organization owners can turn off insights for Projects in their organization.

Organization owners can configure a base permission for projects created in their organization.

Organization owners can allow members with admin permissions to adjust the visibility of projects in their organization.

With custom properties, you can add metadata to repositories in your organization. You can use those properties to target repositories with rulesets.