Omada Identity Reviews

Omada Identity is used for automation of life cycle management, compliance and audit management, risk mitigation, intelligent analytics, automation workflows, and self-service for end users.

Omada Identity has a very good and easy automated onboarding and offboarding process which provisions correct system access from day one when employees or contractors join, and it automatically revokes their access and prevents orphan accounts when they leave.

It provides role-based transfers which seamlessly upgrade user permissions when individuals change departments or roles, ensuring they only have the privileges necessary for their new positions.

For risk mitigation and intelligent analytics, it leverages machine learning to uncover vulnerabilities, recommends appropriate access roles, and flags anomalous user behavior before it becomes a security threat.

Omada Identity also extends strict governance controls and life cycle tracking to AI agents, service accounts, and API keys, securing the expanding IT infrastructure.

It allows businesses to map their paper-based approval process into automated drag-and-drop digital workflows without relying on complex custom coding and provides a centralized self-service portal for employees to request temporary or permanent access to specific applications with proper approval from one or two level approvers, which includes built-in routing to the correct approvers.

The value received from Omada Identity at the start was significant, particularly due to its codeless configuration, allowing us to map our approval process into automated drag-and-drop digital workflows without excessive complexity.

For access requests, we established a centralized self-service portal to manage temporary or permanent access requests with appropriate approvals.

Omada Identity uses machine learning to uncover vulnerabilities, recommending access roles and flagging anomalous behavior before it becomes a threat, providing confidence through initial POCs leading to a complete deployment.

Apart from pricing concerns, limitations in AI, and non-human identity governance, Omada Identity needs to simplify their complex onboarding processes and reduce operational overhead.

Omada Identity connectivity community provides basic documentation and tutorials that are helpful but could benefit from more detailed technical information for teams operating across different time zones. The use of the community connectivity packages is crucial for customization, especially during initial deployment for 12,000 users, although response times from support could be improved for quicker resolutions.

I have worked with Omada Identity for around one year.

The consolidation with Omada Identity significantly shortened the access granting process. An application was integrated within one week and a rollout to pilot users was completed, testing end-to-end scenarios for that timeframe and moving to all production users shortly thereafter.

Scalability issues arose when we attempted to manage 12,000 users across on-premise and cloud applications, exceeding the API rate limit, which temporarily halted performance until we contacted customer service, who quickly adjusted the rate limit. I rate the scalability experience as eight out of ten, while performance post-deployment earns a perfect ten out of ten due to meeting our expectations effectively.

For customer service, I would rate it a seven out of ten on a scale of one to ten.

Omada Identity provides rapid development and time to value; it can be fully deployed in as little as 12 weeks, minimizing typical long-term implementation delays.

It includes out-of-the-box, standardized workflows, which eliminate the need to design complex processes from scratch, and its no-code configuration system allows changes without expensive custom coding. Omada Identity strengthens our zero trust security by instantly revoking system access when an employee leaves or shifts roles, wiping out orphan accounts and mitigating ransomware exposure.

It lowers the total cost of ownership through AI-driven automation, particularly with Javi, an intelligent AI assistant that automates routine checks, speeds up request routing, and handles bulk access approvals.

It also helps reduce help desk burden by minimizing incoming access request ticketing via a secure, initiative self-service portal for employees.

The return on investment with Omada Identity is not as strong as anticipated, given its high cost and fewer features relative to competitors such as Saviynt and SailPoint.

Although Omada Identity is costlier than expected, it remains less expensive compared to SailPoint's AI offerings.

Comparing Omada Identity to other products such as SailPoint, it requires enterprise-grade AI identity security for larger user bases and substantial budgets, making SailPoint more suitable.

Omada Identity is ideal for those needing predictable pricing and strong workflow customization without coding.

The process of removing access starts from Workday, where accounts are disabled upon user departure, leading to automatic removals from Active Directory via configurations in Omada Identity.

Omada Identity's identity analytics utilize AI and machine learning to modernize identity governance and administration services. Features include Javi, an AI assistant that integrates with platforms such as Microsoft Teams and Slack, allowing for natural language processing requests for software entitlement, alongside intelligent role mining that automates corporate role groups and provides anomaly detection systems to neutralize potential threats.

Omada Identity has automated reviews of access requests, rerouting them to appropriate approvers.

We defined two-level approvers for critical applications and single-level approvers for less risky applications.

Access reviews are conducted regularly, prompting managers to recertify access if users have not logged in within certain time frames and implementing on-demand and time-based recertification processes.

Most of the access requests are automated, significantly reducing the help desk workload. If a user is removed mistakenly, they can raise a request through a ServiceNow form, allowing the help desk to add users back into their correct groups within half an hour.

The time required for provisioning access varies by application; some applications offer just-in-time access within one to two minutes, while others may take longer depending on the user's access methods such as single sign-on.

Omada Identity is set to automatically remove an employee's access as soon as they leave the organization using Active Directory for on-premise applications, syncing removals automatically through Omada Identity.

I utilize Omada Identity for both role-based and attribute-based access control, and we employ its role mining system to enhance RBAC schemas.

Omada Identity has improved our security posture by defining multiple roles and managing access control based on birthright access and custom approval levels, with role mining ensuring the automatic correlation of tasks and permissions according to job titles.

Omada Identity's role certification service helps us remain compliant and secure through on-demand and time-based recertification processes, allowing managers to approve or deny access based on user activity.

My advice to organizations considering Omada Identity is to choose it if they seek predictable pricing, moderate workflow customization, effective role-based access management, and minimal coding requirements.

I rate this product an overall eight out of ten.

My main use case for Omada Identity involves working for L2 support operations, where we have used it for onboarding contractors into Omada, and also passing user data to target systems such as Azure AD, Active Directory, and ServiceNow. When an employee joins the organization, HR enters the data, and after Omada import, the data comes to Omada Identity Cloud, and from there it passes to the target systems. For that use case, we have used Omada Identity, and we have also used it for providing roles based on user type.

I have used Omada Identity in another way as well. When a new user joins the organization, they may need system access. To enter login details such as user and password, that data should be available in our AD. By default, the new user has to have some basic roles, and all those things are handled through birthright provisioning from Omada Identity. Additionally, if a user's validity is over, meaning they have resigned, we remove all access for that user. If there is any urgent situation where some employees are terminated on the same day, we have used the emergency lockout feature. I have integrated Omada Identity with Power BI and SAP target systems, which is very useful, and Omada Identity Cloud UI is very friendly.

Omada Identity has positively impacted our organization very well. I have worked for a particular client with almost 12,000 users. When I worked for that client, they sold half of their company to another organization, and they asked us to change the user principal name. We managed to change the user principal name with minimal downtime of two days, and I executed a POC for that, earning a standing ovation award without affecting any team members over the weekend. We achieved this very easily because of the support from the vendor team and the user interface of Omada Identity Cloud along with all its features, which saved a lot of time for us due to these advanced features.

I can estimate that we worked almost 20 hours and saved a significant amount of effort. If we had done it manually, it would have taken a lot of time; we saved more than 45 to 60 hours of work during that transition, and there were no issues at all. We specifically changed only the user principal name and were careful to avoid duplicates. For instance, if an email address already exists in the Active Directory target system, changing the domain of the email address could create a duplicate. Therefore, we conducted a thorough exercise to avoid duplicates in ServiceNow and Active Directory, the two target systems, and we completed a POC one week prior, which saved us considerable time and effort. Omada Identity vendor team provided excellent support, and although we did not involve them in the actual weekend meeting, we asked them to be available in case any issues arose. However, we achieved our goals without needing their help due to the security enhancements and features of Omada Identity.

In my opinion, the best features Omada Identity offers include birthright provisioning access, which is the most valuable feature, and the emergency lockout. It is a very easy tool that anyone can understand, and we practiced for three months, requesting accesses and manager approvals. Each feature is unique and has its own value; they are helpful in our day-to-day activities to perform well.

For re-provisioning access and emergency lockout features, what makes them so valuable in my daily work is that when an employee joins a project and leaves that project due to some emergency, they need to move, and if they come back again, we can use the re-provisioning access. That is very important. The emergency lockout means that if there is any urgent termination of an employee, their access has to be locked out immediately, and then the emergency lockout feature comes into play, which is very helpful in my daily work.

Regarding the workflow, we have a manager level and application owner workflow. Based on the requirement, we can add levels of workflow, which is very valuable. We gather the business requirements from the particular application owners or teams, and based on that, we can design. The workflow is very well designed. Also, the upgrade features of Omada Identity happen regularly; we receive emails monthly, typically on the second Tuesday of the month. This is very helpful; if we report any issues or anything, they add those missing features and release them. Omada Identity upgrade is very simple, and anyone with minimal knowledge, by following the SOP documents, can upgrade it. Omada Identity Cloud is the best.

Regarding how Omada Identity can be improved, I find that Omada Identity import takes a long time. Also, in Omada Identity, if a user goes and requests, it creates jobs for specific target systems, and those jobs are limited to a threshold of 80 jobs per minute; that should be improved. I heard they are implementing AI into Omada Identity Cloud, introduced in the recent upgrade, which is very good. I want Omada Identity team to provide reports that allow me to see what accesses users have in bulk; it should be downloadable in Excel format. If they improve that, it will be great for tracking purposes.

I believe improvements needed for Omada Identity include out-of-the-box integrations and connectors for modern SaaS and cloud-native applications.

I have been working in my current field for three and a half years with Omada Identity Cloud, and I have a total experience of 13.6 years.

Omada Identity has been stable for us with no downtime or issues; we face it rarely. In case there is any downtime, they inform us via email or another form of communication, so we experience no issues.

In terms of scalability, Omada Identity is very scalable; it can handle an increasing number of users without any issues and easily manages complex environments. As I mentioned earlier, it is a configuration-based tool, making it very easy to manage.

Regarding customer support for Omada Identity, I rate it 10 out of 10, as they are very responsive and helpful. They consistently support us, and when we raise any support cases, they address and resolve them within the stipulated time.

Before Omada Identity, I had worked with SailPoint according to the project need. Before choosing Omada Identity, I did evaluate other options, particularly SailPoint, which I considered one of the best. Having worked extensively with SailPoint IIQ before moving to Omada Identity, I found that both are strong IGA platforms. I found that Omada Identity offers a streamlined approach to identity governance with robust out-of-box governance capabilities, a user-friendly business experience, and a cloud-first strategy. From a practitioner's perspective, SailPoint provides extensive customization and flexibility, while Omada Identity emphasizes standard governance processes and faster adoptions through configuration-driven capabilities. Everything can be configured in Omada Identity, which has given me a broader understanding of how different organizations approach identity governance based on specific business and regulatory requirements.

I have seen a return on investment with Omada Identity, as fewer employees were needed, which saves time in pricing, meaning investment. Maintenance is very easy; actually, one person can manage the operations. However, to support the organization, we maintain a team of two or three, but one is more than sufficient because of its operational efficiency, the security it provides, and the user interface, including the dashboard provided.

Regarding my experience with pricing, the setup cost and licensing for Omada Identity were handled by my manager, and I did not face any licensing issues for Omada Identity, nor did my team.

I have seen a return on investment with Omada Identity, as fewer employees were needed, which saves time in pricing, meaning investment. Maintenance is very easy; actually, one person can manage the operations. However, to support the organization, we maintain a team of two or three, but one is more than sufficient because of its operational efficiency, the security it provides, and the user interface, including the dashboard provided.

Regarding my experience with pricing, the setup cost and licensing for Omada Identity were handled by my manager, and I did not face any licensing issues for Omada Identity, nor did my team.

Before Omada Identity, I had worked with SailPoint according to the project need. Before choosing Omada Identity, I did evaluate other options, particularly SailPoint, which I considered one of the best. Having worked extensively with SailPoint IIQ before moving to Omada Identity, I found that both are strong IGA platforms. I found that Omada Identity offers a streamlined approach to identity governance with robust out-of-box governance capabilities, a user-friendly business experience, and a cloud-first strategy. From a practitioner's perspective, SailPoint provides extensive customization and flexibility, while Omada Identity emphasizes standard governance processes and faster adoptions through configuration-driven capabilities. Everything can be configured in Omada Identity, which has given me a broader understanding of how different organizations approach identity governance based on specific business and regulatory requirements.

Regarding Omada Identity's AI capabilities, I think the governance and security aspects are evolving well with intelligent recommendations, and it has many automation capabilities to improve the design, decision making, and access governance process. These capabilities help organizations reduce manual effort, identify access anomalies, and strengthen compliance. From a security perspective, features such as segregation of duties, audit trail certifications, and integration with enterprise security systems assist in maintaining compliance while reducing identity-related risks. I believe that AI can further enhance governance effectiveness, combined with Omada Identity's strong identity governance framework, particularly in areas such as access recommendations, risk analysis, and operational efficiency to minimize repetitive work.

Regarding the accuracy and reliability of the output from Omada Identity's AI capabilities, I find that the accuracy and capabilities have generally been reliable and serve as useful decision support mechanisms rather than fully autonomous decision-makers. I see Omada Identity's AI capabilities as an enhancement to improve efficiency and assist governance activities such as role recommendations and access analysis, while still depending on human oversight for critical access decisions. From what I have observed, the outputs have been reasonably consistent and trustworthy when implemented with a robust governance framework. I believe AI recommendations should always be validated through established approval workflows and governance controls, particularly in highly regulated environments, and Omada Identity's recommendations and insights have proven most effective when supported by well-maintained identity data and mature governance processes. The quality of the output depends significantly on the quality of the underlying data and access models provided.

My advice to others looking into using Omada Identity is to adopt Omada Identity Cloud because of its scalability and the impressive security features it provides. Omada Identity is most effective when an organization has a solid understanding of the user lifecycle process, access policies, and compliance requirements. I recommend investing time in role design, data quality, and application onboarding since these factors significantly influence the success of any IGA implementation. Engaging both business stakeholders and IT teams early in the project ensures the governance process aligns with operational needs. For an organization considering Omada Identity Cloud, I suggest leveraging its out-of-box capabilities whenever possible before pursuing extensive customization. Doing this can simplify implementation, improve maintainability, and accelerate value realization. Omada Identity is a strong platform for organizations seeking to enhance identity governance, automating the access management process and improving compliance, provided that the implementation is backed by clear governance practices and quality identity data. I give this review a rating of 8 out of 10.

Omada Identity serves as our primary identity and governance system for the entire bank and all applications and platforms, enabling central governance and administration and provisioning of resources. As a developer, I provide the ability to order access and minimize access to all systems users need. We control approximately 350 applications through it and serve about 20,000 users. Users employ it to change passwords on all systems and to request temporary and full access. We conduct four major reviews every year on everything, and we continuously manage movers, joiners, and leavers from HR data and other sources.

Omada Identity has given us much better control over who has what access than we had before, even though we had solid controls previously. Upper management can see what we do and when in a more visible way, making it easier to manage user restrictions effectively, such as ensuring that one person cannot perform both loan application and approval processes simultaneously.

The visibility for upper management works through our quarterly reports and others that they can review to see how well we are performing, which we present to the audit team who then present it to the managers and the board. The governance system involves splitting tasks among several people to ensure checks and balances.

Omada Identity's best features include an overall governance system that is appreciated by the managers. It can be quirky at times, but it has some restrictions that do not work well together with what we are working on, but we try to find ways to work around those as much as possible. Overall, it is a product that works well for us in the governance and access management area, although it is not as strong for provisioning yet, but it is getting better as we transition everything to REST protocols.

The governance system is appreciated by managers because they recognize that we are trying to reduce accesses. We aim to focus on roles rather than just access, which simplifies the process. Currently, it is more about access, but we want to transition towards a role-based approach. When it comes to restrictions, they are mainly due to bank regulations that create problems for Omada by restricting what we can access at what time, limiting our processes. It can be difficult to get through these restrictions because security always takes precedence.

Omada Identity could be improved by revamping the password system because the one in place currently does not align well with modern standards. I believe they would like to enhance it, but currently, their focus seems to lie elsewhere. With the industry moving towards passwordless solutions such as MFA, that might be the direction to head. I would also prefer a different workflow engine, although I have not experienced the one in the cloud yet. Currently, we use the Microsoft reporting system that came with an earlier version, but with the shift to a new report system in the cloud version, the transition might pose significant challenges, especially for our numerous reports. Transitional tools could help streamline that process.

Automation in Omada Identity is getting better with the newer versions, although in my view, the built-in workflow engine is not the best available. The reporting system functions well, but I know that the cloud version will change the report system, and I have no idea how much work that will entail with hundreds of reports. We will also change the HR system soon, which will require additional efforts, although I hear the new one will be supported by Omada. Regarding integration, we have a wide variety of platforms including IBM i, mainframes, Linux, Unix, and several thousand Windows platforms, which all require a lot of time to communicate with. Unfortunately, one downside of Omada Identity is that it can only handle one import at a time, making it resource-intensive for our numerous systems.

I have been in the field since 2005, and I have been in my current position since 2010.

Omada Identity is stable in that it runs without crashing. We do encounter occasional issues, usually due to bad data. At times, we require assistance from Omada to clean up blocks in the system caused by database changes, but overall, it is stable.

We run Omada Identity on a four-server setup, which is functioning well. However, we anticipate needing to expand due to how it operates, particularly since it handles imports in a single-threaded manner, which poses a bottleneck during processing.

I would rate customer support around a seven. While the expertise of the support team tends to be high when we contact them, the length of time to receive support can be an issue. We have established biweekly meetings for communication, which helps, but initial response times often require improvement.

When I started at the bank in 2010, they were using Sun Microsystems' old identity solution, which was run by Oracle for a while, but it went unsupported in the last years until we switched to Omada Identity after evaluating various products on the market.

My advice for others considering Omada Identity is to take your time and not rush into implementation, as doing so can lead to a messy state that might persist for a long time. It would have been best for us to start fresh, but that is not an option at this stage. Transitioning to the cloud might provide that opportunity in the future, so it is essential to plan and proceed cautiously.

I think we are performing well with our current staffing, managing a team of ten running a bank that serves 20,000 people and several hundred applications effectively. We are fully operational at all times, and while Omada Identity aids governance and access management, we also benefit from tools that enhance cooperation across sites. This results in time savings and improved onboarding and offboarding processes.

I would rate Omada Identity a seven or eight; it seems to work fine for our day-to-day operations. However, it does have issues that we would like resolved, and while the technicians are skilled, the time taken to solve problems can sometimes be frustrating.

I would lean towards giving it an eight because, overall, it is functioning well; however, the issues we face bring it closer to a seven. So, my overall experience is probably an eight.

I feel comfortable giving Omada Identity an eight because our team works with it daily and it is getting better with each version. Since we started with version 12, the changes are noticeable, especially now that we are on version 15, which is quite effective once we got it running.

I have not explored any AI capabilities in Omada Identity and did not even know it had such features. As I mentioned, I have not used AI features personally. I am primarily focused on platform interactions and building our own functionalities, so any AI features might be utilized by others in the security and governance teams, but I am not aware of them.

I find it odd that they are a European company selling products to European companies without apparent GDPR compliance, which has been a law in Europe for a long time, but besides that, everything is all good. My overall rating for Omada Identity is an eight out of ten.

I started in a consultancy company, and the first six months there I joined Omada Identity on one of their projects to get to know the project. I have been working with Omada Identity directly for 15 years.

Omada Identity provides 80% of functionality out of the box with standard features without requiring any special configuration. There are many templates available, so you can get up and running pretty fast.

Omada Identity's identity analytics helped reduce the cost of my IGA program. This has affected my organization's security since I am also in the same department as the security team, so we are very focused on that. Especially if someone is having a case with fraud or supposed fraud, we can click the log out feature and then all accounts will be disabled immediately or at least within a few minutes. I am sure that has helped the security level.

Omada Identity's role certification surveys have helped me stay compliant and secure, but we have not used them yet.

Everything can always get better. The maximum on my scale is basically nine. Regarding their documentation, it has become better, but there is certainly room for improvement. If you run into some technical problems, it can be quite difficult. Sometimes the log could be better, or the log is there, but then we cannot see it from here.

I have been working with Omada Identity directly for 15 years.

As far as I remember, I had some problems with upgrading the on-premise version. We are running cloud now and it is very easy. Basically, you can do the update online by just pressing the update button, and it will run for a few hours with everything coming back online. The different services will restart during the process, but the users will not notice the upgrade until the new features appear. Another feature I really appreciate is the ability to refresh development or test environments by simply going to production and creating a copy. After a few hours, you have a complete copy of that environment.

Omada Identity scales very well for our organization. We have less than 5,000 employees, and we do not run into any problems. A few years ago, we bought another company about the same size and merged them together, and that did not affect the performance of the system. However, it is still a relatively small scale.

I have called their service desk or help desk system every now and then, at least once a week. Their help desk is pretty fast. If you have an urgent case, they are on it within five to ten minutes and always react immediately. I would rate their job from 1 to 10 as a 10.

How long the deployment takes totally depends on the company, how fast they can deliver data, and how fast they can provide an overview of their data. You have to analyze the data you can get from the HR system and from other systems. If we go completely standard, you can connect to Salesforce in one week and Active Directory in one week also. HR depends on the system, so it can take anywhere from one week to several months.

For instance, if you are a manager and you want to show on the screen how many employees you have in your department, then you cannot make Omada Identity calculate that number and show it somewhere. Omada Identity has many powerful features with a lot of standard functionality, but if you want to do something a little bit out of standard, sometimes you can, but sometimes it is really hard work.

When we import new employees from HR, they are registered and we do nothing. We do not have to help with new employees or do manual tasks at all, at least in our department. I know some of the managers have to do some manual jobs, and they know their own roles and who should have access to what.

Regarding their pricing, costs, and licensing model, it is not my job to pay the bills. My manager is responsible for that, but I know he is satisfied.

Regarding role-based access control, I use Omada Identity for that, certainly. Everything is role-based because if you have fine-grain access where you have to go for separate Active Directory groups, that is basically a pain for managers and employees. If you have to request 25 separate groups just to do your work, then it should be wrapped in a role. So it is role-based 95%.

Regarding how Omada Identity's role-based access control has affected my organization's security posture, I would say it is basically our department that has done that, but we are using Omada Identity as a tool. I think we are measuring it, and we are an okay place, but we are always working to get better. Omada Identity has helped me consolidate disparate systems for access management. I would rate Omada Identity from 1 to 10 overall as an eight, and I provide an overall review rating of 8.

The main use cases for Omada Identity in these projects differ; some use cases focus on increased usability for end users, while others focus on compliance and regulatory demands.

In one case, the use case is usability, and the integration to ITSM tools or ticketing tools such as ServiceNow was a factor in increasing one pane of glass access to compliance and access requirements for users. Another case involves the increased regulatory demands for compliance; in this case, the Omada Identity portfolio of coverage was the main driver.

Some projects replace existing identity and access management systems, typically long-term running systems of ten or more years or even twenty years, during which significant changes in the IAM area occur. Switching to a new and modern cloud-based system has increased coverage and provided a much richer feature set, which applies across all IAM solutions.

The best feature of Omada Identity, in my opinion, is its configuration. Omada has a feature set that you configure to your specific use case without needing to program anything or develop custom solutions. As a cloud solution, it operates as designed, and configuring those capabilities means it is less technical in day-to-day operations than other solutions I have encountered.

My best comparison would be infrastructure as code, where you build capabilities and then use those capabilities to perform different tasks. The configuration of Omada works similarly; account provisioning is manageable, and integration possibilities exist across the board. The integrations use REST API, and you configure them without custom programming. You do not need custom add-ons for Omada, which is not feasible in a cloud solution, allowing configurations to be used in various scenarios.

Omada Identity supports regulatory compliance for my clients by providing reports for compliance teams to review. It features a strong request approval flow that supports audit trails of requests, meeting business requirements for those requests and approvals. This system enables compliance teams to generate their own reports without having to rely on the IAM operations teams for access to data. It is notably strong in this aspect as it can provide insights into segregation of duties. Users can define rules that will highlight when there is a potential breach in segregation of duties or toxic combinations, prompting the compliance team or responsible managers to enter either predefined or free-text descriptions of compensating controls to allow such conflicts. In scenarios where rule-breaking is necessary to maintain business operations, Omada will indicate that there is a breach, necessitating the provision of compensating controls and subsequently tracking the status of that breach, making risk exposure visible.

Omada Identity is a strong product, but it also has shortcomings. In the projects I have run, we have had to submit feature requests for enhancements and new capabilities, which have been provided in some recent releases by Omada. While we receive what we want, I have had issues where I think certain features should be functioning correctly without requests. These surprises arose particularly in a project managed by a very knowledgeable IAM department that has operated for over twenty years, knowing the requirements very well. Given that Omada ranks as a top product in Gartner's list, it is puzzling why certain issues exist. Nonetheless, Omada has been eager to address our requests; I have suggested improvements to SAP connectivity and ServiceNow integration, and they have responded positively. It is clear that while their architects possess robust knowledge in configuration and IAM, they are also on a journey to mature the product and enhance its robustness. Thus, I view it as a strong candidate for my clients' identity management needs, though it is not flawless.

Omada as a company needs to delve deeper into customer feedback because we have submitted requests for enhancements. While I know they are working on this, it is crucial for their growth to meet customer needs effectively. Another unique benefit of Omada is their accelerator pack, which can propel you from zero to a working environment with basic configurations in about twelve to fourteen weeks. I have done that twice, and it provides a really good experience that gets you off the ground. Then, you can either extend the basic capabilities or expand from there, meaning it is not a one or two-year-long project. You can start using Omada within three months and then spend the rest of the project time enhancing the coverage, which brings significant benefits to customers.

I have not received much feedback from audit and compliance teams indicating that Omada does not support audit and reporting requirements extremely well.

I have been running a project implementing Omada Identity for the last two years.

Omada Identity has been stable in my experience.

In my experience, Omada Identity's scalability is quite impressive in the cloud environment. I have worked with both large and small installations, with use cases generally involving fewer than five thousand users, and I have not encountered any problems. I know there are installations with user bases in the hundreds of thousands, but I have no insights into how they operate. The cloud model clearly allows Omada to effectively scale resources as needed.

The customer support from Omada has been excellent whenever we needed assistance. In my projects, I have worked with dedicated Omada architects and technical contacts, which allowed them to relay our support requests more effectively because they possessed inside knowledge of our projects, enabling them to frame the requests appropriately.

I previously used IBM Identity Manager, which was switched due to its end-of-life status from IBM.

Implementing Omada requires personnel to manage it; it does not run itself. However, I have seen one client reduce their Identity and Access Management team from three employees to two after implementing Omada. I have also noted a shorter lead time from approval to provisioning, saving time for end users. While there are clear advantages, I do not possess specific metrics to quantify them.

I would rate Omada Identity at seven or eight on a scale of one to ten.

Omada Identity is not a cheap license; it is on the expensive side, and there are certainly cheaper options available. However, I think the benefits outweigh the costs. I recognize that the cloud license tends to be pricier than the on-premises one as it accounts for usage in the cloud, but it is still more economical compared to a solution such as CyberArk, which I know is not optimal for IAM, while it is pricier than One Identity.

Before choosing Omada Identity, we evaluated a few other options, including SailPoint, among others, although I cannot recall all the names.

One of the key features of Omada Identity is the ability to build a hierarchical role model, which gets executed appropriately at different levels—entry level, department role, team role, and any additional roles that may stack on top. I have implemented this model twice with great success.

Omada Identity integrates reasonably well, primarily using APIs, with REST API serving as the main integration mechanism to directories such as Active Directory. This integration functions out of the box and is relatively straightforward. Other integrations, as long as they utilize REST API, are also strong and easy to implement.

In one instance, we replaced a system, resulting in an increase from three and a half thousand different accesses that users could request to more than twelve thousand at go-live. This means we removed over eight thousand manual requests by automating processes through Omada. I consider this a significant benefit that reduces time for end users, although it does not lessen the need for authorizations and approvals, but it does reduce manual work and ticket flow in the ticketing system due to automation, which is where Omada excels.

My clients have experienced that the identity and access management coverage—specifically, systems coverage in provisioning and governance—has greatly expanded with the capabilities from Omada Identity. Additionally, we have added richer features to the ServiceNow integration, leading to a very seamless one pane of glass approach to requesting and governing access.

I rate Omada Identity at eight out of ten overall.

My use case for Omada Identity stems from my position as an Identity Access Management Engineer. I used it previously as a user for a few months, and after that, I became the administrator of the platform itself.

The best features of Omada Identity include its cloud version, which is really fast, and I appreciate the main menu and overall look of the features; it is really user-friendly and easy for the users to understand what they want. 

As an administrator, I find that it is not complicated to manage, and you don't need that much background to do so. 

Omada Identity helps automate reviews of access requests and reroutes them to appropriate people, which is what it should do; it really assists in reducing the workload time. However, as an administrator, it requires knowledge of specific languages to perform the automation tasks, but in general, it does help.

I participate in the connectivity community by posting questions and acquiring clarifications, and I find it helpful; I have received multiple replies, indicating it is a good community support.

Omada Identity saves time in provisioning access for identities as it is linked to the HR system, allowing onboarding and offboarding to be done automatically; this includes the automatic creation of access roles. That said, the daily imports take time due to the size of our user base, however, they have promised to improve this in new versions.

Omada Identity is set up to remove an employee's access as soon as they leave the organization; if a user is marked as leaving in the HR system, their status changes in Omada Identity, and the provisioning will disable or terminate their account.

There is room for improvement in Omada Identity, primarily in customization for administrators; many custom tasks require contacting providers even for simple changes. 

We need more hands-on customization to meet our company's needs and not rely on specific templates or out-of-the-box solutions that incur additional costs. 

Aside from customization, improving the performance regarding imports and the clarity of error logs is essential; the logs are sometimes technically challenging to understand and do not make the error source clear.

The out-of-the-box connectors for applications can be challenging; even though some projects have used them with SAP systems, the connections are not that easy, and there needs to be clearer documentation or guidance provided.

I have been using Omada Identity for about three years.

In terms of stability, I rate Omada Identity a nine out of ten. In three years, we've only faced a few downtimes, about three or four times.

The scalability of Omada Identity is excellent; they offer flexible pricing for licenses, accommodating both full accounts and lighter identities, which makes it truly scalable and I would rate it a ten out of ten as they adapt to our needs.

We have a lot of users using the solution, over 26,000, and for this large number, I can say it's really good.

On a scale from one to ten, I would rate the technical support at a six; it's not catastrophic, however, it's not the best either, as first-level support lacks expertise, though escalated issues are resolved quickly.

Positive

While I don't have personal experience with other IAM software, I compare Omada Identity to solutions like SailPoint and One Identity and find that they are more advanced, offering more features. However, it depends on the company using them; they may not purchase the full suite of features, and those other solutions are considered market leaders.

While I wasn't involved in every aspect of the deployment of IGA with Omada Identity, I joined the team three years after it was deployed. My understanding is that they helped with the deployment. EAM was something new for our company, and they contributed alongside our specialists.

The solution does require maintenance, as we have monthly updates done automatically in the environment while the production updates are done manually to monitor things. Sometimes, Omada Identity tries to force updates to the latest version, as failing to do so can cause problems with older versions.

I'm not fully aware of the pricing details, which are managed by higher management; however, the product itself is said to have a good price, although the support can be expensive.

I would recommend Omada Identity to companies looking for a scalable cloud solution and good pricing; however, for other purposes, there might be alternative solutions on the market.

Omada Identity saves me a lot of time as I work daily in operations and on project tasks, helping keep my focus on other important matters; however, when issues arise such as errors in imports, it can take a significant amount of time to resolve, especially when we need to rely on support, which can be unresponsive.

Regarding compliance, the feature for access reviews isn't yet in use in our company; although it exists in Omada Identity, we are still working on integrating it as a focus area. 

I rate Omada Identity an eight out of ten.

For onboarding or assigning licenses through Omada Identity, when a new employee joins a company such as Sasol, we onboard them through Omada Identity by having their details logged through the system, which generates a user ID assigned to that specific user. Then, since they become an employee for that entity, we assign a Microsoft license to them so they can use all the Microsoft packages and tools linked to Microsoft.

In relation to my main use case with Omada Identity, I can also create security groups, allowing us to assign specific users to applications that require a certain platform access. Additionally, Omada Identity enables us to create shared mailboxes that can be linked to service accounts and shared accounts within the organization.

The integration with those systems helps my workflow and saves time considerably because I can manage all the accesses and assignments through Omada Identity at once, eliminating the need to add a license through Azure or a mailbox through Exchange. Data pulls from Omada Identity within the systems such as AD, Azure, and Exchange facilitate everything I create.

Additionally, I appreciate Omada Identity's ability to smoothly migrate everything, which is beneficial when migrating from on-premises to cloud.

Omada Identity has positively impacted my organization primarily through its identity management system. For instance, if there is a department using a specific folder of documentation and processes, we create a security group that assigns common access to that folder. This process saves time spent on assigning or sending links to every user. Users needing access, even from external departments, simply get assigned to that group and always have the most updated documentation. Omada Identity also allows us to give different access levels such as read, write, or read and write.

In terms of time saved compared to doing it manually with Omada Identity, I believe it has saved considerable time because we eliminate redundancy in assigning access or sending links continually. Moreover, it enhances security since user access requests require approval from group managers or folder owners on Omada Identity.

I chose a rating of eight out of ten for Omada Identity mainly due to the single sign-on functionality being the only aspect I feel could be better.

If Omada Identity had single sign-on, it would make everything much easier. If they expanded their services to more companies, it could easily be a ten. Overall, I believe it is a good product.

Positive

I have been using Omada Identity for about nine years.

My main use case for Omada Identity is implementing it at all my customers. I implement and support it and create the more complex new processes, wokrflows and extensions on Omada Identity for my customers.

I can provide a specific example of how I have used Omada Identity for one of my customers. We implemented Omada Identity to migrate from an on-premise old system to a new identity cloud system. We implemented it within a year with complex migration rules for the old system, and to the surprise of the customer, we completed it in eleven months and implemented all business functionality they needed and more.

That project was primarily focused on getting a modernized IGA system and real governance in place, and the customer was truly surprised by the extensibility of the product and the user-friendliness.

Omada Identity has positively impacted my organization as we have quite a lot of customers being satisfied and remaining connected to us for very long periods because of how satisfied they are with the product and our expertise. This connection is growing increasingly strong. Customers continue to stay, and more and more customers are coming in. That is very positive for our organization.

I can share more about the positive impact. We are a very small company and we tend to keep it that way, but we have grown from one customer on Omada Identity to now about eight customers, and about every year a new one is added to that. We also have multiple RFPs on the same customer that we receive. So there is more work at the current customers, but also very much new customers. That is good.

In my opinion, the best features Omada Identity offers are the no-coding solution. If you compare it with the other products, and I know most of them, the other products always have extensibility in code. We use Omada Identity Cloud and on-premise. The cloud version is strictly codeless and that really works well. But still, you have all the advantages of extensibility, creating custom data object types, or creating custom processes and workflows that really work well. So that is really the main advantage. Additionally, the adaptability of the configurations for all the connectors to existing source and target systems is impressive.

In the past, my experience with other products meant that if you wanted to change something based on the customer requirements, you had to code it and then test it. With Omada you can really do it codeless by creating a custom process with the process designer, adding the building blocks of the process designer into the process, and then getting it to work. This is truly a great feature of Omada Identity.

Omada Identity is moving towards a new reporting user interface, and that is working well. Customers are getting more and more pleased about the possibilities of reporting. If you compare it to the old reports from the beginning, it is much more user-friendly. So that is also worth mentioning.

Omada Identity can always be improved. It has an ideas portal for customers and partners. Since we are a partner, we have been providing them with positive insights on improvements. I would love to have better control on the improvements they want to create and in which order. A more close relationship to partners is greatly appreciated if they do that.

I think it would be great if they had even better control on the connection from cloud to the on-site or on-premise platforms.

Omada Identity is really stable. I have worked with it for the past nine  years and it is really stable.

Omada Identity's scalability is strong. I have customers with only two thousand identities in it and I have customers with over fifty thousand identities in it. So I would say it is really scalable.

Customer support is where we are in between most of the time. The customer calls us if they have a problem, and if needed, we reach out to Omada support. Omada Identity's support is, thanks to our relationship with Omada Identity as a partner, really fast because they know if we call, they really have a problem.

Positive

I did previously use a different solution, having worked with Behold, but that is end-of-life. I have worked with SailPoint and I was really not satisfied about all the amount of coding you had to do. I have also worked with One Identity and I switched over to Omada Identity because in my opinion, it is the best solution for the customer.

The initial setup for Omada Identity Cloud is fast and straightforward. For on-premises installations it is a bit more complex, due to the middleware needed like SQL Server, etc.
connecting to source and target systems is again easy. A bit more complex is the finetuning of the business requirements into the proper workflows.  Mostly because of historical ways of working of the customer that may need some adaptation.

We are a partner of Omada, specialised in IGA implementations of Omada, both on-premises and cloud. We often sell the product together with the implementation and most of the times including years of support, training and consultancy for the customer.

I have seen a return on investment, and we have done these metrics at several customers. If we look at one customer where we initially started, they had about four to ten employees working on IGA, and it is now almost half of it. So it is getting better. However, the implementation itself requires more people to get it properly working and after the implementation you can end up with a smaller crew for running the solution, but also with a crew to extend the soolutiuon for all business requests for IGA.

My experience with pricing, setup cost, and licensing is that I think they are the same as all the competitors. It would be great if they gave more insight into the real costs because that is typically a discussion with the customer and not with us.

Before choosing Omada Identity, I evaluated other options, including Saviynt, One Identity, SailPoint, and ForgeRock. Main differences are the Omada codeless versus java (a.o.) coding in the other products. The extensibility of the data model and in workflows and processes is something I could not find in the other products.  

The advice I would give to others looking into using Omada Identity is the advice I always give for each IAM or IGA implementation, and that is to keep the scope for initial implementation as small as you can. Do not think that it is a thousand things solution. Keep it small, but implement it well. First, start with the primary feed of HR into your main target system and then extend after that. Do not do it all in one. Do not make it a big bang implementation.

I have additional thoughts about Omada Identity. I would love to have a better press review in the market. Omada Identity itself is very good. It is in my honest opinion, better than the competition, but somehow they lack the marketing aggressiveness that the other vendors like SailPoint have. I would rate this review an eight overall.

My clients appreciate the user-friendly interface of Omada Identity. Currently, I'm working for a Norwegian client who appreciates the user interface, but Omada Identity is struggling to make the Norwegian language work.

We use Omada Identity for provisioning, de-provisioning, identity lifecycle, access review, access analysis, and compliance reporting, but not access management if we are discussing authentication.

Most of our clients deploy Omada Identity on-premises, but the current client is the first one rolling out a cloud solution.

My clients are medium-sized businesses, and we are going to manage around 30,000 identities in Omada Cloud.

Omada Identity helps automate reviews of access requests, generating an approval for the manager immediately when a request is created, so that process doesn't take long.

The setup to remove access rights promptly as soon as someone leaves the organization helps ensure timely removal, which increases the general security level when people are escorted to the door or leave for other reasons.

Omada's certification surveys have helped in the way that we have got the critical access re-certified by the owners, but we are not able to pull out an audit report proving it because it is not yet part of the cloud solution.

The deployment of Omada Identity is complex; the product is not brilliantly documented, and it lacks the same level of documentation that could be found for systems such as SailPoint or Saviynt, making it harder to find material or help online, particularly with Omada Cloud.

The system performance of Omada Identity is inconsistent; we've been analyzing this issue together with Omada, but we haven't been able to resolve whether the problem lies on their side or my client's side, which causes long response times and long run times in Omada sometimes.

Omada Identity does not help deploy IGA within 12 weeks; the time frame for applying the rapid deployment solution was much longer than expected, and I am unsure if it is built on best practices across all systems.

When we receive an error or system message from Omada Identity, it's very hard to decode what it means; we have had serious issues in daily imports that we can't explain, indicating a need for improved stability.

The comprehensiveness of out-of-the-box connectors that Omada provides differs; the connectors for Microsoft and Salesforce are good, but for SAP, they are basically non-existent.

I have been working with Omada Identity at several clients for approximately five to eight years.

The stability of Omada Identity needs improvement because we have experienced too many unexpected errors on a daily basis, causing significant trouble as we onboard more complex and business-critical systems.

The scalability of Omada Identity is acceptable.

The vendor support needs improvement because we have reported serious incidents that remain unresolved, leading to an unclear communication stream that often escalates issues to a critical level.

Neutral

Omada Identity has a strategic price model; it is not expensive compared to systems such as SailPoint, which are significantly costlier.

Much functionality is built in an Omada way, complicating processes that should be straightforward.

Regarding identity analytics helping make informed decisions faster, we haven't worked with that part yet, and I find the analytics capabilities in the on-prem solution to be better than in the cloud, which leaves me unimpressed.

I rate Omada Identity 5 out of 10.

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.

Positive

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.