SailPoint Identity Graph provides a unified view of relationships between identity data in an intuitive graph visualization. Identities, roles, access profiles, and entitlements can all be visualized in the graph, providing a comprehensive view of an identity's access. Allowing you to gain valuable insight into who has access to what, how they have gained that access, and if that access is appropriate.
I was trying to get access to the Identity Graph that was announced in our tenant, and when I searched in the Harbor I just got a snippet of the text here: Identity Graph - SailPoint Identity Services
However, I had to dig further in the Developer Community to find the below announcement that says this is an add-on feature rather than a capability already included in ISC (i.e. we have to pay for an extra license to be able to use it).
Thanks Rachel, first time I see a detailed definition of the multiple offerings based on the different plans contracted with SailPoint and I appreciate the link (bookmarked!).
However, my initial observation is that the document about Identity Graph doesn’t clarify anywhere that this is an add-on and a separate sku needs to be contracted to access this feature.
Also, I got interested in researching about this feature because I got prompted in our own tenant. If this feature isn’t available to us, why that popup was displayed in the first place?
Can you please ask to add a banner or some another notice in the documentation and popups displayed in our tenants the license requirements, so we don’t waste time looking at features that are aren’t available in our core platform?
Hi @eabedrapo1! I understand your frustration. Due to the complexities in licensing contracts, it is not feasible to provide licensing information for each feature in the documentation.
I’ll raise your request for more information about our add-ons to the team that manages that content.
Hi @eabedrapo1! I’ve found where we provide more information about our Adds Ons and Suites. The product documentation covers the entirety of available options, but hopefully this will help identify which apply for your configuration.
I agree with Elisa. This doc currently makes it seem like this is something I should already have access to in my tenant. It’s very unclear that this requires a separate add-on. It should be very doable, even taking into account that there are “complexities in licensing contracts,” to add a “this feature requires an add-on, please talk to your account team for more details.” Otherwise, this documentation gives the incorrect impression that this is functionality that is built into the base product, and we wouldn’t want to give people the wrong impression.
I agree with the others that it would be good to note that a particular feature in the documentation is part of an add-on and they should contact their CSM if they are interested. You don’t need to get into the details of the licensing, as the CSM would handle that, but just making it known that it is not expected to be in their base product.
Something simple like:
This is an add-on and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager.
This would go a long way. What is currently happening is people are reading about this in the documentation, and then asking why they can’t find it in their system. When you have to go find the information on the add-ons and show them it is actually an additional cost, it leaves less-than-positive feelings about it.
@gmilunich and @sup3rmark - While our general policy is to avoid including specifics on licensing in the documentation, we never want to introduce or add any confusion.
I’ve created a ticket to review the Identity Graph documentation and provide more context around accessing the feature. Thank y’all for your continued help in improving the documentation!
Thanks Rachel! Just for context, the reason this came up for me today is that today’s SaaS Release Notes mention an enhancement to the Identity Graph, so as I was reviewing the Release Notes with my team I tried looking into the Identity Graph and noticed I couldn’t access it following the directions listed in the documentation, which led to further investigation.
Thank you for your feedback, @sup3rmark and @gmilunich! I have updated the Identity Graph documentation with a note mentioning the additional licensing. I hope this improves the user experience! Thank you for helping us improve our documentation, and please let us know if you have further feedback.
Thank you for the idea, @gmilunich! The team is looking into the feasibility and best approach for providing more information around add-on features. We’ll update you once we’ve come to a decision.
@gmilunich - Thank you for your patience! The team had to have few discussions on the best route for this.
We do not include licensing information in the product docs, but you can find more information about what is included in the SailPoint Identity Security Cloud Suite levels here. You can also contact your Customer Success Manager to find out which suite level your organization is using or if you have any other concerns.
I see that the note about this being an add-on has been removed. This is disappointing, as the documentation is now (again) misleading, as users looking for this functionality will be confused as to why they can’t find it in their environment.
I understand that from a sales/marketing perspective, it’s bad for prospective customers to see that everything is an add-on sku, but… documentation is not a sales/marketing tool. Please don’t make the documentation worse for the sake of sales.
(Realistically, the real solution here is to stop making every new feature an add-on sku, but that’s a different debate for a different thread.)
