LoginSign Up
← Back to all sparks
Z

Zluri

FINANCE
Velocity7.5

Zluri is turning SaaS management into identity governance, and Segregation of Duties is the pivot.

identity governanceaccess reviewssegregation of dutiesworkflow automationsaas management
◆Current state
Zluri now covers discovery, access requests, access reviews and Segregation of Duties enforcement in one product. September releases spread SoD conflict signals into both access requests and certifications, and they gave approvers more control over who decides. The latest release closes a data-trust gap: JDBC, on-prem AD, CSV and SDK sources now show when they last refreshed.
◆Where it's heading
The product is moving from SaaS discovery and spend toward the IGA territory of policy, certification, and remediation. Each release either adds a governance control or makes the underlying identity data more trustworthy. The Workflows v2 canvas, SoD detection and source prioritization all support automated, auditable access decisions.
◆Prediction
SoD and Workflows v2 are likely to move from early access and beta to general availability. Expect deeper links between them, such as SoD violations triggering canvas playbooks directly.

◆Recent moves

  1. 29d ago

    See When Data Was Last Refreshed for More Sources

    JDBC, on-prem AD, CSV Connector and SDK sources now show a last-refreshed timestamp where they used to show N/A. Governance decisions depend on fresh data, so letting admins see staleness for every source supports the reliability work behind SoD and access reviews.

    View source ↗
  2. 1mo ago

    Reassign and Add new approvers in Access Requests

    Approvers can now reassign a pending request, or approve it and add a next-level approver, without asking an admin. This removes a common cause of stalled access requests and moves routing control to the people making the decisions.

    View source ↗
  3. 1mo ago

    SoD Violation Insights in Access Reviews

    SoD conflicts now appear as insight chips during certifications, and exempted conflicts are labelled separately so reviewers don't rule on them twice. The SoD engine now feeds the second major decision point, after access requests.

    View source ↗
  4. 1mo ago

    Workflows v2 - Canvas-based UI

    ⚡ SPARK

    Every playbook type, including onboarding, offboarding, access requests, reviews and SoD, now runs on one node-based canvas with named and nested branches. This is the automation layer that turns Zluri's governance signals into enforced actions.

    View source ↗
  5. 1mo ago

    SoD Violation Insights in Access Requests

    Approvers now get a 'compliance risk detected' signal when granting a request would create an SoD violation. It was the first place the new SoD engine reached the approval workflow, which the access-review integration later followed.

    View source ↗
  6. 1mo ago

    Allow Admins to cancel Access Requests

    Admins can cancel requests directly, and the statuses now separate Cancelled from Withdrawn. This tidies the audit trail, which matters more as Zluri sells into compliance-heavy buyers.

    View source ↗