Request Types
Request Types are a customizable no-code approach that defines and automates the entire lifecycle of a request. They consist of actions assigned to users at different stages during the request. Each Request Type is assigned to a specific team and allows organizations to create a comprehensive service library to meet user and organizational needs.
You can't use Request Types to streamline access requests for admin roles. See Govern Okta admin roles and Access Requests for admin roles instead.
Govern Okta admin roles might not be available for you depending on your org's eligibility. Contact your account executive or customer success manager for more information.
Design
Every Request Type is made of one or more steps. A step is an item that you can add to a request type, such as questions, tasks (custom, approval, or action), and timer.
Questions prompt users for information either during the creation of the initial request or later in the process. Tasks are usually out-of-band actions the system or another user must perform.
The complexity of an individual Request Type can vary greatly. A simple usage might automatically add a user to a group, while a more advanced usage might need approvals and justifications from multiple stakeholders.
Integrations
Access Requests can sync resources from your integrations such as Okta, Jira, and ServiceNow.
Use Okta resources like applications, groups, and Okta Workflows to perform a range of administrative actions.
Actions involve common tasks like adding or removing users from groups, assigning applications to users, and running delegated flows automatically. These actions have a direct impact on your Okta organization and are a powerful way to help automate access requests.
Before assigning actions or configuration items to a Request Type, admins must manually enable access to Okta resources for the related team. See Manually sync resources from Okta.
Assignments
Teams can assign Request Types to specific users, Access Requests teams, or use information from Okta to route requests to an Okta group or the requester's manager. This ensures critical requests receive the necessary oversight and allows organizations to simplify decision-making and accountability. This approach ensures that the system routes requests to the correct person.
- To manage task approvals within a Request Type, use groups instead of teams.
- If an automated task doesn't complete, check that the questions and other tasks in the request are complete. Access Requests automatically runs the task after a request assignee enters the missing information. Request assignees can also run a delegated workflow manually by clicking Run manually, or mark the task as done without running the flow by clicking Mark as complete.
Multi-step requests
Combine multiple actions to create complex Request Types. Multi-step requests allow an organization to set a chain of events that must happen before a request completes. For example, a request might need approval from multiple departments. Each approval would need a separate approval action from a different stakeholder. Combining multiple tasks into a single Request Type gives oversight and accountability into how and why a request is approved, as well as simplifying the decision-making process to give the total context of the request.
Conditional logic
Request Types can use conditions to control request routing and actions. This conditional logic is key to creating complex routing paths. For example, a Request Type could require an approval from an HR team before routing a request to an IT team. If the HR team denies the approval, the request would skip IT approval and automatically close.
The Okta Workflows option is only available in the Access Requests console if you have enabled the Okta Workflows actions in Access Requests and Assign admin roles to apps features for your org. Okta Workflows actions in Access Requests is an Early Access Feature. To learn how to enable it, see Enable self-service features. Also, see Before you begin.