Okta Identity Governance release notes
Version 2026.08.0. Deployed on August 5, 2026.
Generally Available features
- Certify AI agent resource connections is Generally Available in Preview environments
You can review and certify AI agent resource connections using identity campaigns (formerly, user campaigns). This helps you maintain visibility and control as AI agents' access changes over time. See Create identity campaigns to certify resource connections.
- Governance Analyzer is Generally Available in Production environments
Governance Analyzer provides access certification campaign reviewers with insights and recommendations to make more informed decisions when approving or revoking user access. See Governance analyzer.
- Certify service accounts is Generally Available in Production environments
You can now create resource campaigns to review and certify access for both SaaS application and Okta service accounts. This feature extends your governance strategy to non-human identities, helping you maintain visibility and control over critical service account access. See Certify service accounts.
- Okta Workflows actions for request types is Generally Available in Production environments
Use the Run a workflow action step in a request type to allow requests managed by request types to trigger a delegated flow automatically. The
requestIDof the request is passed to the delegated flow using the Okta Workflows Caller input field. This feature lets you use your existing Workflows connectors and flows in Access Requests to automate requests. See Create request type.- Request subscriptions data export
To export information about users subscribed to access requests, select the Request subscriptions option in the Export Data window. The Requests option no longer includes subscriber data. See Export data from Access Requests.
- Increased maximum for unique groups in the requester scope
You can now specify a maximum of 500 unique groups when you define the requester scope for all conditions in an org. See Access request condition limits.
Fixes
-
When the AI agent connection type was API_SERVER, the connection's configured scopes weren't available in an Identity campaign's review item table. (OKTA-1235938)