Activate Customer Reduced Manual Access Fulfilment by 70% in Six Months.
Customer Snapshot
Organisation: Mid-sized enterprise
Workforce: 5000 employees
Environment: ServiceNow, hybrid Active Directory and Microsoft Entra ID, and more than 120 applications
Jobs to be done: Keep ServiceNow for requests and approvals while automating provisioning, role changes and deprovisioning across connected systems
Solution: Activate Identity Lifecycle
The Challenge
Our customer used ServiceNow for access requests and approvals. The workflows worked well, but much of the identity fulfilment behind them was still manual. IT teams depended on custom scripts, email hand-offs and a limited set of connectors to provision access across more than 120 applications.
As a result, new employees could wait two to five days for the access they needed. Role changes did not always remove outdated permissions, and deprovisioning was inconsistent across downstream systems. The organisation needed deeper identity automation without replacing the ServiceNow experience its users already knew.
The Jobs the Organisation Needed to Get Done
Give new employees access from day one
Update permissions when people changed roles
Remove outdated access rather than letting it accumulate
Deprovision leavers across connected systems
Reduce manual access fulfilment
Replace fragile hand-offs and scripts with consistent automation
Give audit teams a clear record of identity changes
Keep ServiceNow as the user-facing portal and approval engine
The job was not to replace ServiceNow. It was to automate what happened after a request was approved.
Where the Hidden Costs Were Building
The hidden cost sat between an approved ServiceNow request and the completed access change. Every manual intervention took time. Every email hand-off created another delay. Every custom script needed someone who understood and maintained it.
The effects reached beyond IT. New employees waited before they could work effectively. Old permissions remained after role changes. Leaver access could stay active in downstream systems. Audit teams struggled to trace whether every required change had happened.
Across more than 5,000 users and 120 applications, these gaps created service desk workload, lost productivity and growing identity risk.
The Solution: Add Identity Execution Behind ServiceNow
We introduced Activate as the identity automation engine behind ServiceNow. ServiceNow remained the place where users requested access and approvals were managed. Once an event or approved request was triggered, Activate applied the identity changes across connected systems using policy-driven automation. Activate delivered:
HR-driven joiner, mover and leaver automation
Role-based access control
Provisioning across connected systems
Automated removal of outdated permissions
Real-time deprovisioning cascades
Identity-level audit traceability
This connected ServiceNow workflows with the deeper execution required to complete identity changes consistently.
Giving Each Platform a Clear Job
ServiceNow remained the user-facing portal, and managed requests and approvals
Activate applied identity policies, provisioned and removed access across downstream systems
Identity activity was recorded for audit and review
The organisation kept its ServiceNow investment while removing much of the manual work happening behind it.
The Outcome: Policy-Driven Identity Automation in Six Months
Within six months, the organisation reduced manual access fulfilment by 70%. Day-one readiness increased from 40% to 98%, meaning far more new employees had the access they needed when they started.
Deprovisioning fell from days to minutes. Automated access removal also reduced the number of orphaned accounts to near zero.
Identity-level audit traceability gave the organisation clearer evidence of provisioning and deprovisioning activity across its connected environment.
ServiceNow remained in place, but identity management moved from ticket-driven fulfilment to policy-driven automation.
The Bottom Line
An approved ticket is not the same as completed identity work. The hidden cost appeared in everything that happened after approval: manual intervention, scripts, emails, delayed access and permissions that were not removed.
By adding Activate behind ServiceNow, the organisation automated that execution without changing the front-end experience.
The result was 70% less manual fulfilment, much faster deprovisioning and 98% day-one readiness within six months.
What Happens After Your ServiceNow Request Is Approved?
If provisioning still depends on scripts, emails or manual IT work, Activate can automate the identity changes behind your existing ServiceNow workflows.