{"id":94487,"date":"2026-03-12T07:53:28","date_gmt":"2026-03-12T14:53:28","guid":{"rendered":"https:\/\/github.blog\/changelog\/2026-03-12-actions-oidc-tokens-now-support-repository-custom-properties"},"modified":"2026-03-12T12:13:45","modified_gmt":"2026-03-12T19:13:45","slug":"actions-oidc-tokens-now-support-repository-custom-properties","status":"publish","type":[3521],"link":"https:\/\/github.blog\/changelog\/2026-03-12-actions-oidc-tokens-now-support-repository-custom-properties","title":{"rendered":"Actions OIDC tokens now support repository custom properties"},"content":{"rendered":"\n

GitHub Actions OpenID Connect (OIDC) tokens now support repository custom properties as claims. Additionally, a new settings page is available in public preview, making it easy to configure OIDC token claims directly from your repository, organization, or enterprise settings while adding properties to the claim.<\/p>\n

Organization and enterprise admins can select custom properties to include in OIDC tokens. Once a property is added to the claim, every repository with that property value set will automatically include it in its OIDC tokens, prefixed with repo_property_<\/code>. You can use these claims to build attribute-based access control (ABAC) policies in Azure, AWS, GCP, and other cloud providers without modifying individual workflows.<\/p>\n

With custom properties in OIDC tokens, you can:<\/p>\n