What needs improvement with Omada Identity Cloud?

It would be nice if we could use queries. It is not possible to customize reports on Omada Identity. Everything is fixed. We can only use the standard options. It would be very nice if we could write queries using the SQL database.

There is room for improvement in Omada's integration capabilities, particularly in streamlining complex integrations and enhancing programming logic for better rule management. The ease of integration may vary depending on the organization's complexity and volume of data.

We have been having trouble with Omada compared to other tools in the market. They can improve its UI and make it more user-friendly. The architecture of the entire system should also be less complex. The way they process the data is complex. I am still trying to understand it. They can add more types of services that we need from the compliance and audit perspective. Their out-of-the-box connectors are not enough. They can add more connectors for integrating with different products. Omada does have a clear roadmap, but things are not delivered as promised.

The UI design needs improvement. One or two years ago, Omada changed its user interface to simplify, but the simplification has not really kicked in. UI design is something that can be improved. We do not use the reporting capabilities of Omada. They can improve it and provide very cool automated reporting for us to use. AI capabilities are another area of improvement, but I know that is already on the roadmap. They want to enrich AI mechanisms into role management and help requesters get to the role they need. That is definitely a thing to improve.

Improved traceability would be helpful for administrators. For example, let's say a user's permission is being revoked. We can only see the system that has carried out a particular action but not what triggered it. If an event definition or something has changed in the criteria for the permission being removed or something like that, we don't have immediate access to that information. It takes a little detective work.

In our organization, all the data is event-driven, which means that if an attribute is changed in the source system, it can be updated within a few seconds in all end-user systems. There is room for improvement in Omada regarding that. Omada is still batch-based for some processes, so sometimes it can take an hour or even four hours before the execution is run and the update is sent. We know that 100% real-time synchronization is not possible. There is always a delay because of system utilization and things like that, but we try to achieve near real-time. If someone is locked out for a reason, we want to find the reason, resolve the issue, and resume the access for that user to enable him or her to log in within a few minutes. With Omada Identity, sometimes, it takes a quarter, and sometimes, it takes more than an hour. It sometimes also takes more than a day before access is given back to their user. There is always a good explanation for that, but that does not bring us as real-time as we want it to be. In the future, Omada should move towards a real-time and event-driven system.

The user interface could be improved. The interface between Omada and the user is mainly text-based. One of the demands that our management had for the new IDM and IGA system was that it should look like the interface of Microsoft products with a nice graphical interface. We struck that requirement from our list as soon as it became apparent that none of the products offered a nice graphic interface. They are all more or less textural. Interface-wise, it can look a little bit smoother, more like the 21st century. It does not have a sharp learning curve. New users of Omada to whom we provide this service find it very easy, which is a plus. On the backend, using Omada and building and programming features have a steep learning curve. You need a very good technical background, but I guess this is how it is. This will not be changed or improved because this is the way the system works. Out-of-the-box connectors were available for the applications that we needed. Only the integration with Microsoft Teams was not ready when we started implementation. We had to build things ourselves for that, so the connection to Microsoft Teams could be improved out of the box. It might have already improved. Our system is already built, so I do not know what has been added to the out-of-the-box functions. I would rate the integration that Omada provides an eight out of ten.

Omada Identity has a steep learning curve. Due to the abundance of features, I have still been relying on Omada University for assistance even after six months of use.

If I had to name one thing, it would be the user interface (UI). They're already working on improvements, but it could be a bit more user-friendly. It's on their roadmap though.

There seem to be many different and complex ways to do things in Omada Identity. I would like to simplify how configuration is done and also have fewer different ways of doing things. The solution should be made more agile for customers to own or configure. Omada Identity needs to invest more in analytics capabilities. Currently, identity and access analytics are add-ons that you do in Power BI on the side. It's not a part of the product, and it's not directly accessible to the customers. I would like to see identity analytics capabilities in Omada Identity.

We are still on Omada on-prem, but I understand that when Omada is in the cloud, you cannot send an attachment via email. We have some emails with attachments for new employees because we have to explain to them how to register and do their multi-factor authentication. All that information is in the attachment. People have to do that before they are in our system. We cannot give them a link to our Intranet and SharePoint because they do not yet have access. They have to register before that, so I need to send the attachments, but this functionality is not there in the cloud. They say it is not possible to add an attachment to the email, but for us, it is very important to be able to do that. I heard from my consultant that they informed Omada about this bug, but Omada said that it was not a bug. That is a bit of a shame. They should look before they say no because if it is a bug, people can work around it with PowerShell or something else. However, it is always better if you do not have to work around it because then you have a layer of PowerShell scripts around Omada to get it working, and I do not think that is how it is meant to be. When there is something wrong, you have to look at the error code book in Omada, which is very difficult to read. You sometimes get an error, but the message in the error does not say anything. It does not help you to know what is wrong. For example, today, I did a survey, but the email was not sent. I do not know why. We did the same in the test environment and then moved it to production. In the test environment, emails were sent, but in production, emails were not sent, and I cannot find out why. There is also no error. It is sometimes difficult to know why things are not working. It should be easier.

The web GUI can be improved.

I would like more training. As someone who is new to this world, I don't feel that the courses Omada provides are good enough. They should also improve the documentation. It is difficult to learn how to use the solution by yourself. In general, the user interface isn't user-friendly or intuitive. In some cases, it's extremely easy to delete critical information. You don't know that you need to select this gray box before you can access a particular object.

When making a process, you should be able to use some coding to do some advanced calculations. The calculations you can currently do are too basic. I would also like some additional script features.

There are some technical bits and pieces that we have looked at that could be better. For instance, when you do a recalculation of an identity, it's hard to understand what was incorrect before you started the recalculation, and which values are actually updated. Right now, all you see are all the new fields that are provisioned, instead of seeing only the fields that are changed. This makes it hard to understand the situation before you started it, compared to after. This is one of the key features that I'm really missing. Also, the onboarding of applications could be easier. There could be workflows to go through the entire process of onboarding a new system or application, instead of having to go to three places to do it. Those are the two key improvements needed. Also, the connectors for the applications that we use are good, but not fantastic. This is constantly improving. Recently, they added a ServiceNow integration, so there are still new connectors coming. But there are a few systems that I would like to see on the list, systems that are not there today. We have two ERP systems: SAP and something called Infor M3, and the latter is not there. It's okay, though. Maybe some of the other companies we evaluated have even more connectors, but Omada was good enough for us.

Omada could communicate better with us about the product roadmap. We haven't gotten any updates about it. The user interface is often a bit difficult to understand. It isn't optimized for small screens, so it doesn't display all of the information clearly, so users need to scroll a lot. The configuration could also be simpler for our admins. For example, it could have some configuration assistance or preset out-of-the-box functionality because it's complicated to enable new features.

I would like to see some additional functionality and improvements in usability.

I would like to see them expand the functionality of the tool to continue to be competitive with the monsters out there. For example, they could add functionality on the authentication side, functionality that Octa and SailPoint have. But they should do that while maintaining the same simplicity that makes Omada a product of choice today.

They need to improve the cost for small companies.