Okta Prevents Raising Access Requests for Staged, Deactivated, or Suspended Users
Last Updated:
Okta Classic Engine
Identity Governance
Okta Identity Engine
Overview
Okta prevents raising Access Requests on behalf of users in a Staged, Deactivated, or Suspended status to meet compliance requirements as part of Release v2026.02.3. Okta hides these users during the request process, whereas Okta previously allowed Access Requests for Staged users before the start date.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Identity Governance (OIG)
- Access Requests
Solution
Why does Okta hide Staged users during the Access Request process?
Okta disables the Access Request feature for users in a Staged, Deactivated, or Suspended status to meet compliance requirements. While Okta previously allowed Access Requests for Staged users before the start date, Okta now hides these users during the request process. This represents the expected behavior of the product as part of Release v2026.02.3.
