Organizations
Manage shared repository ownership, members, teams, defaults, credentials, and billing.
An organization owns repositories and shared operational configuration for a team. Organization administration covers members and roles, repository access, defaults, Actions credentials, billing, bots, and automations.
Inspect an organization
The CLI provides read-oriented organization commands:
try org list
try org view ORG
try org members ORGUse the dashboard for member administration, team access, defaults, billing, bots, and automations. Organization Actions secrets and variables also have CLI commands, described in secrets and variables.
Roles and authority
Organization owners and administrators manage the organization and its repositories. Ordinary members receive only the access supplied by organization policy, team membership, and direct repository grants.
| Actor | Relevant authority |
|---|---|
| Owner or administrator | Manage members, roles, repository defaults, teams, repository access, billing, bots, automations, and Actions credentials |
| Member | Use repositories granted through teams or direct access; invite outside collaborators only when organization policy allows it |
| Outside collaborator | Access only the repositories to which they were invited |
When member invitations for outside collaborators are enabled, a member still cannot grant repository admin access or grant permission above their own level. Repository transfers and other ownership-sensitive actions may require an organization owner even when an administrator can manage the repository.
Teams and repository access
Attach a team to an organization repository to give its members shared access. The current attachment form expects the exact team slug; it does not provide a team picker. Confirm the slug and intended permission before submitting it.
Team access and direct collaborator access are independent. A person can retain access through a team after a direct grant is removed, or through a direct grant after leaving a team. Audit both sources when changing access.
Repository defaults
Organization repository settings define defaults for new repositories, including the default branch and merge or issue behavior. These defaults do not retroactively rewrite existing repositories.
Dashboard creation does not inherit auto-initialization
The organization's Initialize repositories default is not currently applied by the dashboard repository-creation flow. Repositories created there start without an initial commit even when that organization default is on. The default branch and other merge or issue defaults still apply.
Actions secrets and variables
Organization administrators can create and delete shared Actions secrets and variables from the dashboard. Updating an existing value in place and bulk import or export are not currently available there; from that surface, delete and recreate a value when it must change.
Credential access supports:
- all organization repositories; or
- private organization repositories.
Do not choose Selected repositories. The dashboard can display that option, but the platform currently rejects creation with selected-repository access.
Repository credentials override organization credentials with the same name. Organization credential kind also has an important runtime naming caveat; read organization credential limitations before sharing a sensitive value.
Billing, bots, and automations
Billing belongs to the selected personal or organization account. Organization wallet state and included credit are separate from a member's personal account; see billing and wallet.
Owners and administrators can also manage organization bot identities and automations. Treat bot tokens as secrets and follow the credential guidance when minting one.
Organization-wide Actions policies and organization webhooks are shown as coming soon. Do not depend on either as an active organization feature. Use repository Actions settings and repository webhooks where those controls are required today.