Keep your secrets synced across multiple repositories with organization secrets

Centralize secret management at the organization level

Sensitive data like access tokens no longer needs to live only in individual repositories. By creating secrets at the organization level, you can share them across multiple repos, update them in one place, and have those changes propagate automatically. This cuts down on manual duplication and helps prevent workflow failures caused by stale credentials.

Controlling secret visibility

Organization secrets are shared only with the repositories you explicitly select, so you can reduce duplication without over-exposing sensitive information. Alternatively, you can grant access to every repository or to all private repositories in the organization. In either case, any new repository added later will automatically have access to the relevant organization secrets.

Centralized updates and automatic sync

Organization admins have full control over both the secret values and the list of repositories that can use them. When you rotate a secret, the new value syncs automatically to every repository with access—no need to touch each repo's settings individually.

Repository-level secrets have also been improved: repository owners now have the ability to update their values as well.

Automation via the API

Organization secrets are now exposed through the GitHub Actions API, enabling partner integrations to provision and manage these secrets programmatically.

This feature works with any public repository, as well as private repositories belonging to organizations on a GitHub Team, Enterprise, or One plan. For full details, see the documentation on creating and storing encrypted secrets.