Use SCIM provisioning when available. Custom workflows are for resources without SCIM support where you want to avoid manual provisioning.
When to Use Custom Provisioning
- The resource doesn’t support SCIM
- You have API or CLI access to the resource
- Manual provisioning would otherwise be required
How It Works
Custom provisioning requires two workflows:- Provisioning workflow: Grants access
- Deprovisioning workflow: Revokes access
Create a Provisioning Workflow
1
Open the role
In Access Manager, open the role you want to configure
2
Start a new workflow
Next to “Choose a provisioning workflow,” click +
3
Enter provisioning steps
In the workflow builder, enter your steps below the template line:
4
Write instructions
Write the provisioning steps in natural language
5
Test the workflow
Click Test workflow to verify the logic
6
Publish
Click Publish when ready

Custom provisioning workflow builder
Create a Deprovisioning Workflow
1
Return to the role
In Access Manager, open the same role
2
Start deprovisioning workflow
Next to “Choose a deprovisioning workflow,” click +
3
Enter deprovisioning steps
Enter your steps below the template line:
4
Write instructions
Write the deprovisioning steps in natural language
5
Test and publish
Test and publish the workflow
Link Workflows to the Role
1
Select the role
In Access Manager, select the role
2
Link provisioning workflow
Under “Custom workflow,” select your published provisioning workflow
3
Link deprovisioning workflow
Under “Deprovisioning workflow,” select your published deprovisioning workflow
Custom provisioning workflows execute only through access requests managed by the access policy. They cannot be triggered manually.

Workflows marked with key icons
Verify the Configuration
Test the complete flow:- Submit an access request for the role
- Verify the provisioning workflow executes correctly
- Wait for the access period to expire or manually revoke access
- Verify the deprovisioning workflow executes correctly

