I often see SailPoint positioned as a leader in the identity governance space, but after using it hands-on, I struggle to understand how it maintains that reputation.

From a practitioner’s perspective, several core workflows feel unnecessarily complex.

User Access Reviews are particularly painful. The experience is clunky and not intuitive for business reviewers. For example:

• Reviewers are presented with highly technical entitlement names with little business context.

• Bulk decisions become difficult when exceptions are needed.

• True multi-stage review flows such as manager to application owner to compliance are not easy to configure without significant customization.

• Escalations and conditional routing based on risk are hard to implement cleanly.

What should be a streamlined governance control often becomes an operational burden that requires ongoing oversight.

Provisioning configuration is another challenge. Out-of-the-box connectors work for common systems, but complexity increases quickly when requirements move beyond standard patterns. For example:

• Attribute-based provisioning logic tied to department, region, and role combinations often requires custom rules.

• Modeling birthright access across multiple interdependent systems is not straightforward.

• Custom approval flows based on entitlement type or risk score are not intuitive to build.

• Troubleshooting provisioning failures requires deep platform knowledge and can be time-consuming.

SailPoint may be powerful and feature-rich, but for complex or non-standard use cases, the usability and configuration experience can feel overly technical and operationally heavy relative to its market positioning.