Organization settings#

/orgs/<handle>/settings/general is available to owners and admins; the bare /settings path lands there. Other members see an access-denied page when opening a Settings URL directly; settings controls are not shown. The settings navigation includes General, Billing, Rulesets and Integrations.

General#

• Avatar: upload a PNG, JPEG, GIF, WebP, or AVIF image up to 1 MiB, or remove the current one. The organization page, the header breadcrumb, and the user menu show it.
• Organization name: the display name shown instead of the handle. It cannot be blank.
• Description, parent company, location, website: the public profile prose rendered at the top of the organization page. The description is capped at 500 characters and the website must be a full http or https URL. Clearing a field removes it.
• Default repository permission: the baseline every member gets on the organization's repositories: No access, Read, or Write. Members can still be granted more on individual repositories.
• Allow forking: whether members may fork the organization's private repositories.

Press Save after making your changes. If another admin saved first, your change is rejected; reload to see their values before retrying. An untouched form picks up background changes on its own.

See billing and Buildkite integrations for those settings and their configuration requirements.

Close organization#

Only an owner with a recently confirmed human session can close an organization. Personal namespaces are closed only through Settings → Account. Type the organization handle exactly to confirm.

Closure is blocked while the organization has a live repository, pending repository admission/import/transfer/native work, or retained repository storage. Deleted repository tombstones remain blocking because the native layer does not support deletion or an absence validator. Failed or uncertain native admissions also remain blocked. Any Stripe customer or subscription row blocks closure, even when the subscription is canceled, because a late checkout can still attach provider custody. There is currently no safe self-service cleanup for those retained records. Closure never changes provider billing. Remove or transfer repositories through their normal settings. Closing archives the organization and tombstones its actor while retaining historical content and audit identity; it does not delete native Git storage or start a remote cleanup workflow. A validated closure event is stored atomically; instance administrators can inspect an exact receipt through the operator API.

Rulesets#

/orgs/<handle>/settings/rulesets lists the organization's branch and tag protection rulesets; New ruleset and each row's name open the editor at /orgs/<handle>/settings/rulesets/<id> (or /new). The editor is the same one repositories use, described as organization-wide.

An organization ruleset applies to every repository the organization owns and shows up in each repository's Effective rules with the org scope. If the organization or ruleset changes while you edit, your save is rejected and the list refreshes. Changing protection can also reject a push already in progress; review the new rules before retrying the push.