Using the Timer Feature in Request Types in Okta Identity Governance
Last Updated:
The Timer feature in Okta Identity Governance (OIG) Access Requests lets a Request Type pause for a set duration or until a specific date, then continue. Use it to manage time-bound access, such as long-term access that ends on a selected date or short-term privileged access that ends after a fixed period.
NOTE: This article applies to the Request Types interface. It does not apply to Resource Centric Access Requests (RCAR/Conditions and Sequences). For a comparison, see Request Types and Resource Centric Access Requests (Conditions and Approval Sequences).
Timer feature overview
In the Request Type builder, select Timer to add a Timer step. The step pauses the Request Type and resumes it when the timer ends.
A Timer step can end in either of two ways:
- End after duration pauses the Request Type for a set number of days, hours, or minutes. Use this for a fixed-duration pause.
- End on date pauses the Request Type until a specific date, based on a previously selected date field. Use this when an end date is provided as part of the request or another Request Type activity.
Some built-in actions also include an Add a time limit option.
Selecting Add a time limit allows choosing End after duration or End on date and adds the timer to the Request Type.
OIG also adds a reversal action for the timed action. For example, if the action is [Okta] Assign individual app, OIG adds [Okta] Remove individual from app. The steps include logic to run only when the preceding steps meet the required conditions.
For example, after a user is assigned to an app, the timer can run for a day. When it ends, the Request Type automatically removes the user’s access.
A start date can also be configured by placing a timer between approval and the Okta action. To set both start and end dates, use two timers: one before the provisioning action and one before the de-provisioning action.
Example 1: Date-based long-term assignment
In this example, a user requests access to a carpark access app and selects the date access should end. After approval, OIG assigns the app and removes access when that date is reached.
Add a date question called Need Until to the request form.
Need Until step using a Date Question
On the Assign to App action, select Add a time limit and set the end date to the date selected by the requester.
Access Request Request Type with Timer and Revoke steps
When submitting the request, the requester selects the date they need access until.
User initiates access request
After the request is approved and the app is assigned, the timer starts.
Timer running in Request Type
When the timer ends, OIG automatically revokes app access. The end date can also be set by someone else, such as a manager, reviewer, another team, or the application owner.
Manager setting the end date for access
Example 2: Fixed-duration short-term assignment
This example uses a fixed time limit for access to Windows DBA accounts. The accounts are tied to the Okta Advanced Server Access AD-Joined feature, which lets the user select the accounts they need to access.
On the Assign step, using the [Okta] Add user to group action, select Add a time limit and set the duration to 2 hours.
Add a time limit to the group assignment
OIG adds a Timer step that waits 2 hours and a Revoke step that removes the user from the DBA access group using [Okta] Remove user from a group.
Timer and Revoke steps in Request Type
After the request is approved and the group assignment completes, the timer starts.
Timer for 2 hours
Hover over the message in the Tasks view to see the expiry time.
After 2 hours, OIG automatically removes the group membership.
Timer done and access revoked
The actions also appear in the Okta System Log.
System Log entries for Request Type actions
