Create requests
Depending on how you've set up Access Requests to manage requests, requesters can submit requests using different methods. Requesters can cancel a submitted request using the Access Requests web app if a team member or approver hasn't taken any action on it. They receive a notification about the request cancellation based on the notification preferences that they've set up.
Requests managed by access request conditions
If you set up access request conditions for an app or resource collection, users who meet those conditions can request access to the app or collection directly from the resource catalog of their dashboard. If the conditions include a requester-specified access duration, users indicate how long they need access (up to a limit that you configure).
If you've defined separation of duty (SOD) rules for an app and configured access request settings for the app or resource collection, requester experience may vary based on the access request settings. See Configure settings.
By default, all requests are marked as private so only the requester, request assignee, and users who are assigned a step in the request can see it.
If you're new to Access Requests, use conditions to manage access requests first.
Requests managed by request types
Requesters can use the Okta Access Requests web app, Slack, or Microsoft Teams to submit requests for a resource if you have one or more active request types.
When requesting access from the Okta Access Requests web app, requesters decide which request type to choose to get the access they need.
When requesting access through Slack or Microsoft Teams, Access Requests uses machine learning to parse information from natural-language requests and compare it to historical requests. If a requester sends a message stating, I need a Grammarly account or I need to access Jira, the system tries to identify the request type that best fits the request. If the system doesn't classify a request correctly, the requester can manually adjust the request.
A user can also submit requests on behalf of another user with the Access Requests web app if they're both an audience for a request type. While you can only use the Access Requests web app to submit requests for another user, request creators and requesters can receive notifications about the request in Microsoft Teams and Slack based on their notification settings. The System Log records the user who created the request.
For example, a manager can request access to an app on behalf of a new employee so that the employee has access to all the necessary applications that they need from day one and they don't have to request access to applications after they join the team.
Requesting access on behalf of another user isn't available for admin role access requests.
By default, all users can view requests. You can mark a submitted request as private or you can update your team settings to mark all incoming requests for the team as private. See Create an Access Requests team
Methods to submit requests
The approver experience depends on whether the approver takes action within the Okta Access Requests web app, Slack, or Microsoft Teams. To understand the approval steps in the Okta Access Requests web app, see Manage tasks.