Omada Identity Reviews

My use case for Omada Identity is that it's an identity and governance administration tool, and we use this for IGA as our IGA tool in the company.

What I appreciate about Omada Identity solution is that it covers most of the concepts of IGA, and the request access UI is getting better. Omada Identity has helped us consolidate solutions for access management as they provide access request concepts, access reviews, and different types of access reviews that can be used. Both important parts of any IGA solution, requesting access and reviewing access, are provided by Omada Identity.

The areas that have room for improvement in Omada Identity are the UI, the reporting as they don't have any kind of reporting currently available, and the notifications. These three are the main areas where they need to improve.

I have been using Omada Identity for more than two years.

I would rate the stability as having no downtime, but there are many bugs which we report, and we are informed that they are not going to improve those bugs, although they apologize for them.

We did not have a requirement to scale, but I have been told that it's easier to scale, so I would rate it as eight.

I would rate the support of Omada Identity as a six out of ten.

We were using Saviynt previously, and the support was not very good with Saviynt, which is why we had to move. The cost was also a factor in why we moved to Omada Identity.

We have Omada Identity set up to remove an employee as soon as they leave the organization. This does not affect our security, as that is the standard procedure we have always had where, whenever a user is terminated from the company, their access gets disabled or revoked after a few days, which is also what we implemented in Omada Identity.

Omada Identity has definitely helped us save time when provisioning access for various identities, though I cannot recall the numbers right now. It's not better than what we had with our earlier IGA solution, as we moved from the previous tool to Omada Identity, so there was not much difference from that perspective.

In comparing Omada Identity with my previous vendor, I mention the support, but overall, it is not better. I have worked on different tools such as SailPoint in my previous organization, and this company had Saviynt, making it clear that Omada Identity is definitely not better than both Saviynt or SailPoint, so we are struggling and having issues with everything.

Omada Identity is deployed on cloud, specifically Azure. Around 4,500 users work with Omada Identity. From an infrastructure perspective, the solution does not require any maintenance. The updates and releases for Omada Identity are easy to perform.

Omada Identity has helped automate reviews of access requests and reroute them to appropriate people, but they have a standard workflow that we use. They lack in notifications, as the emails sent to the reviewers do not have sufficient information about what the review is for, nor do they have a way to communicate via Slack or Teams.

I use Omada Identity certification surveys to recertify roles or determine them with managerial surveys done quarterly. We use Omada Identity to run managerial surveys, access owner surveys, and transfer of ownership surveys.

Regarding connectivity, Omada Identity has good packages which allow us to connect to almost any application, and I would rate it as nine out of ten. The out-of-the-box connectors provided by Omada Identity are good enough to connect to any applications we want.

If Omada Identity is cost efficient and an organization has a lower number of employees who use birthright policies instead of access requests, I would recommend it. However, if they rely heavily on access requests and approvals, I would not recommend it, as the UI and reporting are not that great. If someone is looking for extensive reporting for audit purposes, I wouldn't recommend this product.

I would rate Omada Identity overall as seven out of ten.

We utilize self-service access request workflows. We faced a compliance issue when an employee from the Poland team ran a script that deactivated almost 400 accounts. Sometimes there will be a flaw. He ran the script and 400 users were automatically terminated. In our organization, we have a status in Omada Identity that defines users as active, inactive, or terminated. After this incident, many employees reported that they were not able to log into the system, mail, or access the internet. When we checked the identity status of the user, it was actually terminated. We initially thought HR had terminated these accounts for some reason, but that was not the case. The colleague from the Poland team ran a script that was not correct and removed everything. The development team of Omada Identity took care of everything and reactivated the users, resolving the issue.

I assess the integration capabilities of Omada Identity with existing IT infrastructures positively. Most of our self-service requests are automated. If someone needs something and they raise it from the ITSSP self-service portal, it goes through automation and is done within 15 minutes, with the ticket closed automatically. We have a ticketing tool called BMC Remedy, and we raise the ticket from there, which is connected to Omada Identity. If a user needs something, the automation goes to Omada Identity and gives the resources or facilitates changes in job title, functional area, or location. After HR approval, it automatically changes.

Everything is connected, and I evaluate the integration capabilities of Omada Identity with third-party tools and existing infrastructures positively. We use SAP, which is our first point of contact and integrated with Omada Identity, while Omada Identity is connected to Active Directory. Although this is primarily managed by the development team, we have a mini master in the SAP system containing details of employees. Once saved, the details sync with Omada Identity. When searching for an employee ID or name, we get all results including their email, first name, last name, SAP ID, and functional unit, and then it goes to Active Directory. These tools are linked very well.

The risk-based approach of Omada Identity helps our organization manage potential security threats as Omada Identity is safe. It operates only on our intranet if configured perfectly. You cannot access Omada Identity's page from your computer unless you are connected to our company's VPN. If connected to an external network, you cannot access Omada Identity. The security is robust, and we have not faced any major threats such as phishing emails. We have a cybersecurity team that handles potential issues, but to my knowledge, Omada Identity is safe.

The overall positive impacts and benefits I have seen since the deployment of Omada Identity are significant. The tool is impressive as every single detail of the user is actually available on Omada Identity. There is nothing else apart from Omada Identity where you can check the details in another application. This is a single application where you get everything about the employee, including their manager, identity owner, and every detail needed. Omada Identity is actually useful.

The features of Omada Identity that I have found most valuable and useful are how it works when an employee joins an organization. When a new employee comes, HR handles everything and the details are uploaded in the PHE system of SAP. We basically use SAP for the starting stage. From SAP, all the details are pushed to Omada Identity. Everything such as organization, entity, job role, and the joining date are included. It even notes if the employee is a contractor, when their contract will end, and what resources they need, such as a Windows user, email, and internet connection. Everything is provided by Omada Identity itself. If it is an automation, for instance, if a manager wants internet access for the employee, the manager raises a request and gets the access. Unless internet access is given in Omada Identity, the user cannot access the internet on their system. That is the actual scenario of Omada Identity, and we handle the Active Directories from Omada Identity, so from the PHE system of SAP to Omada Identity and then from Omada Identity to Active Directory. This is the process, and this is the workflow we use in our organization.

Regarding the compliance reporting features of Omada Identity, when we check resources for some employees, we first contact Omada Identity if the resource is available for the user, such as internet access. If the resource is available and the user cannot access it, then there is some issue with the network. If the resource is not available, it is actually with the particular internet access. We provide the internet access, and it activates immediately as soon as we give the access to the user, allowing them to access within minutes. There is no wait time. For the system, we need a Windows user, which is the Active Directory group in the Omada Identity resource. We add that resource, and then users will be able to log into the system. Unless they have a Windows user, they cannot log in. The process is very quick. Once activated, the resource is immediately available through Active Directory.

Regarding areas of Omada Identity that could be improved or enhanced, I do not have much idea. As of now, the tool is good, and I haven't seen any bugs or errors. I consider it perfect as of now.

I have been using Omada Identity for approximately 2.5 years for identity purposes.

Omada Identity is a stable and reliable tool. I have not seen many errors, and it performs well. It is a good tool and I can confidently say that.

Omada Identity is scalable as it is used by many organizations. I have worked in different organizations, and it is available in most places. Omada Identity is a top-growing tool that is booming in the market, and based on my experience, it is good and will scale up for future needs. Most organizations will likely adopt Omada Identity.

I often communicate with the technical support of Omada Identity regarding maintenance. There is maintenance every two to three months, usually over the weekend, which results in a temporary outage of Omada Identity. However, maintenance is necessary, and aside from that, if there are issues with Salesforce cloud, then Omada Identity may go down.

I communicate directly with Omada Identity vendor as we are the technical support for Omada Identity.

Positive

Before using Omada Identity, I actually used Okta. I decided to switch from Okta to Omada Identity because everyone wants to explore new tools and technology. Omada Identity is a new technology for me that I can learn and improve my skills with, which also adds value to my resume. It opens up job opportunities for me. I appreciate what I have learned and I am currently working with Omada Identity. We do not only work with Omada Identity; we also have multiple tools such as BMC Remedy, but they serve different purposes and are not for identity access management.

I participated in the initial setup of Omada Identity through training. When I joined the company, I was trained on how it works.

I did not face any challenges in the initial setup process. This is just a tool; nothing more about the configuration because it is already configured by the development team. Any changes they need will get reflected to us. There is no initial configuration such as something else, although there is a challenge to learn the configuration because the data is pulled from SAP to Omada Identity. I do not know the exact process of that, but it is managed by the development team.

Regarding the pricing of Omada Identity, this is not taken care of by me. The price and everything is managed by the organization, particularly by my IT director. Therefore, I am not aware of the exact cost of Omada Identity.

Omada Identity is deployed on the cloud in our organization. We use Salesforce as our cloud provider.

I evaluate the speed of Omada Identity as generally good. From the start, I have been using Omada Identity, and I have not seen any flaws. Occasionally, the tool is slow, but every three to six months they release a patch update and perform maintenance. If there are any bugs or errors, they resolve them during that time. Therefore, everything is good as of now. I do not see any implementation required at this moment.

I do not use any documentation, manuals, or guides for Omada Identity available on the internet. That is managed by the development team. If they identify any errors or if the tool lacks requirements, that responsibility is taken care of by them.

Overall, I would rate Omada Identity as an eight out of ten as it varies by organization. The tool will differ in every organization based on how the developers create it to meet company requirements.

Public Cloud

Other

My main use case for Omada Identity is user provisioning, specifically automatic user provisioning, where Omada Identity acts as the workforce authority to create, delete, or change AD accounts, email addresses, and AD group memberships based on HR system changes.

In my day-to-day work, a recent scenario where Omada Identity handled a change for us involves monitoring the environment to ensure that the connections between HR systems and Active Directory systems or Exchange systems work as expected, while starting to integrate Omada Identity with our SAP environment to provide access based on user roles.

The best feature that Omada Identity offers is the user provisioning, which enhances security by ensuring that users have the access they need while removing access promptly when someone leaves the company.

The provisioning feature of Omada Identity stands out for me because, after several years of lacking a proper connector to our HR system, Omada Identity finally released a good connector, allowing us to utilize everything out of the box, which has made our life much easier.

Omada Identity has positively impacted my organization by automating the identity and access management aspects, which was a game changer since manual processes previously took two to four days and now allows us to streamline our operations while increasing security.

The outcomes from using Omada Identity include an impressive reduction of errors because automation replaces human input. Now the onboarding experience for new hires is efficient, with everything set up the day before they start.

Omada Identity could improve by addressing the technical knowledge required for managing the tool, as it can be hard to find professionals who are skilled in using and supporting it.

Currently, the documentation for Omada Identity is sufficient, with a portal for ideas, a good command center, and available training, so I feel well-supported.

I have been using Omada Identity for five to six years.

In terms of scalability, Omada Identity meets our needs well. We do not have a large demand for scalability since we focus on user provisioning and access provision in our on-premises environment.

The customer support for Omada Identity is good, though not great. Sometimes it has not been very fast, and at times they rely on external partners, causing delays, but they are improving and so are we with our internal knowledge.

Prior to Omada Identity, we used Microsoft PIM, also known as Forefront Identity Manager, but we switched because we realized that Omada Identity would provide a great upgrade for us.

Before choosing Omada Identity, we evaluated Octane savings, which were good, but the primary factor for our decision was the cost.

My advice for others looking into using Omada Identity is to have an open mind and ensure that business areas and IT departments are aligned, as both sides play critical roles in successful implementation.

Omada Identity is a great IGA and IAM tool that integrates the latest AI capabilities and is highly recommended for those looking for user provisioning, application access, and enhanced security. I give this product a rating of nine out of ten.

On-premises

Omada Identity is used primarily for user access management, helping us manage user permissions in a centralized way. When a new employee joins, Omada Identity automates the user account and access provisioning based on their role, which reduces manual work and ensures users get the right access.

Additionally, Omada Identity helps with access review and user lifecycle management by improving visibility, reducing manual effort, and ensuring users have the right access based on their roles.

The best features Omada Identity offers are automated user provisioning, access management, role-based access, access review, and user lifecycle management, which significantly reduce manual work and improve security.

User provisioning has made the biggest impact by automating accounts and access provisioning based on roles, reducing manual effort and ensuring users get the right access quickly.

Access reviews are especially important as they help us regularly verify user permissions and reduce unnecessary or excessive access, improving overall security.

Omada Identity has positively impacted our organization by improving access management, reducing manual work, and making user provisioning and access review more efficient, while also helping to ensure users have the right access based on their roles.

I have noticed a clear reduction in the time spent on user provisioning and access management. While I do not have the exact percentage, automation has significantly reduced manual effort and improved the overall process.

Omada Identity could be improved with a similar interface, easier integration with third-party applications, and more advanced reporting and automation capabilities.

Better integration with cloud applications and ITSM tools would be useful, and more customizable reports and real-time access analytics would help with compliance and day-to-day access management.

Strong governance and security are important for Omada Identity's AI capabilities, as proper access controls, data privacy, role-based permission, and audit logs are essential for secure and responsible use.

The AI output from Omada Identity is generally accurate and useful for access analysis and recommendations; however, I would still validate important recommendations before applying them in production.

I have been using Omada Identity for one year.

Omada Identity is stable, saving us time in access provisioning. I estimate around twenty to thirty hours per month saved by reducing manual provisioning and approval tasks.

Omada Identity is highly scalable, as it can support a growing number of users, applications, and access requirements, making it suitable for expanding enterprise environments.

Omada Identity's customer support has been good, with the support team being responsive and helpful, and the service desk makes it easier to raise technical issues.

I would rate Omada Identity customer support an eight out of ten, as the support team is generally responsive and helpful when we face technical issues.

I previously used a manual access management process before switching to Omada Identity to automate provisioning, improve access governance, and reduce manual effort.

The pricing, setup cost, and licensing for Omada Identity are reasonable for the features provided, and the setup is straightforward. Overall, I find the licensing management effective within our organization.

Omada helped us deploy IGA within twelve weeks by focusing on recommended fundamentals and best practices. Initially, we gained faster user provisioning, centralized access management, and better visibility into user access.

I evaluated a few other identity governance solutions, including SailPoint and CAVION, before choosing Omada Identity for its strong access governance, automation, and integration capabilities.

I have seen a return on investment primarily through time saving, with an estimate of around twenty to thirty hours saved per month by reducing manual provisioning and access management tasks.

The pricing, setup cost, and licensing for Omada Identity are reasonable for the features provided.

I evaluated a few other identity governance solutions, including SailPoint and CAVION, before choosing Omada Identity for its strong access governance, automation, and integration capabilities.

I use Omada Identity's certification surveys to review and recertify roles, which help me identify outdated and unnecessary roles and ensure access aligns with current business requirements.

I use Omada Identity for role-based access control, which improves security by ensuring users receive only the access required for their roles, thereby reducing excessive or unauthorized access.

Omada Identity has helped me save significant time when provisioning access for identities. Approximately, I save around twenty to thirty hours per month by reducing manual provisioning and approval time.

I find Omada Identity's out-of-the-box connectors quite comprehensive, as they cover most of the applications we use and make integration and provisioning easier with minimum customization.

I recommend Omada Identity for organizations looking to automate access management and improve governance. It is especially useful for user provisioning, role-based access, and access review.

Overall, I am satisfied with Omada Identity since it has helped us automate access management, improve governance, and reduce manual effort, particularly with role-based access and access review capabilities that are crucial for maintaining security and compliance. I rate this solution an eight out of ten.

On-premises

My main use case for Omada Identity involves working on email templates, email notifications, event definitions, user groups, user identities, global instance management, asset management, asset instances, security resources, and other related tasks. I also work on identity import, user import, application entitlement import, and similar processes.

In my day-to-day workflow, I get stories based on customer settings, where options available inside Omada Identity allow us to change views. Additionally, if someone raises a request for configuration changes in the joiner, mover, or leaver workflow, I handle that too.

My main use cases also include asset instance creation, asset creation, resource creation, system creation, and application account creation, including application ownership. We can perform many of these actions through Omada Identity, and we're creating forms where we've added multiple columns inside views, utilizing database tables for various options.

I observed that when we change views through customer settings, we can automate various processes. Once, we created a process template for asset creation, asset instance creation, and resource approval, which all automate seamlessly using the configuration object functionality in Omada Identity.

The best features of Omada Identity, as per my understanding, include the TSEC option, which helps us configure things correctly and obtain quality results based on our client's requirements. Sometimes while configuring, we struggle to get proper results, but using TSEC significantly aids in resolving those configuration issues efficiently.

The TSEC feature is crucial, and I also find customer settings valuable, especially since I have been working with Omada Identity for one and a half years, allowing me to adjust configurations according to client requirements.

Omada Identity positively impacts my organization, particularly regarding security and efficiency. It provides multiple layers of protection for data privacy and prevention of data leakage, which I understand from my experience.

I would suggest improvements for Omada Identity, specifically regarding the user interface in version 15. Coming from version 14, I find the new UI a bit difficult to navigate, making it challenging to understand how to raise requests or get approvals, signaling a need for a more intuitive design.

Additionally, proper documentation is crucial because the provided materials lack detail. For someone unfamiliar with Omada Identity, comprehensive documentation would greatly enhance user understanding, which I believe is essential for clients and vendors.

I have been using Omada Identity for one and a half years.

Omada Identity is stable, but in comparison to Saviynt, it is not as user-friendly, and my experience shows that Saviynt offers a more intuitive and accessible interface.

The scalability of Omada Identity is good, though it doesn't match the user-friendliness of other identity management tools I've used.

Customer support for Omada Identity is lacking. When I encounter issues and reach out to the team, their responses are often insufficient, indicating a need for improvement in addressing user problems.

Before using Omada Identity, I worked on Saviynt, and for my identity management tool experience, the transition was smooth, as some tasks are similar, and using Omada has not changed much.

I am a reseller and not a partner; Omada and I collaborate directly to support our clients.

My experience with the pricing, setup cost, and licensing of Omada Identity is good. Omada team provides effective support regarding these aspects, making the setup cost and licensing processes manageable.

Before choosing Omada Identity, I evaluated Saviynt, and while I considered SailPoint, it was too complex for our needs, prompting my choice in favor of Omada Identity.

There are no additional improvements needed for Omada Identity that haven't been discussed, as I have shared everything I know.

I think it is important to emphasize the usefulness of Omada Identity. With some time dedicated to learning it, the understanding of its functionalities will improve significantly alongside better documentation.

Omada Identity is a solid tool but needs to focus on improving documentation and making the tool more user-friendly. I would rate this review as an 8 overall.

Private Cloud

Microsoft Azure

I use Omada Identity to manage user access. It is simple and saves a lot of time. The automation and user-friendly management are among the best features.

In my day-to-day work, I use Omada Identity to automate user onboarding by assigning the right access based on roles or department. Whenever a new employee joins, they automatically receive access to the required applications. This saves our time and reduces manual work.

Omada Identity has really impacted our organization positively because it has improved our access management by automating routine tasks, reducing manual efforts and errors. It ensures that users get the correct access within a few minutes and helps us improve security and compliance.

It has really saved our time and money because it has reduced manual user provisioning time by approximately 60 to 70 percent.

There are several best features in Omada Identity. The features are automated user provisioning and de-provisioning, role-based access control, access reviews, and compliance reporting. These features save time and improve security and also make user access management much easier.

Automated user provisioning has had the biggest impact because it automatically gives new employees the right access based on their roles. That really saves time and reduces manual work.

Omada Identity's AI capabilities are mainly focused on governance and security, which is really helping to identify access risk and improve the access reviews and support better compliance.

The output and accuracy of Omada Identity are very reliable and accurate. It provides useful recommendations for access governance. In most cases, the results are consistent and help us reduce manual efforts.

Omada Identity is working very properly. One thing that could be improved is the initial setup, which requires expertise that could be simplified.

I have been using this solution for more than two years.

Omada Identity is a very scalable solution.

The support team are very supportive and knowledgeable engineers, providing support 24/7.

I have not switched solutions. I am using this kind of solution for the first time.

I would advise planning your roles and access policies before getting into the implementation. This will really make the setup smoother and help you get the most value from Omada Identity.

We are a partner.

I have not evaluated other options.

I do not have any additional thoughts. My review rating for this solution is 9.

On-premises

My main use case for Omada Identity involves handling regular employees where we used to get the regular employees from the client and then update them into Omada Identity, where it used to create that user, all those things, user update, all the history and all we used to get it from Omada Identity.

When someone joins the organization, their account should be created. We get the update from HR as an Excel file stating that this user has been onboarded. We create their identity in Omada Identity, where username, user designation, department, first email, all those things we mention. Those data sync to our MIM, Microsoft Identity Manager. This is the process where I was involved in. In identity management, we were using Omada Identity and then access management we were using Microsoft Identity Manager.

As per my experience, the best features Omada Identity offers include excellent identity management where you can track user activities. Someone is changing the password, someone is doing any kind of change in the employee data. We can go to the history and find out exactly who has done the changes. This is very transparent, so that if anyone is trying to see about the user history, they can check about that if they have admin access.

The feature of Omada Identity has helped my team in day-to-day work significantly as I was a part of identity management as well as access management. In identity management, I felt that it is a very good tool and whenever we are updating the user data, it is getting created and then synced to our next target application. There was a very smooth process, and we were not encountering many challenges because the data which we are updating in Omada Identity was getting created and then processed by our sync system. We did not feel any big challenges, and we were working very well with Omada Identity product.

I noticed that Omada Identity has positively impacted our organization, improving transparency. Every employer needs everything to be tracked in a proper manner. Who is changing the password, why is changing the password, all the details are captured. This is the best feature which Omada Identity has and even employees and employers want that same thing.

Nowadays there are multiple tools available in the market. I am not sure how much Omada Identity can be improved, but I could say it is all good for now. As per my understanding, I feel very good using the application when I was in the product. I have completely moved to SailPoint now, but Omada Identity was really good for me.

If they come up with some good features that are in demand in the market, it will be a good thing.

I have been using Omada Identity for 3.5 years.

Omada Identity is stable and a good product.

Customer support from Omada Identity is really nice. We raised a concern to Omada Identity and quickly their team connected with us and resolved the issues we had.

Before Omada Identity, I was completely into manual provisioning where I used to monitor all the user accounts and their access manually. Omada Identity was the first identity management tool which I used. Before that, I was into manual provisioning.

Omada Identity was deployed in a hybrid cloud manner.

I was not involved in the purchasing because the organization assigned me to work on it, so I was working on it.

I chose a rating of eight because when I started working with SailPoint, I could see lots of differences in SailPoint where I use Entra ID and all SailPoint tools, and I could see that those are very smoother compared to Omada Identity. When I was working in Omada Identity, there were no such facilities in SailPoint. Now, SailPoint has some enhanced facilities, which is impacting.

If you have employees' data to manage, I would suggest you opt for Omada Identity. It is a really good tool, and it also has AI features available, which is really nice. I am providing this review with an overall rating of eight out of ten.

Hybrid Cloud

Amazon Web Services (AWS)

My main use case for Omada Identity is managing Wi-Fi devices, switches, and controllers of the companies where we install these devices.

A specific example of how Omada Identity is used in a concrete scenario within my organization is that it is used when Omada devices are installed for customers: Wi-Fi access points, switches, controllers, and so on. Through the cloud, we monitor the ports, how they are being used, Wi-Fi usage, and the frequencies in use. We also use the cloud service to understand whether they are installed correctly, the speed at which they are connected, the efficiency of the devices, and the optimization of the installations.

According to my experience, the best features offered by Omada Identity are that it is very fast, and the cloud management is intuitive. It is very easy to recognize if there are problems related to switch ports or the frequencies used on the access points. It is very easy to understand if there are devices that are not connected correctly, possibly connected at a lower speed than they should be. The color management of the ports makes it very clear what the port status is, and you can run a lot of diagnostics on possible problems, such as cables, ports, speeds, and possibly routing.

These features make daily work easier because through the cloud, it is easier to manage a remote infrastructure. There is no need to connect via VPN, there is no need to have a client inside the network to connect to, and there is no need to have an in-house technician at the customer site to monitor the situation because from the cloud you have all the logs you need. Omada Identity automatically connects to the customer's network device and transfers all the alerts and all the information about the devices to us quickly and clearly.

Omada Identity has had a positive impact on my organization primarily due to the remote management of the customer's infrastructure. There is no longer a need to go to the customer in case of problems because ninety percent of the time we can identify and manage problems remotely.

I do not feel the need to suggest any major improvements to the portal, since everything is very clear, including the network topology, which is done very well. I have not found any flaws yet.

The difference in how organizations are managed could be a bit clearer. I found this a bit cumbersome and not immediately clear, especially for those who use Omada Identity's cloud in a multi-organization setup, meaning those who have a single portal for multiple customers.

I have been using Omada Identity for two months.

In my experience, Omada Identity is stable.

Omada Identity's scalability is very good according to my experience.

So far, I have had few opportunities to use technical support, but the little support I have requested has always been provided quickly.

I previously used similar solutions, and I switched because of pricing, as Omada Identity is more competitive, and because of technical support, which disappointed me with other vendors.

My experience with pricing, setup costs, and licensing shows that the costs are very competitive for Omada Identity. I find that compared to other vendors they are cheaper and they leave a profit margin for the reseller.

I have already obtained a return on investment as I have been able to win tenders thanks to Omada Identity's more competitive prices.

I have not yet made the calculation to roughly quantify the savings obtained or the number of technical interventions reduced thanks to this solution.

Before choosing Omada Identity, I did evaluate other options, including Ruijie by Reyee, and I was happier with Omada Identity.

My advice to other people who are considering using Omada Identity is to absolutely try it because it is very convenient, fast, scalable, and very intuitive both in installation and in problem management. I would rate this product an eight out of ten.

Hybrid Cloud

Other

We use Omada Identity for managing 99% of our employees and non-employee identities. We also use it for provisioning to Active Directory and across 12 different SAP systems and two other application integrations.

Omada provides us with a clear roadmap for getting additional features deployed. Our company, in particular, has been a key player in getting new features developed through the years. A lot of the features that are in their product today started as a custom enhancement implemented just for us, which they eventually rolled into the core product. We have been a customer for ten years, and their product has grown significantly in terms of feature set and so forth over the last ten years. A lot of that functionality started with us. Not all of it, of course.

We were able to realize its benefits immediately. Prior to Omada Identity, we did not have an identity access management platform in place. Everything was done manually. We did not even have a homegrown solution or anything. Identity management, account creation, and other similar things were done manually, so there were immediate benefits as one would expect. Of course, not everything was implemented all at once. We primarily started with Active Directory, so we started with primary identity management and so forth and then rolled in other things through the years, which was well before my time in the space.

Their identity analytics helped us make informed decisions, but we are running a much older version of their product. They have made a lot of progress over the last few years. We have not been able to take advantage of a lot of new functionality that has been implemented particularly around analytics.

Omada's solution is set up to remove an employee's access as soon as that employee leaves our organization. It has significantly impacted our security. Omada does its part very fast, and then we have to wait for replication across the main controllers and things like that, which could take up to an hour. We desire to do it immediately. We would like people to lose access immediately, and Omada does its part, but the rest of our infrastructure is not always immediate due to replication and so forth. That is huge from a security perspective because we have use cases all the time with regard to employees or non-employees leaving abruptly and in a manner where you need to cut off access immediately. Prior to Omada, it required a lot of phone calls and manual steps to make it happen and usually not at convenient times.

We have used Omada's certification surveys to recertify roles or to determine if roles are relevant. That is one of my primary roles. I am on the governance side, so I am well-versed in their recertification capabilities. We have a variety of different ones that we run at different intervals. Most of them are semiannual, but, of course, we deal with the same challenges as every other organization. That has nothing to do with the tool itself. It is with regards to people rubber-stamping access and so forth.

We use Omada for role-based access control in a very limited way. The capability is there. We would like to do more, but anybody who knows anything about role-based access control knows that the tool is the easiest part. The business processes are the hardest part. It is hard to get people to define their access model so that you can use a tool to implement that access model. We are very limited when it comes to role-based access control. It is mostly for high-level birthright type of access and so forth.

It has very much helped us save time when provisioning access for identities, but it is difficult for me to provide any metrics because we have been doing it for so long. We do not have people, either employees or as part of managed services, who are in roles to do this on a regular basis.

Omada Identity has helped us consolidate disparate systems for access management.

Omada Identity has also helped us to automate reviews of access requests and reroute them to the appropriate people. It is hard to compare how it affects our help-desk workload involving access requests because we have been doing it for so long, but it certainly avoids a significant number of calls to the help desk. If this was done manually, there would be calls to our help desk. It will either be done by the help desk or escalated to an applicable tier-two support team.

They have gotten better in terms of the comprehensiveness of the out-of-the-box connectors. They do not have as extensive a connector portfolio as SailPoint does, but they have enough to meet our needs. They have the basics, and we do not need a lot of connectors to various applications because we have an access model that is highly dependent on Active Directory groups for access management. Omada Identity Suite does very well in managing AD resources.

Technically, the product does everything one would expect from an identity and access management platform. The product offers robust handling of Active Directory resources. 

The ease of working with Omada itself is commendable. They have been a great partner of ours for ten years, and it is clear they fully understand the identity space.

The biggest issue, which is the reason why we are transitioning from their product to SailPoint, is the overall user experience. From a technical perspective, it is a very good product, but from an end-user experience perspective, it significantly lacks. Although they have made some improvements over the last few years, it is still not on par with many of their competitors, particularly SailPoint. We have gotten so much negative feedback through the years on users not being able to effectively use the system. It was not always intuitive, so our leadership wanted a change.

We have used the solution for about ten years.

We do not contact their technical support directly because we have a service agreement already in place with them with some dedicated and some non-dedicated resources. We work through them if they need to escalate anything to the development or the level 3 support team. We never have to do that directly.

Neutral

We are in the process of migrating from Omada Identity Suite to SailPoint IdentityIQ due to the need for a better user experience.

We did an evaluation and looked at some of the other key players in the space but quickly settled on SailPoint.

From an implementation perspective, we had Omada resources who did the implementation. They do our support and all of our upgrade work. Omada does not have a lot of partners out there.

In terms of upgrades, the tool itself is not easy or hard. It is probably comparable to other identity solutions. For us, it is extremely difficult because of the detailed and thorough regression testing that we do for any upgrades, but that would be the case for any solution.

Early on, we did a lot of customization of the product that we had to go in and regression test everything, which made it extremely difficult. That is not Omada's fault. That is on us.

Being an on-prem solution, it does require maintenance. I would have loved to have gone to the Omada cloud product, but being an on-prem solution, there is regular support maintenance. We use Omada as a managed service provider for us, and they do a very good job with that.

They are positioned at a good price point. They are lower than some of their competitors.

I would rate Omada Identity an eight out of ten. The reason why I would not give it a nine or a ten has to do with the user experience.

My main use case for Omada Identity is for IGA projects which I do for customers. I can give you a quick specific example of how I use Omada Identity in those projects, but for one, it is not allowed to talk about, and for the second one I do is something I cannot fully disclose at this time.

Omada Identity's best feature is the role modeling. What stands out to me is how Omada handles the role modeling. Omada Identity has positively impacted my organization because it automates the work for governance proposals.

I can share that this automation and governance has made things easier and more efficient for me and my customers. The customer is happy that we implemented the system as we did, and when the customer is happy, we are happy.

Omada Identity can be improved with better performance. I would like to add more about the needed improvements, specifically around performance during dynamic role assignments.

I have been using Omada Identity for two years.

My experience with pricing, setup cost, and licensing is that it is satisfactory.

I would not add anything else about the features. Regarding Omada Identity's AI capabilities, I think that its governance and security are enhanced as AI helps, and we need to be careful that it just helps and we use it as a tool and not as a goal.

Regarding Omada Identity's AI capabilities, I think its accuracy and reliability of output are good. I would rate this review an 8.