# Your customers' CI jobs call your app with no stored key

19 October 2026. A company you sell to can now let its CI jobs and cloud workloads act as one of its service accounts by exchanging the short-lived token their platform already gives them, so no company API key sits in CI.

## Added

- **Authentication:** Workload identity for company service accounts. Turn it on in the console on the WorkOS provider card, and a company's admin who manages its API keys can add a workload credential under one of its service accounts: GitHub Actions, GitLab, Google Cloud, AWS, Microsoft Entra or another OpenID Connect issuer, pinned to its repository, project or account by number and to a branch or environment. The job sends its own token to POST /api/v1/company/token and gets a company API token of at most an hour with the credential's scopes, and no refresh token. The card shows the step to put in the workflow, when the credential was last used and why it was last refused. Your team can add one from the enterprise in the console, and the company sets it up in your app from @buildbase/sdk 1.0.0, which also brings a helper for the exchange.
- **Authentication:** How a workload's access ends. Turning a credential off or deleting it, deleting its service account, or turning workload identity off ends its live tokens at once; narrowing a credential leaves live tokens their scopes until they expire, unless the company ends them now. Every token issued is in the company's trail with the run that got it, and every change it makes names it.
- **Webhooks:** Two webhook events and workflow triggers: enterprise.workload_credential_updated when a company adds, changes, turns on or off, or removes a workload credential, with the live tokens it ended, and enterprise.workload_access when a workload exchanges its token or is refused, with the reason.

## Fixed

- **Authentication:** A change in behaviour: in your app, a key made for a company's service account now carries only the scopes the admin making it reaches through their own company roles, as their own key and a workload credential already do. A scope beyond their roles is refused, naming it. Keys already made keep their scopes, and your team in the console may still give any scope.

Source: https://www.buildbase.app/changelog/workload-identity-for-company-service-accounts
