Organization settings#

Owners and admins manage an organization at /orgs/<handle>/settings. The settings pages are General, Billing, Webhooks, Apps, Integrations and Rulesets.

General settings#

• Avatar: upload a PNG, JPEG, GIF, WebP or AVIF image of up to 1 MiB and 4096 pixels per side, or remove it.
• Organization name: the display name shown instead of the handle.
• Description, parent company, location and website: shown on the organization's profile. The description holds up to 500 characters.
• Default repository permission: what every member gets on the organization's repositories: No access, Read or Write. Teams and individual repositories can grant more.
• Allow forking: whether members may fork the organization's private repositories.

Choose Save to apply your changes. If another admin saved first, reload and apply your change again.

Rulesets#

Organization rulesets apply to every repository the organization owns. Open Rulesets, choose New ruleset or a ruleset's name, and use the same editor as repository rulesets. They appear in each repository's Effective rules with the org scope.

Other settings#

• Billing: see billing and plans.
• Webhooks: see webhooks.
• Apps: install apps and choose their repositories; see apps.
• Integrations: connect Buildkite; see Buildkite.

Close an organization#

Owners can close an organization from General after confirming it's them and typing the organization's handle. Closing archives the organization; past issues and comments keep its name.

An organization can be closed only when it has no repositories (transfer or delete them first; deleted repositories still count) and has never had a paid subscription. The page lists anything that still blocks closure.