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.
Every Request Type is made of one or more questions and tasks. Questions prompt users for information either during the creation of the initial request or later in the process. Tasks outline specific actions the system or a 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.
Access Requests can sync applications and groups directly from your Okta organization and perform a range of administrative actions.
Actions involve common tasks like adding or removing users from groups, assigning applications to users, or disabling or suspending accounts. 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 Sync resources from Okta.
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.
Request Types can combine multiple actions to create complex workflows. 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.
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 HR team denies the approval, the request would skip IT approval and automatically close.