---
title: "Update an organization"
method: PATCH
path: "/orgs/{org}"
tags: ["orgs"]
---

# Update an organization

`PATCH /orgs/{org}`

**Parameter Deprecation Notice:** GitHub Enterprise Server will replace and discontinue `members_allowed_repository_creation_type` in favor of more granular permissions. The new input parameters are `members_can_create_public_repositories`, `members_can_create_private_repositories` for all organizations and `members_can_create_internal_repositories` for organizations associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. For more information, see the [blog post](https://developer.github.com/changes/2019-12-03-internal-visibility-changes).

Updates the organization's profile and member privileges.

The authenticated user must be an organization owner to use this endpoint.

OAuth app tokens and personal access tokens (classic) need the `admin:org` or `repo` scope to use this endpoint.

## Path parameters

- `org` string, required

## Request body

- object
  - `billing_email` string — Billing email address. This address is not publicized.
  - `company` string — The company name.
  - `email` string — The publicly visible email address.
  - `twitter_username` string — The Twitter username of the company.
  - `location` string — The location.
  - `name` string — The shorthand name of the company.
  - `description` string — The description of the company.
  - `has_organization_projects` boolean — Whether an organization can use organization projects.
  - `has_repository_projects` boolean — Whether repositories that belong to the organization can use repository projects.
  - `default_repository_permission` 'read' | 'write' | 'admin' | 'none' — Default permission level members have for organization repositories.
  - `members_can_create_repositories` boolean — Whether of non-admin organization members can create repositories. **Note:** A parameter can override this parameter. See `members_allowed_repository_creation_type` in this table for details.
  - `members_can_create_internal_repositories` boolean — Whether organization members can create internal repositories, which are visible to all enterprise members. You can only allow members to create internal repositories if your organization is associated with an enterprise account using GitHub Enterprise Cloud or GitHub Enterprise Server 2.20+. For more information, see "[Restricting repository creation in your organization](https://docs.github.com/enterprise-server@3.8/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)" in the GitHub Help documentation.
  - `members_can_create_private_repositories` boolean — Whether organization members can create private repositories, which are visible to organization members with permission. For more information, see "[Restricting repository creation in your organization](https://docs.github.com/enterprise-server@3.8/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)" in the GitHub Help documentation.
  - `members_can_create_public_repositories` boolean — Whether organization members can create public repositories, which are visible to anyone. For more information, see "[Restricting repository creation in your organization](https://docs.github.com/enterprise-server@3.8/github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization)" in the GitHub Help documentation.
  - `members_allowed_repository_creation_type` 'all' | 'private' | 'none' — Specifies which types of repositories non-admin organization members can create. **Note:** This parameter is deprecated and will be removed in the future. Its return value ignores internal repositories. Using this parameter overrides values set in `members_can_create_repositories`. See the parameter deprecation notice in the operation description for details.
  - `members_can_create_pages` boolean — Whether organization members can create GitHub Pages sites. Existing published sites will not be impacted.
  - `members_can_fork_private_repositories` boolean — Whether organization members can fork private organization repositories.
  - `web_commit_signoff_required` boolean — Whether contributors to organization repositories are required to sign off on commits they make through GitHub's web interface.
  - `blog` string
  - `advanced_security_enabled_for_new_repositories` boolean — Whether GitHub Advanced Security is automatically enabled for new repositories. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see "[Managing security managers in your organization](https://docs.github.com/enterprise-server@3.8/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request.
  - `dependabot_alerts_enabled_for_new_repositories` boolean — Whether Dependabot alerts is automatically enabled for new repositories. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see "[Managing security managers in your organization](https://docs.github.com/enterprise-server@3.8/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request.
  - `dependabot_security_updates_enabled_for_new_repositories` boolean — Whether Dependabot security updates is automatically enabled for new repositories. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see "[Managing security managers in your organization](https://docs.github.com/enterprise-server@3.8/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request.
  - `dependency_graph_enabled_for_new_repositories` boolean — Whether dependency graph is automatically enabled for new repositories. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see "[Managing security managers in your organization](https://docs.github.com/enterprise-server@3.8/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request.
  - `secret_scanning_enabled_for_new_repositories` boolean — Whether secret scanning is automatically enabled for new repositories. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see "[Managing security managers in your organization](https://docs.github.com/enterprise-server@3.8/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request.
  - `secret_scanning_push_protection_enabled_for_new_repositories` boolean — Whether secret scanning push protection is automatically enabled for new repositories. To use this parameter, you must have admin permissions for the repository or be an owner or security manager for the organization that owns the repository. For more information, see "[Managing security managers in your organization](https://docs.github.com/enterprise-server@3.8/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." You can check which security and analysis features are currently enabled by using a `GET /orgs/{org}` request.
  - `secret_scanning_push_protection_custom_link_enabled` boolean — Whether a custom link is shown to contributors who are blocked from pushing a secret by push protection.
  - `secret_scanning_push_protection_custom_link` string — If `secret_scanning_push_protection_custom_link_enabled` is true, the URL that will be displayed to contributors who are blocked from pushing a secret.

## Response `200`

Response

- OrganizationFull — Organization Full
  - `login` string, required
  - `id` integer, required
  - `node_id` string, required
  - `url` string, uri, required
  - `repos_url` string, uri, required
  - `events_url` string, uri, required
  - `hooks_url` string, required
  - `issues_url` string, required
  - `members_url` string, required
  - `public_members_url` string, required
  - `avatar_url` string, required
  - `description` string, nullable, required
  - `name` string
  - `company` string
  - `blog` string, uri
  - `location` string
  - `email` string, email
  - `twitter_username` string, nullable
  - `is_verified` boolean
  - `has_organization_projects` boolean, required
  - `has_repository_projects` boolean, required
  - `public_repos` integer, required
  - `public_gists` integer, required
  - `followers` integer, required
  - `following` integer, required
  - `html_url` string, uri, required
  - `type` string, required
  - `total_private_repos` integer
  - `owned_private_repos` integer
  - `private_gists` integer, nullable
  - `disk_usage` integer, nullable
  - `collaborators` integer, nullable
  - `billing_email` string, email, nullable
  - `plan` object
    - `name` string, required
    - `space` integer, required
    - `private_repos` integer, required
    - `filled_seats` integer
    - `seats` integer
  - `default_repository_permission` string, nullable
  - `members_can_create_repositories` boolean, nullable
  - `two_factor_requirement_enabled` boolean, nullable
  - `members_allowed_repository_creation_type` string
  - `members_can_create_public_repositories` boolean
  - `members_can_create_private_repositories` boolean
  - `members_can_create_internal_repositories` boolean
  - `members_can_create_pages` boolean
  - `members_can_create_public_pages` boolean
  - `members_can_create_private_pages` boolean
  - `members_can_fork_private_repositories` boolean, nullable
  - `web_commit_signoff_required` boolean
  - `advanced_security_enabled_for_new_repositories` boolean — Whether GitHub Advanced Security is enabled for new repositories and repositories transferred to this organization. This field is only visible to organization owners or members of a team with the security manager role.
  - `dependabot_alerts_enabled_for_new_repositories` boolean — Whether GitHub Advanced Security is automatically enabled for new repositories and repositories transferred to this organization. This field is only visible to organization owners or members of a team with the security manager role.
  - `dependabot_security_updates_enabled_for_new_repositories` boolean — Whether dependabot security updates are automatically enabled for new repositories and repositories transferred to this organization. This field is only visible to organization owners or members of a team with the security manager role.
  - `dependency_graph_enabled_for_new_repositories` boolean — Whether dependency graph is automatically enabled for new repositories and repositories transferred to this organization. This field is only visible to organization owners or members of a team with the security manager role.
  - `secret_scanning_enabled_for_new_repositories` boolean — Whether secret scanning is automatically enabled for new repositories and repositories transferred to this organization. This field is only visible to organization owners or members of a team with the security manager role.
  - `secret_scanning_push_protection_enabled_for_new_repositories` boolean — Whether secret scanning push protection is automatically enabled for new repositories and repositories transferred to this organization. This field is only visible to organization owners or members of a team with the security manager role.
  - `secret_scanning_push_protection_custom_link_enabled` boolean — Whether a custom link is shown to contributors who are blocked from pushing a secret by push protection.
  - `secret_scanning_push_protection_custom_link` string, nullable — An optional URL string to display to contributors who are blocked from pushing a secret.
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required

## Other responses

- `409` — Conflict
- `422` — Validation failed

---

[API](https://skmtc.net/github/apis/github-v3-rest-api-7.md) · [All operations](https://skmtc.net/github/apis/github-v3-rest-api-7/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/github/github-v3-rest-api-7/revisions/5438365412fe/schema)