Preparing for Okta Unified Requester Experience (URE) Changes in Access Requests

Okta Unified Requester Experience (URE) general availability changes the requester experience for customers using Request Types and the request experience in Microsoft Teams. These changes require action before general availability (GA) in production to avoid unintended request visibility and end-user confusion. The Unified Requester Experience is currently available in all cells in Self-Service EA. We recommend customers test out this feature now in advance of the upcoming GA release. (See Enable self-service features.)

• Okta Identity Engine (OIE)
• Okta Identity Governance
• Unified Requester Experience (URE)
• Access Requests
• Request Types
• End-User Dashboard
• Microsoft Teams
• Slack

Why do Request Type audiences require review before general availability?

Request Types now appear in the unified End-User Dashboard (EUD) catalog. Users no longer need to be assigned to the Okta Access Request application to raise requests. A user not assigned to the Okta Access Request application can still browse the unified EUD resource catalog and will be JIT provisioned to the Okta Access Request application at the time that he or she raises a request. As a result, the audience field on each Request Type now solely controls who can request it, instead of the previous combination of the audience field and assignment to the Okta Access Requests app.

Request Type audiences require review and may require updates before general availability to ensure that request types that have broadly scoped audiences do not become requestable by all org users unintentionally. Request Types will be visible to all users in the requester audience for that Request Type, independently of whether or not a user is assigned to the Okta Access Requests app. That visibility, if unintended, may incorrectly expose request paths to users outside the intended requester audience.

The Request Access button now supports configurable visibility.

The Request Access button in the EUD can now be scoped by Okta group. This can be used if you want only a certain population of users to see the entrypoint to the unified resource catalog in the EUD.  Configuration options allow visibility for all users, specific Okta groups, or no one. 

This change requires administrator awareness and possible action so the EUD matches the intended end-user experience.

How does the Microsoft Teams request submission change affect request flows?

The ability to submit requests end-to-end from Microsoft Teams is replaced by a request initiation flow at general availability. Users can still initiate a request search and (new) browse matching catalog entries in Microsoft Teams. However, final request submission happens in the Okta web interface. There is no change to the post request submission experience on Microsoft Teams.  

Customers that currently submit requests end-to-end through Microsoft Teams should update internal processes and notify end users before general availability production.

What changes arrive in the current early access release? 

The current early access release adds the following capabilities:

• Users can submit both Request Type and Request Condition requests from the Okta EUD Resource Catalog.

• Users can submit both Request Type and Request Condition requests from Slack.

• Admins can configure whether users are allowed to submit requests and/or approve requests from Slack. 

• Users can search the research catalog and initiate both Request Type and Request Condition requests from Microsoft Teams.

We recommend customers test out this early access feature now in advance of the upcoming GA release. (See Enable self-service features.)

The general availability release adds additional request experience changes.

The general availability release adds the following change:

• Admins can configure who sees the Request Access button in the EUD.

Why are these customer groups affected by the change event?

The following groups are affected for different reasons:

• Request Type customers that use Microsoft Teams are affected because Microsoft Teams end-to-end submission is out of scope for this general availability release, while search and request entry remain supported.

• Request Type customers are affected because Request Types now appear in the unified EUD catalog and requesters no longer need to be assigned to the Okta Access Request application to raise requests. As a result, the Request Type audience field now fully controls end user visibility of that request type.

• All Access Requests customers are affected because the visibility of the Request Access button in the EUD is now configurable.

When is the change event?

The rollout is phased over approximately 4 months

Teams request submission replacement takes effect at the 11.0 GA Prod release (November 9, 2026). Dates are subject to change; confidence is moderate.