Access Management Automation
Simplify and accelerate how you automate access management requests
Install Trend
View Install Data
| Date | Install Count | Change |
|---|---|---|
| 2026-09-09 | 0 | - |
| 134 days of no change | ||
| 2026-04-27 | 99 | -99 |
| 242 days of no change | ||
| 2025-08-27 | 98 | +1 |
| 8 days of no change | ||
| 2025-08-18 | 97 | +1 |
| 11 days of no change | ||
| 2025-08-06 | 96 | +1 |
| 1 days of no change | ||
| 2025-08-04 | 95 | +1 |
| 5 days of no change | ||
| 2025-07-29 | 94 | +1 |
| 74 days of no change | ||
| 2025-05-15 | 93 | +1 |
| 16 days of no change | ||
| 2025-04-28 | 92 | +1 |
| 5 days of no change | ||
| 2025-04-22 | 91 | +1 |
| 12 days of no change | ||
| 2025-04-09 | 90 | +1 |
| 12 days of no change | ||
| 2025-03-27 | 89 | +1 |
| 8 days of no change | ||
| 2025-03-18 | 88 | +1 |
| 5 days of no change | ||
| 2025-03-12 | 87 | +1 |
| 27 days of no change | ||
| 2025-02-12 | 86 | +1 |
| 32 days of no change | ||
| 2025-01-10 | 85 | +1 |
| 71 days of no change | ||
| 2024-10-30 | 81 | +4 |
About
Automate service catalog requests for external application access in minutes with the Access Management Automation application. Choose from catalog items covering common use cases integrating with Microsoft Active Directory, Microsoft Azure Active Directory, and Okta, and quickly move from request to fulfillment.
Each catalog item comes linked to a flow that includes an approval process and automated fulfillment and follows request fulfillment best practices. The flows reassign the task and create an incident or event (or execute a custom subflow) in the case of an automation error. Follow the configuration steps to select approvers and other assignees and get up and running in minutes.
Key Features
This application includes the following catalog items, each with an associated flow for automated request fulfillment.
- Okta
- Create user
- Create group
- Activate user
- Suspend user
- Unsuspend user
- Unlock user
- Add user to groups
- Remove user from groups
- Reset user factors
- Microsoft Active Directory
- Create user
- Create group
- Enable user
- Disable user
- Unlock user
- Add user to groups
- Remove user from groups
- Microsoft Azure Active Directory
- Create user
- Create security group
- Create O365 group
- Delete user
- Enable user
- Disable user
- Add user to groups
- Add owner to group
- Remove user from groups
- Remove owner from group
The application also includes two subflows to choose between when automation fails depending on your company’s processes. One creates an Incident, and the other creates an Event.
Each flow in the application follows a similar pattern:
- Triggered by a service catalog request
- Approval step (choose approvers in setup)
- If approved, creates catalog task, executes automation
- If automation succeeds, closes task and requested item
- If automation fails
- Reassigns task for manual action (choose who/what group to assign to in setup).
- Creates Incident or Event (choose in setup) to address in the case of automation failure.