Identity Security Cloud

The virtual appliance architecture and implementation because it's scalable and very robust in my opinion, and I have worked closely with SailPoint support to further improve it after encountering issues during our implementation. Provided REST APIs and their supporting documentation. We have leveraged the available APIs to our advantage to further automate processes such as mass role creation in order to make our lives easier during go-lives or testing and validation processes. The documentation for APIs specifically is better than the connector documentation is currently, having examples of API calls in multiple programming languages would be helpful. Identity Insights - this allowed teams to view certain types of auto provisioned access for individuals, departments or job codes. We gained a lot of value out of having this functionality out of the box with SailPoint ISC and we did not have to spend time and resources investing in an aging home-grown tool that would need more updates with the change in identity platform.

the workflows and the ease of use for the people using it

For IIQ: The flexibility of the tool to adjust to specific niche needs and use cases through the development of custom rules, plug-ins, and other extensions or changes, even going so far as to implement custom Java classes to accomplish key requirements, and to do so without breaking supportability from vendor.

There is a lack of insight into some of the major components in ISC relating to tasks such as the 'on the 8's' job and the queues/tasks that appear when identity refreshes or aggregations and other activities occur. There is an absolute need to better document and make these more understandable to customers and configurable where applicable. We were unhappy to have to open a ticket to change the 'one the 8's' job because it was negatively impacting our production tenant during a go-live, this should have been easier to configure or change. The Saas connectors seem to be inconsistent and need work or change in order to meet the functionality of the non-Saas counterparts that use the on-prem VAs to do the work for the connector. This has been an issue we have run into multiple times when trying to implement them, we were excited at the prospect of less reliance on on-prem hardware but issues with things like partitioning not being available for SaaS connectors meant we spent time getting them working or trying to get them working to the level we needed only to fail and have to fall back to the on-prem versions. The connector documentation is honestly my single biggest issue with SailPoint ISC. It's severely lacking in detail and supporting information, often has incorrect or out of date data, and is lacking in helpful screenshots or example data.

right now the only dislikes i have about the product are the in house professionnal services our internal expert knew more on how do do thiings then they did

For IdentityIQ: The UI has a number of areas where it can be improved. The inability to have multiple tabs open is a constant annoyance, and while the UI can be customized in many ways, doing so involves a lot of work to surface critical information, and the overall design of the UI is largely fixed past adding rows or columns. Scalability is very good for the most part, but some critical areas have poor optimization and in areas where it is difficult or impossible to optimize or configure from the client side without major steps being required. A lack of flexibility on the administrative side is frustrating as well - it's challenging to impossible in some scenarios to provide minimum necessary access, and certain areas require full administrative access to see any information at all, forcing workarounds to be created.