Notifications
Clear all
Topic starter
11/06/2026 11:31 pm
TL;DR: Ticketing, reporting, automation, and self-service differ across ITSM workflows in Zluri’s comparison of Jira and Zendesk, while its alternative-app-request example points to broader access governance concerns for SaaS operations, according to Zluri. The real issue is not help desk choice alone, but how request handling, approval logic, and auditability shape identity control.
NHIMG editorial — based on content published by Zluri: IT Teams Zendesk Vs Jira: Which Is The Better ITSM Tool
Questions worth separating out
Q: How should security teams govern app requests that start in an ITSM tool?
A: Security teams should treat app requests as identity transactions, not as generic help desk tickets.
Q: When does self-service app access create more risk than it reduces?
A: Self-service access becomes risky when the catalog expands faster than policy, ownership, and review.
Q: What do IAM and IGA teams get wrong about ITSM automation?
A: They often assume automation is the same as governance.
Practitioner guidance
- Map ITSM tickets to identity events Identify which request types create access changes, who approves them, and which downstream systems execute them.
- Separate convenience from entitlement approval Review self-service app catalogs to ensure visible apps are policy-approved, ownership is assigned, and high-risk requests still require meaningful review before provisioning.
- Test automation for evidence retention Check whether routing rules, notifications, and bulk actions preserve the approval chain and produce logs that can be tied back to a specific decision and actor.
What's in the full article
Zluri's full article covers the operational detail this post intentionally leaves for the source:
- Side-by-side feature comparison across ticket management, reporting, automation, and knowledge base functionality.
- Workflow examples showing how IT teams route employee app requests and approve access in practice.
- Operational detail on Zluri's employee app store model and how app requests move through IT and procurement.
- Practical guidance on using the platform for approvals, audits, and SaaS request handling.
👉 Read Zluri's comparison of Jira and Zendesk for ITSM and app requests →
Jira vs Zendesk for ITSM: what identity teams should evaluate?
Explore further
12/06/2026 8:12 am
ITSM is now part of the identity control plane, not just the support stack. Once app requests, approvals, and follow-up actions flow through service management tooling, the distinction between help desk operations and access governance collapses. That makes the tool choice relevant to IAM, IGA, and SaaS governance programmes, especially where request fulfilment has real entitlement consequences. Practitioners should treat ITSM workflows as governed identity events, not administrative noise.
A few things that frame the scale:
- 4.6% of all public GitHub repositories contain at least one hardcoded secret, according to State of Secrets Sprawl 2025.
- 15% of commit authors have leaked at least one secret in their contribution history, showing how quickly access exposure can spread across everyday developer workflows.
A question worth separating out:
Q: How do you decide whether Jira or Zendesk is the better fit for access workflows?
A: Choose the platform that best supports your access governance process, not just your ticket volume. If request handling needs role-based routing, approval traceability, and operational evidence for audits, the better fit is the one that can preserve those controls consistently across the request lifecycle.
👉 Read our full editorial: ITSM tools and identity governance: where Jira and Zendesk differ
