Notifications
Clear all
Topic starter
12/06/2026 12:51 am
TL;DR: IT process automation reduces manual work across SaaS management, onboarding, offboarding, renewals, and access requests, according to Zluri’s analysis of lifecycle workflows and operational bottlenecks. The governance lesson is that automation improves efficiency only when it is paired with clear approval logic, offboarding discipline, and access visibility.
NHIMG editorial — based on content published by Zluri: Lifecycle Management How To Boost IT Teams’ Efficiency with IT Process Automation
By the numbers:
- 91% of former employee tokens remain active after offboarding, leaving organisations vulnerable to potential security breaches.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
Questions worth separating out
Q: How should security teams automate SaaS onboarding and offboarding without losing control?
A: Security teams should automate only the parts of onboarding and offboarding that can be tied to identity source data, app ownership, and auditable approval rules.
Q: Why do manual access requests and renewals create governance risk?
A: Manual requests and renewals create governance risk because they separate entitlement decisions from the records needed to review them later.
Q: What breaks when offboarding is handled app by app?
A: Offboarding breaks when teams revoke access application by application because delays, omissions, and ownership confusion become inevitable.
Practitioner guidance
- Map every repetitive workflow to an identity control owner Assign clear ownership for onboarding, offboarding, app requests, and renewals so each automation path has a named approver and an auditable fallback.
- Automate deprovisioning before you automate convenience workflows Prioritise revocation flows for leavers and dormant accounts before expanding self-service access or renewal shortcuts.
- Tie app requests to policy and licence review Require every access request to carry the business owner, approval rule, and licence review checkpoint so the request cannot become a permanent entitlement by default.
What's in the full article
Zluri's full article covers the operational detail this post intentionally leaves for the source:
- Step-by-step examples of how IT process automation is applied across SaaS workflows.
- Detailed product-oriented descriptions of onboarding, offboarding, and renewal handling in the platform.
- Specific workflow examples for app requisitions, vendor management, and access approvals.
- Operational details on how the dashboard consolidates SaaS insights, usage, and compliance signals.
👉 Read Zluri's article on IT process automation for SaaS lifecycle efficiency →
IT process automation and SaaS governance: what changes for IAM teams?
Explore further
12/06/2026 10:21 am
Manual lifecycle handling is the real failure mode behind SaaS sprawl. The article frames automation as an efficiency win, but the deeper governance issue is that manual onboarding, offboarding, and renewal handling cannot keep pace with SaaS growth. That leaves access, licences, and approvals drifting apart. The practical conclusion is that identity governance must be embedded into workflow design, not bolted on after the fact.
A few things that frame the scale:
- 91% of former employee tokens remain active after offboarding, leaving organisations vulnerable to potential security breaches, according to The 2025 State of NHIs and Secrets in Cybersecurity.
- 62% of all secrets are duplicated and stored in multiple locations, causing unnecessary redundancy and increasing the risk of accidental exposure, according to The 2025 State of NHIs and Secrets in Cybersecurity.
A question worth separating out:
Q: Who is accountable when automation creates a licensing or access error?
A: Accountability stays with the organisation that owns the workflow, not with the automation itself. Teams need clear approvers for provisioning, renewal, and deprovisioning decisions so errors can be traced to a person or role. Governance frameworks expect documented responsibility, especially where access, contracts, and audit evidence intersect.
👉 Read our full editorial: IT process automation reshapes SaaS governance and access reviews
