Zluri is a next-gen Identity Governance and Administration (IGA) platform that enables IT and security teams to discover identities and applications, streamline access management, and automate access reviews—all from a single, intuitive interface. Zluri helps organizations automate critical access controls mandated by SOX, HIPAA, SOC 2, and more—ensuring the right people have the right access to the right applications at the right time, with minimal time and manual effort.
Do You Manage Peer Insights at Zluri?
Access Vendor Portal to update and manage your profile.
What I like most about Zluri is the visibility and organization it gives us. Being able to see all user access in one place has made it much simpler to manage our software ecosystem, optimize licenses, and stay on top of usage. It's also incredibly helpful for off-boarding since we can quickly confirm and remove access across all apps without digging through multiple systems. It really has streamlined our IT workflows.
The customer service and product team is the highlight of the product. They are very responsive to feature requests and to making quick updates based on user feedback.
The onboarding and offboarding features it provides and its integration with our HR application, BambooHR. This provides seamless autonomy between BambooHR and the Azure domain - we are happy to say that the experience allows us to be hands free when changes happen on HR side, we do not worry that the properties will also change on Azure.
Getting a few of the integrations set up has taken more time and back-and-forth than we expected, especially apps with more complex permissions. The initial data cleanup and app inventory process can feel overwhelming if you don't already have things well-documented. Certain dashboards and reports have a slight learning curve and could be a bit more intuitive for new users.
Zluri requires dedicated ongoing administration and management. Also, there are a limited number of API integrations and depending on the availability of integration, provisioning and deprovisioning for different applications will not be uniform. Also, each integration provides different scopes (e.g. you can remove users for some applications but can't make user updates on other applications). This leads to higher maintenance overhead.
Sometimes the automation rules do not work - the expected action of an automation rule does not work as expected despite it being configured the right way.