# Agents approved by your customers' identity providers

18 October 2026. A company you sell to can now let its own identity provider approve the AI agents that act for its people in your app, with no consent screen, and their access ends when it stops approving them or the person leaves.

## Added

- **Authentication:** Enterprise-managed authorization. Turn it on under Agent readiness, and a company you sell to can let its own identity provider approve the AI agents that act for its people: its admin pastes the identity provider's issuer once on the Single sign-on screen in your app (from @buildbase/sdk 1.0.0), copies what to enter into Okta, and an agent it approves then gets a short-lived token for one of the company's people with no consent screen. It is the Identity Assertion JWT Authorization Grant, which Okta calls Cross App Access, and it is built for Okta. An issuer the company's admin saves waits until its first sign-in matches one of the company's people by single sign-on, or your team approves it in the console, and an issuer that signs for everyone at a provider, such as Google's, is refused.
- **Authentication:** How an approved agent's access ends. Its token lasts an hour at most, or less if you or the company choose, and comes with no refresh token, so an agent the identity provider stops approving stops when its token does. Turning the identity provider off or removing it, a policy that no longer allows the agent, and a person deprovisioned, blocked or signed out by the company end its live sessions at once, and your app's revoke URL is told why. An agent's session can never change the company's settings, whoever it acts for.
- **Agents:** Agents that name themselves by a client ID metadata document, as Claude does, connect with no registration once you turn it on under Agent readiness. The consent screen names each one by its document's host and marks it unverified unless you listed that host as vetted, a company's identity provider can approve one only when the company's policy names it, and the clients table's new Metadata document source lists them apart from the clients you created.
- **Webhooks:** Two webhook events and workflow triggers: enterprise.agent_issuer_updated when a company's identity provider for agents is trusted, proven, approved, turned on or off, changed or removed, and enterprise.agent_access when it approves an agent for one of the company's people or your app refuses one, with the reason.

Source: https://www.buildbase.app/changelog/agents-approved-by-company-identity-providers
