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.

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.

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 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 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.

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.

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.

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.