Omada Identity Reviews

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.

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

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

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

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

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

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

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

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

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

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

Omada Identity is a very scalable solution.

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

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

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

We are a partner.

I have not evaluated other options.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

We have used the solution for about ten years.

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

Neutral

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

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

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

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

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

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

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

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

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

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

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

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

I have been using Omada Identity for two years.

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

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

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

I am an independent IAM project manager consultant. I have deployed Omada Identity as an IAM/IGA platform for two clients: a university and a retailer. The retailer is a large enterprise with around 30,000 employees. 

Omada Identity has considerably improved operations at my current client. They didn't have an IGA solution, so it was a huge improvement. My other client replaced two other IGA tools with Omada. The solution's analytics reduce the overhead involved in identity management because we can optimize things via informed decision-making. Omada reduces the cost of IGA. It's an economical solution.

The solution has reduced some of the manual work required to provision accounts. It's hard to estimate how much, but I think 20 percent is a fair estimate. 

I'm not using Omada, but the interface is easy to use and gives you a solid overview of your identities. It automatically removes access when employees leave. This feature greatly improves organizational security because you don't want non-employees active in your systems.

Their out-of-the-box connectors are excellent. The client is integrating their SAP systems, and it seems to be straightforward. I haven't done many integrations with the standard APIs. It looks good so far, but I have limited experience.

I am not working with the product, but they have this BI tool for role-based mining, and I think that should be included in the core product rather than an add-on. 

When marketing its Accelerator Package, Omada should clarify the requirements with the customer. It depends on the know-how within the organization. You need a level of expertise in the organization. Many customers initially struggle because they don't know what to expect. It takes a lot of work internally before you can fully leverage the Accelerator Package. There's a learning curve. 

I have used Omada Identity since 2018.

I rate Omada 9 out of 10 for stability. 

I rate Omada 9 out of 10 for scalability. It's suitable for enterprise organizations. 

I rate Omada support 10 out of 10. 

Positive

I have used several solutions. The closest to Omada I've used is Sailpoint. Omada's advantage is that it's simple to use, and it has worked well so far. 

The cloud-based deployment was straightforward, but the on-prem deployment was in a highly complex ecosystem. Omada has matured since then. I wouldn't say that it isn't straightforward, but it depends on the customer. A standard deployment is relatively easy, but it can be more painful if you need a lot of customization. 

We deployed the cloud solution in around four months, nearly meeting the 12-week benchmark. The on-prem deployment took three years. It was a highly complex ecosystem that was dependent on other systems. 

Depending on the size of your environment, you need a product owner and some specialists for maintenance. My last customer was a university with a complex environment. They had around 12 people involved in maintenance at that organization. Typically, it's between 2-5 people. 

Omada provides clients with a return in the form of security and control. We can deactivate AD accounts that shouldn't be active, releasing many licenses and saving money. When we went live, we deactivated around 150 Microsoft licenses. 

Omada isn't cheap or expensive. The licensing model is flexible. I've only had limited interactions with the Omada sales team, but they were positive. They don't sell the customers more licenses than they need.  It's important to accurately forecast future usage. For example, we have many licenses that we don't use because we don't have the identities yet. We pay extra, which isn't good. 

I rate Omada Identity 9 out of 10. I recommend it. Omada has been an excellent vendor to work with. It's crucial to have a vendor that's helpful and supportive. Many of the products in this field are quite similar. For most companies, implementing IGA is a tricky journey that takes a lot of energy and effort. Their support is top-notch.

We use Omada to manage all personal user accounts, including Active Directory accounts and Exchange mailboxes. We're starting to use it more for access management. We have around 20 roles, and it will grow rapidly. We have some policies in place to automatically assign certain roles, like VPN access and roles for Office 365 applications on mobile phones. We have some distribution groups where we will assign roles to employees automatically based on their job titles or departments. We have 12,000 employees with accounts. 

Omada has sped up employee onboarding. It's more secure and requires less manual work. It's hard to say how long it took us to realize the solution's benefits. We started working with it during the pandemic, but nothing happened in the system for almost a year. Once we started onboarding all the personal user accounts, the process took us around three-quarters of a year.

The solution saves time when provisioning access for identities. It's hard to say how much because the local IT was responsible for these tasks, and now it's just two of us. 

Omada's onboarding features reflect our processes for onboarding new employees well. That is the primary reason we use this solution. We use role-based access control. I'm not sure how much it has improved our security posture, but it's made managing identities more convenient.

 We can also efficiently remove permissions when employees leave. We disable the account and remove permissions 30 days later. Before we went live, we collected all the Active Directory data. When we compared it to our HR data, we saw hundreds of accounts that were still active, though they were already terminated. I don't have the exact numbers, but it must have been hundreds of user accounts that were disabled and eventually deleted because of it.

Omada provides regular information and invitations to participate in the roadmap and see what's coming up. They also organize an annual user group. This year, we are participating in the German-speaking user group.

Omada could make it a bit more convenient to send emails based on events automatically. Having that functionality is critical for us to maintain transparency. I would also like more out-of-the-box API connectivity for REST services, etc. They already have something, but it could be enhanced. 

We went live with Omada in July 2021. 

Omada is stable. We've never had any downtime.

Omada is scalable.

I rate Omada support 9 out of 10. I'm quite satisfied. We have always had a strong consultant that supports us. We also created some support tickets, and almost all of our cases were solved quickly.

Positive

Deploying Omada is extremely complex. The roll-out process was straightforward, but integrating it with SAP ECC was complicated. The connector package from Omada was insufficient. We replaced SAP ECC with SuccessFactors, and the integration was better.  

We went live in one department for around a year. Then, we started onboarding each location one at a time. We had calls with the local IT personnel, HR, and the managers in charge to explain what would happen and things they could not do. After that, we did some testing in our test environment. We compare what will change and which accounts will be removed or created. We spent half a year onboarding location by location. We had two staff members for deployment on our side and two members from Omada. 

It's hard to calculate an ROI because an identity management system is just something we must have for compliance.

Omada is quite expensive. We are in the automotive industry. The pricing might be high because most of the other customers are in the insurance or banking sectors, but it's steep for an auto supply company. The license costs were able compete with the other solutions we evaluated though.

We looked at several solutions, including SailPoint, SAP, and One Identity. We had a detailed checklist with around 100 points. Omada had the most points and fit into the budget. 

I rate Omada Identity 9  out of 10. I recommend engaging an architect to help you develop the system. You need someone with Omada experience. The product involves some complicated processes, and you'll run into problems if they don't align with your company's processes. When you roll out Omada, you also need to look at your own HR processes.

We leverage Omada Identity for 2 main use cases. The first involves managing identities for various user groups: internal employees, technical users, and external users. These technical identities are then synchronized with Active Directory, where they receive Active Directory IDs for network access. The second use case focuses on access management, particularly but not limited to all our SAP systems. Within Omada, we can request specific users within the SAP system and assign them specific roles and authorizations. It's important to note that both of these primary use cases can be further broken down into sub-use cases.

We used Omada Identity for 10 years on-prem and switched to the cloud last month. 

The main benefits of Omada Identity lie in its regulatory compliance capabilities. This is particularly important for companies like ours that manufacture medical products. Many of our processes related to medical components are maintained and documented within SAP. Omada provides a secure and auditable way to track who has access to these critical processes. This ensures we can easily meet audit requirements by demonstrating which users requested access to specific SAP functions and who approved those requests. Omada also offers a high degree of automation. This streamlines the onboarding process for new hires, especially technical users who require access to various systems. In the US, for example, regulations sometimes require granting access within two days. Omada's automation helps us meet these tight deadlines by quickly provisioning technical access for new hires, external collaborators, and others. In short, Omada's focus on compliance and automation are the two key advantages that make it a valuable tool for us.

Omada plays a crucial role in swiftly revoking employee access upon their departure from the organization. It functions as part of an automated chain. When an employee's departure is registered in the HR system and all necessary steps are completed, Omada receives an immediate notification. This termination information is then automatically transmitted to our Active Directory and SAP systems within minutes, effectively blocking the employee's access.

Omada utilizes a role-based access control system. This approach informed our recent logic changes, which have been successful. We're now looking to gain more experience with this new functionality.

Omada Identity helped replace the middleware to consolidate systems for access management.

Omada Identity helps us automate access request reviews and route them to the appropriate individuals. After one month of going live, our help desk is pleased with the results.

Omada offers a technical solution that addresses both our needs. We had extensive requirements for two critical use cases: creating technical identities and managing and administering SAP users and roles within the authorization system. Omada meets all of these requirements.

There's a challenge with handling large amounts of data in this system. When we need to delete data, for example, we can't delete it all at once. You have to delete it in small batches, with a limit on the number of records per deletion. This is cumbersome for working with mass data, even though it might be acceptable for handling single records.

This limitation seems like an architectural flaw in the system. While it might be okay for individual data points, there's room for improvement when it comes to MES data. Ideally, we should be able to archive or upload all MES data at once, not be restricted by limits like 500 or 1,000 records. This limitation creates an unnecessary obstacle when working with large volumes of MES data.

I have been using Omada Identity for 10 years.

We ran into two issues during the implementation phase, but nothing since we went live. 

Our initial impression is that the performance is slower than we'd like. While I wouldn't say I'm entirely dissatisfied, we'd hoped for some quick fixes. Perhaps there's room for improvement in the program's logic. However, scalability limitations exist. We experienced these limitations during our go-live process, which extended from the planned two days to three and a half days.

The project environment is, of course, different from the live environment. It will be interesting to see how users react after the hypercare phase is over. If their reactions are similar to what we saw before, then the current level of technical support seems adequate.

Positive

Migrating from on-premises infrastructure to the cloud proved more challenging than anticipated. Planning for a six-month timeframe was unrealistic, and frankly, an overly ambitious expectation. While some vendors promote swift migrations, our experience revealed a year as a more accurate baseline. In our case, the process stretched to two years. Internal departmental requirements significantly contributed to the complexity.

The challenge wasn't solely about the migration tool itself. A key factor was our desire to migrate all historical data, which accounted for at least half the difficulty. Therefore, attributing the extended timeframe primarily to the tool would be inaccurate.

The project had a core team of at least 5 people who put in a significant effort. A larger group also contributed, but their involvement was more limited. Some of these contributions were temporary and focused on specific phases like testing. While the core team wasn't exclusively full-time, they were all deeply involved throughout the project.

Omada offers two services: one for products and another for consulting. We've also had Omada available as a consulting service for the past 2 years.

The pricing for Omada Identity is fair.

I would rate Omada Identity 7 out of 10.

The roadmap isn't entirely clear. It started as a discussion, and then things escalated quickly. Perhaps it's because we were just coming off a two-year cloud migration project. That was the main focus, of course. In a normal production environment, adding new features is a straightforward process. However, a two-year transition project presents a different situation. With hundreds of existing requirements and ongoing discussions which continued until our go-live date just last month, it's a different ball game altogether. This isn't a typical production scenario where we simply request a new feature. We're coming off a major project, so the approach needs to be different. We'll need to have a conversation about how best to support new ideas moving forward.

Omada Identity requires regular maintenance to ensure it functions properly. We need to identify the cause of any errors that arise. Omada, like a complex system, performs several tasks: it gathers data, processes it, and then exports it to other systems. These various interfaces can malfunction, leading to error messages. By monitoring other tools, we can identify issues. For example, if we see errors in five data transfers, we'll need to investigate the cause. This investigation will determine if the issue is due to incorrect data or a malfunctioning functionality. Initially, we receive six to seven support tickets per day. It's crucial to understand the nature of these issues. For instance, if emails are sent without a link, we need to add the missing link. Despite being a cloud product, Omada offers significant non-coding customization options. This allows for the addition of new functionalities or the correction of existing ones that may be malfunctioning or incomplete. In essence, this is what maintenance entails.

The availability of pre-built connectors for applications varies. There are excellent pre-built connectors available for SAP. Pre-built connectors for ADA are limited, but functionality can be expanded through custom development projects. Integrating other systems, particularly HR systems, with SuccessFactors without additional middleware is not feasible. The logic between HR systems and Omada is fundamentally different, and this complexity is not unique to our situation. Middleware is necessary to map and translate this logic between the two systems.

Our experience implementing Omada suggests using a larger implementation company with strong consulting capabilities. We found Omada's project management lacking. They simply executed our instructions, and we lacked a deep understanding of the tool. More consulting and guidance, beyond basic project management, would have been beneficial. Regarding historical data, migrating less is preferable. Importing large amounts of data, especially outdated structural data, significantly increases project complexity. Thoroughly documenting requirements early on is crucial, and ensuring the implementation partner takes the lead is essential. Omada did not provide a structured approach to gathering requirements. We relied solely on an Excel list for fields, which was insufficient for processes. A structured approach to requirement gathering, focusing on business processes rather than technical details, is vital for successful consulting engagements. A decision-making board that operates efficiently is also critical. Our board was effective in avoiding delays caused by outstanding decisions. Finally, a strong technical architect on the client side is essential for navigating the complex internal system landscape. This project is highly technical and sits at the heart of IT operations. Without a functional system, user productivity suffers.

We use it primarily for identity management for provisioning accounts and permissions to Active Directory and Microsoft Azure. We use it for providing our students/teachers with different roles they are assigned within the organization. We want to make sure that someone who comes into our organization both as a student and as an employee, maybe an external employee, gets one account with a different role setup and not multiple accounts.

We have various systems where our users are enrolled. For an employee, it is a HR system. For students, it is a system called Studielink, which is the Dutch body where students register the study that they will follow. Those systems have connections to our Omada system where their identities are compared and joined. If an identity already exists, an additional role is added to the existing account. Otherwise, a new account is added. People are assigned resources through group memberships automatically. They are assigned licenses. They are assigned, for instance, permission to enter certain buildings or to make reservations in the room system, and most importantly, because of the governance component that is present in Omada, when a student or an employee leaves our organization, their rights are revoked so that there are no people who are no longer a member of our system.

The improvements that we have seen are less manual work and less checking up. Some activities in our old system required manual interference. They are now automated. In the old system we used, we had to do updates two times per year on about 12 to 15 servers, whereas now, updates are done with just a few clicks. Everything gets updated with a few clicks. This is a priceless feature. There is less work and less hassle of doing system maintenance and upgrades.

Omada Identity has improved our compliance readiness. With the previous system, we never used auditing or any methods of revoking permissions other than doing that manually. If somebody completely left, then, of course, their account was terminated, but there was no real automation in the governance. We are still building and introducing Omada to our organization, and in the future, we expect a lot from being able to report on people having too much to less permissions and people who have no clue what they can and cannot do in our organization. With Omada Identity, we will be able to do some form of reporting to make it clear who can do what. The next step will be to employ some automation there to revoke unwanted permissions and completely disable those people who have already left. Their accounts should be terminated.

Omada provides us with a clear roadmap for getting additional features deployed. We have clearly outlined where we want to be in six months or twelve months. We get various suggestions from Omada in regards to what we could do to improve the use of their product in our organization and relieve the strain of some of the things that are currently being done manually or through other departments, which could easily be managed by Omada. One of the main objectives of the people from Omada is to introduce Omada Identity as widely as possible in our organization. This is also an advantage for them. The more we use it, the less likely we are to switch to another product in the future. That is understandable, but the people from Omada who support us are very sincere in their efforts to help us make our work easier and lighten the burden of administration.

It helped us to deploy IGA within 12 weeks, by focusing on fundamentals and best practices. We got our fundamental training. We have the best practices. Two of my colleagues and I attended Boot Camp training for a couple of weeks to get introduced to the technical side of Omada. We have access to an educational portal where we can take all sorts of courses and training for about a year, which was included with our Omada purchase, so support and education in gaining knowledge have been pretty good.

Our Omada solution is set up to remove an employee's access as soon as that employee leaves our organization. It has affected security positively because previously, if an employee switched departments, went on a sabbatical, or took a long holiday, his permissions in the system remained unchanged until someone woke up and noticed. After implementing Omada, if I change departments tomorrow, all my current permissions will be gone the day after tomorrow and will be switched to the new department.

The system for provisioning users, assigning permissions, and revoking permissions has been useful for the life cycle management of accounts. It is completely set up, and it was an eye-opening experience for us. We do not have to do any of these tasks manually. We just trust the system, and it all works out.

Omada's role-based access control has affected our organization's security posture. We are currently investigating how to further improve security measures by using Omada, but we certainly have made progress by defining certain groups and roles that should or should not have access to some of the systems. When we were using our previous product, there was less focus on security, whereas now, we have a complete department with four or five people focusing on security. The organizational focus on security has immensely enhanced over the last six to nine months. We do feel that we have more tools and availability now to do things that are related to security. For instance, when our security team has the ability and the knowledge to use the surveys, they will greatly help them find weak spots in the organization.

Omada Identity has saved us time when provisioning access for identities. It has saved us time because of the implementation path that we have taken and all the work that was put in there. The total amount of effort in our IDM and IGA has remained the same or become even more because we are just about at the point where we are running break even. The features we had in the previous system have now been built in Omada, and about 80% of them have been presented to the people who use them, so we are at the peak of our efforts. From here, it will be downhill, and the effort will be less. We can concentrate on other things. Two new colleagues I have will be learning both the tips and tricks of Omada, its limitations, and the way it works. With the knowledge transfer that we are doing among the three of us, we are discovering new ways to save time and effort with Omada. This is the point where we are right now.

Omada has helped us consolidate disparate systems for access management. Previously, there were various systems at play. Some of those systems were incorporated in Omada. There is still an external system assisting Omada, but instead of four systems, we now have only two systems. The total effort and the total investment have been reduced. However, in terms of time taken to give people the access they need, it does take more time than in the previous system. The previous system was event-based. For instance, if someone got employment at noon, they could work at one o'clock because it was event-driven. Omada is more batch-driven, and it goes through multiple stages to provide someone with an account, permissions, and licenses, but, overall, a student or an employee who gets enrolled can work within a day. We did not gain any speed there, but we did gain an easy way of working.

The support response time and the freedom from strange bugs and strange things happening in the software are valuable. We have people from Omada, Denmark supporting us in doing the implementation and building the system. We have a straight one-on-one contact with the people from Omada. They are very fast in responding when we have questions. This is a great advantage.

It is a very robust product. If anything goes wrong, our contact from Omada can pinpoint what we did, which is very understandable. We have rarely encountered anything going wrong. It is a very valuable feature for an organization like ours because we have an immense amount of user accounts, and it is impossible to manage them by hand.

The user interface could be improved. The interface between Omada and the user is mainly text-based. One of the demands that our management had for the new IDM and IGA system was that it should look like the interface of Microsoft products with a nice graphical interface. We struck that requirement from our list as soon as it became apparent that none of the products offered a nice graphic interface. They are all more or less textural. Interface-wise, it can look a little bit smoother, more like the 21st century.

It does not have a sharp learning curve. New users of Omada to whom we provide this service find it very easy, which is a plus. On the backend, using Omada and building and programming features have a steep learning curve. You need a very good technical background, but I guess this is how it is. This will not be changed or improved because this is the way the system works.

Out-of-the-box connectors were available for the applications that we needed. Only the integration with Microsoft Teams was not ready when we started implementation. We had to build things ourselves for that, so the connection to Microsoft Teams could be improved out of the box. It might have already improved. Our system is already built, so I do not know what has been added to the out-of-the-box functions. I would rate the integration that Omada provides an eight out of ten.

We have been working with it since July last year. That was when our go-live date was. It was around July 14. We have been working on implementing Omada for about two years.

Its stability is key for us. I would rate it a nine out of ten for stability. Nothing is perfect.

We have around 38,000 students and 4,500 employees. During the part of the season when students do the new enrollment and they get their diplomas, there is an overlap between year four and year one, and then the number of accounts can easily rise to 50,000 in Omada.

In terms of scalability, I do not see what is going on in the cloud, but I would rate it at least an eight out of ten in terms of scalability. As explained by the technical people from Omada, if we need more resources, it is just a few clicks for us, and we can give out resources to two, three, or ten times more accounts without any problem.

We very likely would add functionality to Omada because some of the processes are still being done manually or by another subsystem, which we want to get rid of. We want everything to be done on one platform. It is easier to support, and it is easier to maintain. It is easier for people who use the systems because instead of manipulating their data in three screens, they have two screens or maybe even one. Reducing complexity is one of our prime tasks.

They have very good support. I would rate them an eight out of ten.

Positive

We previously used the product from NetIQ. Before that, it was Novell. They have gone through three or four acquisitions and name changes. It was, in its own way, a very good system, but it was not cloud-based. Omada is cloud-based, and one of the prime demands from our management is that anything that we buy now will be cloud-based. The reason the product was replaced and not upgraded was that no cloud-based version was available. The install base was also declining throughout Europe, so the technical knowledge for supporting it was also diminishing.

Management took it upon themselves to get a product that was not dependent on one external person to incorporate new features and do the technical maintenance on the product. With Omada, there were more people supporting it and maintaining it. That seemed like a good step forward.

It is cloud-based. It was a straight-up choice. You either go for the cloud setup or you go for an on-premise setup.

The initial implementation of Omada was done by a third party who was asked by the Dutch Omada representative to help us. It was a nightmare. This party did not know much about educational processes. They did not know about our organization. They had not done their homework, and they lacked the knowledge required to do an implementation on this scale. Their main objective was to finish the small task they had to do and start writing out new bills as soon as possible. We parted with this company, and the people from Omada took over. It was a whole brand new experience of happiness. Suddenly, all things went well. Agreements were met, and the things that we agreed upon were indeed carried out to the extent that we expected. For the price that we agreed upon, work was done as we expected it. So, the first part was bad, but the second part was good. In retrospect, we should have gone with asking Omada to implement it for us the first time. It would have saved us hundreds of thousands of euros.

It does not require any maintenance from our side. The Omada platform automatically provides a message when an update is ready and by when we need to do the update, such as at the end of this month or the end of next month. All we have to do is click three times, and the update is done. Being very cautious, we always wait for four weeks before doing an update. If there are any flaws in the update, they will be noticed by other users and corrected in the background by Omada.

The company that was initially involved in implementation was Traxion from Holland. They were not prepared for the educational industry. Afterward, I learned from some colleagues in the field that they had already attempted to do an implementation with another organization, and they failed. Omada bailed them out there too.

I would rate Omada's implementation support an eight out of ten. There are always some glitches in an implementation. If you report a glitch and say that something is not going right, it is a completely different experience if you have to jump through seven hoops and wait three weeks, or it gets corrected the next day with the Omada team and the glitch is mitigated. It is a whole different experience.

From my end, there were three technicians, one product owner/project leader, one adviser from the cloud team, and one adviser specialist from the identity preparation team. All in all, it was a team of five people.

Being Dutch, I can only say that it is extremely expensive, but all software products are expensive. If you have 38,000 users, then even one dollar or one euro per person would amount to a significant amount of money. Because of the high number of users, anything gets expensive very fast here.

I would recommend Omada Identity to others. To those who are evaluating this solution, I would advise doing a very thorough proof of concept and making a very detailed plan of specifications and demands from the system. Whatever you do, do not use the Traxion company to do the implementation.

It has so many possibilities. We have not yet had a glimpse of all the possibilities. We are still on our journey to discover all the features of Omada Identity. We see a lot of things that can be done. We have barely touched the surface in regard to integrations. We have only done integration with Active Directory and Azure, and it seems to be working fine. Application integrations will be done next year.

The reporting is very powerful, and we have not yet gone into the details. From what we have seen, we know that we can do a whole lot of things. As ICT staff, we do not need to read or interpret reports ourselves. We can provide management with reports. It would be nice if the reports were in a nice readable fashion for the management, but I have not gotten any feedback back from management because we have not provided any reports yet.

Omada's identity analytics have not yet helped us make informed decisions faster than we could without them. We are not yet at that point in implementation to entrust the decision-making to Omada. Currently, people who use Omada as technical staff are purely ICT staff, and we are in the process of enrolling the educational support personnel into Omada. Decision makers and management will be introduced to Omada later on, but it is something that is on our roadmap. We will implement it in the future, but we have not currently implemented it.

Similarly, Omada Identity's reporting tools have not yet significantly impacted our decision-making. The decision-making part is on the road map, but currently, decisions are made at the table in the management staff's departments. They are not affected by Omada yet, but we hope to do that at the end of this year or the beginning of next year to help them see the great picture and make decisions.

We used Omada's certification surveys two or three times to recertify roles or to determine if roles are relevant. We used them partly by watching our Omada friends do it and making a survey ourselves, but this is also something that we have to learn how to do effectively and efficiently. It is loaded with options. Exploring all those options would be a few months of work in itself.

Overall, I would rate Omada Identity an eight out of ten. There is room for improvement. It is not yet perfect.