Omada Identity Reviews

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.

The main purpose is to get services up and running for user management in the whole company and automate workflows. 

We have a pretty big team. We develop a lot of custom solutions. We mainly use it as a toolbox to get a baseline of the IAM platform. We are doing a lot of customization for data. Customization is the key. 

We are in an industry where we have a lot of regulations. Most of the regulatory IGA features that we use are mainly for auditing purposes. We do not use the whole suite for that. 

The data model and how the data model can be utilized to automate things have been beneficial for automating user life cycle management.

Omada Identity improves our compliance and audit readiness a lot because of the reporting capabilities that are there. Because we have a lot of data from the whole organization, we can support the review and auditing processes as well as possible. The historical information gathering that Omada supports is very helpful in such audits.

Omada provides us with a clear roadmap for getting additional features deployed. They have gotten much better in terms of planning the future. They are very transparent about which features are covered and which are not. They let us know at least a year in advance what is coming up.

It has been a very good joint venture. We started with Omada when the company was very small, and they had just started their business in Europe. We worked together a lot in the beginning and improved each other. We developed things that they now have in the standard Omada, and we developed them initially in our company. It was very nice working with them together. A couple of colleagues are still there after ten years. Omada is now a big enterprise. It is getting bigger and bigger. We are no longer the most important customer. Standardization is key for them now, but I am not 100% convinced that standardization always helps with the problem.

We are multidimensional when it comes to role-based access. We have a couple of enterprise role models running for different areas of our company. We have a very good model. Omada gives us capabilities for role management. It helps us to control which access is given to whom.

With Omada's reporting tools, we could make decisions related to onboarding. It was very helpful. We did a lot of analysis to see how many people we have given access to for certain applications, and then we used the data to push certain initiatives. The data that we got out of Omada helped us, but for the analytics, we used different software.

Omada's identity analytics have affected the manual overhead involved with our identity management. We always try to reduce the overhead on the business side of the company, and that is why we focus on automation. Our goal is to not have any manual inputs or access management in five to ten years. We are getting everything automated with AI tools and things like that.

The life cycle of identities is definitely covered 100% within our company, and it is mostly automated. We take away access when a person is leaving. This is definitely very good with Omada Identity.

Omada Identity has definitely improved our security from internal and external aspects. We have automated a lot of identity life cycle processes and situations. The automation enables an HR person to make a decision, and then everything onwards is secured by automation.

We have used Omada's certification surveys, but not as much as they are used, for example, within the banking industry. There they have regulations that it needs to be done in a certain amount of time. We use the re-certification feature for cleaning up things. For every application, we have somebody who is managing the roles, and we also have different departments to take care of the roles. They have also the responsibility to have it cleaned up and match what we need on the business side. That is an effort of the company. It is not something that Omada can take care of.

We have 1,500 stores worldwide, and giving access to every employee and region is fully automated. Taking it away is also fully automated, and we have a big turnover per year in our retail environment. About 40% of the staff is changing. It saves a huge amount of time. Overall, there are about 40% time savings.

Omada has helped to automate reviews of access requests and reroute them to the appropriate people. We also have a lot of customization. We are active in over 50 countries, and the approval mechanisms that we have differ from the standard. The capabilities and the toolbox that Omada gives us make it possible for us to control the access very well. The person who needs to be involved in the approval of something is always within the chain. It is working well.

Implementing Omada brought a lot of change. People had to adapt to requesting things themselves. It improved our operational efficiency a lot because people know they can help themselves. It brought a lot of changes, especially for the IT department.

The out-of-the-box connectors they provide are a good starting point, but there are always some customer-specific things that need to be added, which is totally fine. The standard connectors that they provide are always a good starting point.

Its best feature is definitely the process design. It is quite easy and straightforward to design a process. Customization capabilities in terms of adding code to the processes are very good.

The UI design needs improvement. One or two years ago, Omada changed its user interface to simplify, but the simplification has not really kicked in. UI design is something that can be improved.

We do not use the reporting capabilities of Omada. They can improve it and provide very cool automated reporting for us to use.

AI capabilities are another area of improvement, but I know that is already on the roadmap. They want to enrich AI mechanisms into role management and help requesters get to the role they need. That is definitely a thing to improve.

I have been using Omada Identity for ten years.

We have not seen any bugs or issues because we always went with the updates that were quite solid. We never went with the newest versions because we did not want to get any bugs and glitches, so we are quite happy. The service is running very smoothly, and we do not have situations where Omada does things that we cannot understand and support. It is transparent. I would rate it a nine out of ten for stability.

Scalability has improved a lot over the past years. I would rate it a nine out of ten for scalability.

Overall, we have 50,000 users, and there are a couple of thousands of users who use Omada and the processes of self-service. There are 1,000 to 2,000 users out of 50,000 identities in total.

We had special contact within Omada, so their support was always very good throughout the years. When Omada got bigger, they tried to standardize the support processes more and more. We were not that happy at certain points, but they have been working on it every year. They improved over the past year. They now listen.

We always do a lot of analysis before we open a ticket with Omada. We are not happy with the standard support answers because we would have already checked most things. I would rate their support a six out of ten.

Neutral

We did not use a similar solution before Omada. We only had Active Directory, and manual user management within applications. Omada has already been with the company for 15 years. I came here 10 years ago. It was the first IAM solution we used.

We have deployed it on-premises, and we are in full control of the infrastructure and the servers. We are still on-premises, but we are looking at the cloud solution. I am comparing a lot of things and assessing how we can work with customization in the cloud environment. A lot of decisions need to be taken if we want to go the cloud route in the future.

Its initial setup is quite complex. The most complex thing was getting the software from version 6, which was the initial version we used, to version 12. From version 7 to 12, there were a lot of structural and data models changed within Omada. They needed to be adapted to our environment, so the updates took a lot of effort, but it has gotten much better over the past three years because they did not do any big structural changes.

It took a few months to plan and implement it, but the deployment just took a weekend because of the prior planning we did.

In terms of maintenance, it does not require that much maintenance. The maintenance is mostly at the data level. You have to clean up the data in the database once in a while. Overall, the maintenance is quite low.

One or two external people and three to four internal employees were involved in its implementation.

We have seen an ROI time-wise. It lowers the effort with automation, so it saves time and money. There is at least a 50% reduction in the effort for a classic request scenario.

It is fairly priced for an on-premise environment, but for the cloud environment, I am not that happy with the pricing.

If somebody asks me about a good IAM solution, I would definitely recommend Omada Identity. If you have a very diverse environment, Omada's good features and capabilities would be useful to meet your company's needs. That is where Omada is very strong. If you are just a marketing company and you just want an IAM solution, you can go with Salesforce. If you have a complex environment where you need adoption to your business processes, I would definitely recommend Omada Identity.

Overall, I would rate Omada Identity an eight out of ten.

We use Omada as the core of our identity and access management operations. It centralises the provisioning, deprovisioning, and governance of accounts and access rights across the organisation. It’s integrated with platforms such as SAP HCM, GRC, Active Directory, Exchange, and Microsoft licensing, enabling streamlined, policy-based access control throughout our environment.

Omada has brought visibility, control, and automation into our IAM lifecycle. We’ve reduced manual effort by automating onboarding, offboarding, and access reviews. Its user-friendly interface, strong European support, and comprehensive integration capabilities have all contributed to operational efficiency and increased compliance posture.

API connectivity is a game-changer. It enables seamless integration with business-critical systems such as SAP, GRC, and Microsoft. The platform’s extensibility, combined with its rich policy engine and role-based access control, provides flexibility and governance. The intuitive UI, strong documentation, and access to a community forum are also key assets.

Integration logic could be simplified further for complex environments, particularly when handling rule hierarchies or large-scale data mapping. More native connectors and enhanced debugging tools for integrations would also be welcome in future releases.

I have been using Omada Identity for four years.

Platform is stable with very few outages. Most issues arise from external systems (e.g. HR feeds), not from Omada itself.

Scales well across diverse systems and high user volumes. Integration across cloud and on-prem services is handled reliably.

Omada’s support team is responsive and technically sound. Their engineers provide detailed, relevant assistance and actively engage in resolving escalations. I’d rate support a 8.5 out of 10.

Positive

Previously, we relied on Microsoft AD and other siloed tools. We moved to Omada for a unified IAM experience, allowing both administrators and end-users to manage access within a single, intuitive platform.

Initial setup was complex due to customisation and integration needs. It requires in-depth understanding of the business logic and data sources.

Used a vendor-supported implementation team with strong expertise in IAM and Omada-specific features.

We’ve seen strong ROI in reduced manual processes, improved compliance, and enhanced security.

Significant initial investment in setup and configuration. The value will pay off long-term, but plan for professional services or internal expertise for full implementation.

Yes. We considered solution - Omada stood out for its governance capabilities and integration roadmap.

Implementing IGA with Omada took us over a year, but it was worthwhile. Its built-in analytics, training resources, and excellent support were crucial for success. Automation reduced our workload significantly, and we now rely on Omada for everything from automated user provisioning to access reviews and certifications. Its policy engine ensures that role relevance is maintained, while its access restriction measures mitigate risks.

We leverage Omada Identity to manage user identities for governance applications. We integrate our applications with the Identity Governance and Administration system and conduct periodic access reviews.

Omada helped us deploy IGA within 12 weeks by focusing on fundamentals and best practices.

Omada's identity analytics helps us make faster decisions.

Omada is set up to remove employee access as soon as an employee leaves the organization. This improves our security posture.

Omada can streamline identity access provisioning by up to 5 percent. This efficiency is achieved by focusing automation on frequently used access rights, primarily those assigned to D groups.

Omada helps us consolidate some of our access management systems. However, we don't rely solely on Omada for all our access management needs. We also use Jira for other access management functions.

Omada Identity helped us save around 20 percent of our time.

The out-of-the-box connectors from Omada are easy to use.

I appreciate all the support we receive from Omada. Through Omada, we get to learn about all of our contacts and who to reach out to for assistance. The consultation sessions are also helpful.

The reporting and importing have room for improvement. Currently, it takes half a day to complete and since we are looking to implement more applications the time will only increase.

Omada comes with custom functionalities but the access rights review requires a lot of manual work and could be improved.

I have been using Omada Identity for 1 year.

I would rate the stability of Omada Identity 9 out of 10.

I would rate the scalability of Omada Identity 9 out of 10.

Sometimes the support team doesn't provide clear instructions on how to solve our problems. This might be because we have a lot of self-created content, making it difficult for Omada to offer one-size-fits-all support. Additionally, explaining complex issues with multiple solutions can be time-consuming. Perhaps this reflects a gap in understanding between how we, as customers, use the tool and how Omada anticipates us using it.

Positive

We previously used an IBM solution before switching to Omada Identity.

Consolidating our processes with Omada Identity has shown a return on investment.

Omada Identity offers a reasonable price point, but it will increase as we transition to the cloud.

I would rate Omada Identity 8 out of 10.

When there's a concern about something, such as reporting, the process usually follows a clear path. We typically hold meetings with Omada to discuss any reporting issues we encounter. After providing them with relevant information, the information is then released and formatted accordingly. However, this process likely applies to other types of information as well, such as details about upcoming features. This information is probably sent via email or can be found within the Omada staging area. In our specific case, though, our lead engineer handles the verification of that information.

We are currently in the process of training and implementing the certification surveys to recertify roles and determine if they are still relevant for employees.

Omada Identity is deployed across our organization of 16,000 people and managed by a team of 11 people in IT.

Omada Identity requires regular maintenance. Sometimes, we encounter issues with its functionalities, and troubleshooting is necessary to identify and resolve the problems. One specific process within Omada involves automatically sending new employee login credentials to their managers via email. Unfortunately, this process has been experiencing occasional failures. 

I recommend having a technical introduction or demo on how to use the features of Omada before implementing the solution.

Our final goal is the entire process of identity management including provisioning, de-provisioning, roles-based access, review-based access, and things like that, but first, we needed to replace the old legacy system. That was successfully done last summer.

The main business case was realizing a unique joined identity process because we have students and we have employees. We have external contractor employees, and we have partners who work for our organization and need digital or physical access to our environment. Because of that, Avans wants to use a single identity and an identity for life. If a student who once studied at Avans becomes a teacher or an ICT employee five or ten years later, he or she should have the same identity back with the same UPN or email address, so we have to guarantee an account for life.

Because of the source systems, we know it is a student, which studies they do, and, for employees, we know which department they work for and if they are a teacher or non-teacher personnel and things like that. Based on all those attributes, we have business rules guiding them towards a set of rights. From the moment they agree on the standard basic rules, we get their accounts created. We allow them to have access to that particular account. After the account is created, group memberships are assigned. Through runbook script, Omada sets the right into our Azure Entra ID environment.

Every implementation has some hurdles. Not everything goes 100% smoothly. In our organization, we have a lot of processes and an enormous amount of students starting the study year on the first of September. During this period, we have a lot of students coming in. We have been able to clear any hurdles because everything is traceable within Omada, and we also got the help of the Customer Success engineer from Omada. We were able to pinpoint any problem that would have impacted not only one person but hundreds or thousands of students or employees. In a very short duration, we were able to solve all the problems. That gave me a good feeling. We were expecting problems, but when any problem occurred, they were flexible and very fast in providing answers and solutions.

We did an evaluation almost three years ago in which Omada won. Within Omada, a lot of things are possible, and we have used only a few features. We had a go-live in July, and we are now closing the last features that are a part of the delivery plan for the go-live. So far, the implementation that we have is a replacement of the business logic of our old system. We are aware that Omada Identity can do more, but first, we need 100% synchronization with systems like Azure Entra ID. We are not there yet, but we are aware that it is possible. We have a standard way of onboarding, so we also know what to do when someone leaves a branch to remove those rights. However, within our organization, we still have other groups that are given access manually within other systems. We first have to synchronize with those systems or align with those systems before we can use Omada Identity to take control of removing an employee's access as soon as that employee leaves our organization.

We use Omada Identity for role-based access, but it is still very basic. It is on our roadmap for this year to continue with role-based access and provide departments and teams with the ability to add people to their environment based on the workflows available in Omada for group membership. The group membership is done by roles, and based on what kind of role someone has, the person is provided with certain software licenses, certain applications, certain data structure rights, etc.

Omada Identity has helped to automate reviews of access requests and reroute them to the appropriate people.

Omada Identity has had a good impact on our IT Team's operations efficiency. More and more things are automated. Only a few steps require manual decision-making. Its effect is very positive on our daily activities, and it will improve more and more.

What I like most is that we can always find a solution, and we can also find the cause when something goes wrong. I like that the most because everything is in one way or another traceable. That is what I like most. I like its reliability. 

Omada keeps on releasing new features within their product. We also have our own functional features. The roadmap of Omada quite aligns with our roadmap. The features available in Omada Identity suit our business case.

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

We have been using Omada Identity since July last year. We have been implementing it for two years upfront.

It is stable. I would rate it a nine out of ten for stability.

We have about 32,000 students, but that number fluctuates. Overall, we have about 4,800 identities for the staff. Some of the teachers work only one or two days, and some of the interns work only a few days.

It is very capable of scaling based on the needs of our organization. We have just started. We have to see how things go in the future, but I am very confident of that.

So far, we have Mads as our customer success manager. He is a very good engineer. He is almost a part of our team, so that works fantastic. We are now closing the go-live, and as we start using more and more roadmap features ahead, I hope that Mads will keep that connection with Omada for us. That was the biggest part of the success.

Positive

We had a Novell solution based on Novell directory services, and later on, that changed to the Micro Focus NetIQ solution. In addition, as our IBM tooling, we had a home-built database platform where we had some processes provisioned. They have already been migrated to Omada, and there are still some more to come.

Avans University is quite ambitious. As per our goals that we wrote down a few years ago, by 2025, we want to be more flexible. We wanted to provide students with a more flexible way of doing their studies. Until now, students come to an institute and do a course, and in that course, the path is already defined. The future students would be in control of their own study much more than in the past. A student in the future can decide to have a part of its curriculum from Avans and another part from Amsterdam University or another university. When they have enough certificates within a branch, they get their degree. It is no longer required that everything is done within one institute, so a student can follow a particular course, and then follow another course in another city or institute. For us to be able to do that, we have to be more flexible. We have to have a system that can cope with a lot of changes coming in the near future. The solution we had was not capable of doing that, so we ended up doing a new tender and looking for a solution that was cloud-based and flexible enough for a constantly changing environment. Our organization will constantly change, and the IAM system must be flexible enough to cope with that.

Omada has not helped us consolidate disparate systems for access management. We replaced the old system, so that is a one-on-one replacement. Now that we have installed it, we can start using Omada for workflows and things that we have automated in other systems. In the future, we will have more processes provisioned through Omada. It will start helping us there.

For us, it is a SaaS solution. Omada was one of the top solutions in our tender because of the capability of doing all from the cloud. Its implementation took us about two years.

In terms of maintenance, we have to execute the updates ourselves. Omada tells us that there is a new release, and we can execute it ourselves. Within a time period, we can allow it to happen, which is nice. Within the system, we also have our configured workflows. We have to keep checking that everything is running properly. When there is an update done by Omada, we test it in staging before releasing it in production. We want to ensure that our most important flows are doing exactly what they are supposed to do. That is what I call maintenance.

Omada used a value-added reseller to do the implementation, and things went wrong there. They were not capable of doing SaaS implementations. They were capable of doing on-prem implementations. We were the first or second SaaS customers, and they were not capable of delivering the solution we requested in our tender, but we knew that Omada was capable of doing so. Omada then took over in March or April 2023, so the actual implementation started in March or April, and we went live in July 2023. At the end of February 2024, we are closing the activities from that go-live in July. For me, it was successful when we directly got it implemented from Omada. 

When Omada took over, there were no issues at all. They provided us with what we needed. The most important feature for us was the identity join check process for which we needed an improvement. It was quite a big improvement, but Omada fixed it with extra code, specially built for Avans.

I would rate Omada's implementation services an eight out of ten, and I would rate the third-party provider one out of ten for the effort.

It is not cheap. It is expensive, but compared to what we did almost three years ago, it is value for money. It is worth it.

I would recommend Omada Identity if you are an institute like Avans or an enterprise. If you are a small business, I would not recommend it.

We plan to use more features as we go on. We will use the governance features of Omada Identity as we go on. We have not prioritized the governance features of Omada. They are very important to us, but we have to first align and connect a lot more systems before we can fully profit from the governance possibilities. Similarly, we have not yet used Omada Identity Analytics. Our go-live implementation was a replacement of our old system. Since then, we have released some of the end-customer features, and now we are starting with extra features.

Within the educational IT environment, security is our top priority. It has always been a priority and in the future, we need to prioritize that more and more. Omada helps us, but our Security and Safety department itself has ICT security as the top program running right now where security must be in every part of our environment at every second and in every decision we make. Having Omada implemented during that program makes us aware that we are quite good, but there is always room for improvement. Omada can help us with that a lot.

Omada Identity has not yet saved us time. We have mostly replaced the functionalities that we had from our old system. In the near future, we will have more automatic provisioning. People will also be able to provision other colleagues and things like that. It will help us a lot in terms of time savings, but so far, the time savings are similar to what we have had in the last five years.

Overall, I would rate Omada Identity an eight out of ten.

Omada Identity is our platform for managing the entire lifecycle of user identities, including creating and assigning roles based on changing needs (dynamic roles and birth rates), and we'll soon be implementing access review workflows.

Omada Identity prioritizes transparency in development by providing a clear roadmap. As a customer advisory board member, I gain access to this roadmap and can directly influence the product's future through feedback. This collaboration helps them prioritize features and bring them to production faster. I've even had direct discussions with their VP of product about our specific needs, ensuring they address functionalities that are currently immature or even missing entirely.

We saw the value in Omada Identity within the first four months.

Omada Identity deployed within 12 weeks.

Omada Identity's built-in data filtering eliminates the need for time-consuming manual data exports and filtering, allowing users to analyze information directly within the platform and make quicker, data-driven decisions.

Omada Identity has saved us time which could correlate to cost savings.

By automatically disabling access for former employees, Omada Identity strengthens our overall security posture.

Our organization is piloting Omada Identity's certification survey feature to streamline access reviews. This automated approach will ensure compliance and security by automatically collecting data from target systems, eliminating the need for administrators to manually extract, filter, assess, and compile information – a significant time saver.

We are deploying Omada's role-based access control across a large portion of our organization.

Omada has streamlined user provisioning for identity and access management, saving at least 15 minutes per user for the birthrate access method. It's also significantly reduced time spent on role-based access control, saving an additional hour or so per user.

Omada helped us automate reviews of access requests and reroute these access requests to the appropriate people.

Omada has significantly reduced our workload, particularly for tasks like managing birthrate access which was previously done manually. This applies to other areas where we have dynamic roles as well since anything directly integrated with Omada no longer requires manual intervention.

Contributing to the Omada connectivity community is valuable because it fosters a two-way exchange of information. We gain insights from other customers, their support staff, and engineers. This exchange not only allows us to help others and find solutions but also provides Omada with valuable customer data to prioritize improvements.

The most appealing aspect of Omada Identity is its self-service upgrade system. The cloud console allows us to control the update schedule, manage multiple environments by spinning up or cloning them, and configure most back-end settings without vendor intervention. This level of self-service is unmatched by many other identity governance solutions.

Omada Identity's user interface needs improvement, especially for new users. The key to a successful identity management system is ease of use for non-technical users. New hires or those unfamiliar with the system shouldn't struggle to request access. Ideally, the interface should be clear and straightforward, eliminating confusion about application types, entitlements, and permission levels. Users should be able to submit requests with confidence, knowing they have selected the correct options for full access. The burden shouldn't be on the user to understand the intricacies of the system behind the scenes. This is a common issue that Omada Identity, and similar solutions, should address.

Omada's pre-built connectors are generally effective, however a few require improvement. We've already informed Omada about these specific connectors.

I have been using Omada Identity for two years.

Omada Identity has been a significant improvement for us in terms of system stability. Unlike our previous solutions, which required extensive regression testing after upgrades and often resulted in bugs and performance issues, Omada Identity has not exhibited any lagging or crashing in our production environment, even though our lower environments have limitations due to weaker hardware. This has saved us a considerable amount of time and effort.

Our experience with Omada's scalability has been positive. We regularly communicate our data intake and future plans, including the number of systems we intend to connect, to ensure they can accommodate our growth.

While I appreciate that Omada's technical support surpasses my prior experiences, their response times can sometimes be slower than I'd like.

Positive

I have been deploying solutions for over 20 years and Omada Identity is one of the easier ones I have deployed.

We used two full-time and one part-time people for the deployment. 

Omada Professional Services assisted us with the implementation process.

Omada Identity is competitively priced and delivers good value for our money.

I would rate Omada Identity eight out of ten.

Omada Identity's cloud platform minimizes our maintenance burden; it handles most upkeep, leaving us with only essential tasks.

It's crucial to understand your business rules and data sources upfront. Not all identity management systems can handle complex rules or multiple sources of truth. Before implementing a solution like Omada Identity, ensure it aligns with your requirements to avoid compatibility issues and wasted effort.

We use Omada Identity for its intended purpose of identity governance administration and efficiency.

We are a large retail company with a wide network of stores and a significant number of employees. Our primary focus, until now, has been on automating processes for various scenarios.

Omada offers a clear roadmap for deploying additional features. They excel at communication, keeping users informed through regular newsletters, hosting user groups, and providing a transparent product roadmap. Additionally, they empower users to participate in product development through a suggestion system where users can propose improvements, vote on existing suggestions, and influence the future direction of the product.

Omada Identity has significantly improved our efficiency in several ways. First, automating tasks that were previously done manually, has freed up our staff's time. Second, data quality has increased because user account attributes, such as manager relations and address information, are now automatically maintained using master data. Additionally, security has been enhanced by assigning access based on policies, rather than simply copying permissions from existing employees. While compliance isn't a major concern for our organization as a self-owned retailer except for GDPR, the gains in efficiency and security are substantial. These are the primary benefits we've experienced so far, but we anticipate further improvements in the future.

Our implementation of Omada ensures that employee access is automatically removed when they leave the organization. This has significantly improved data security and quality, and we have streamlined the process through automation.

While Omada hasn't directly reduced our time spent on tasks, it has empowered us to undertake initiatives that were previously infeasible due to time constraints. Omada offers functionalities that significantly streamline these processes.

Omada's role-based access control has had a positive impact on our security posture. We are transitioning from our old method of copying user permissions to a more secure RBAC approach. This will require some cleanup of existing user permissions. However, going forward, our security will be automatically improved whenever we hire a new employee.

As an administrator, we benefit from a lot of functionality that is available out of the box, but it is also configurable to meet our specific needs.

Overall, the integration is excellent. A standardized connector REST scheme allows us to connect to a wide range of systems, including LDAP and others, simply by configuring connectors. This eliminates the need for custom development in most cases. This is a major advantage.

Additionally, the platform offers a user-friendly drag-and-drop interface that empowers us to create custom data, views, and processes with ease. By simply clicking within the tool, we can achieve significant functionality without any coding required.

The reporting on the warehouse data and the import process both have room for improvement. Omada has both of these areas of improvement on its road map.

I have been using Omada Identity for 14 years.

I would rate the stability of Omada Identity ten out of ten.

Our current usage hasn't necessitated scaling Omada Identity yet. However, based on the number of identities it can handle, it appears to be scalable. Additionally, I understand it's possible to spin up additional instances for further scaling if needed. Overall, my impression is that Omada Identity is a scalable solution.

On average, the technical support is good.

Positive

One Identity previously managed our Active Directory, but Omada has taken over that function along with several other systems.

The deployment took months to complete because our infrastructure presented challenges for Omada to integrate with. The initial deployment itself was quite complex. However, we've made significant changes to our internal infrastructure that have greatly simplified things. Omada has also made improvements that contribute to this ease of use. While the deployment was complex back then, I doubt it would be as challenging today.

Two people were involved in the deployment.

Omada assisted us with the implementation process. They conducted workshops and handled the initial installation and setup. While the project did not meet the 12-week target completion date, this wasn't solely attributable to Omada. We required adjustments to our infrastructure and master data to utilize the information in the manner Omada's system requires. Therefore, the delay in reaching full functionality wasn't necessarily Omada's responsibility.

I would rate Omada Identity eight out of ten.

Our organization has a single product installation managed by two administrators. We configure policies, mappings, and roles for this central installation, which applies to the entire organization. This encompasses 30,000 employees across more than 3,000 stores in 28 countries.

Omada Identity requires ongoing maintenance. There are three upgrades released annually for the on-premise version according to their current schedule. We've established an internal policy allowing us to defer two updates. However, an upgrade becomes mandatory after skipping two. This translates to at least one upgrade performed in-house every year. Omada offers upgrade services as an option, but we currently manage them ourselves. On-premise upgrades are more time-consuming compared to the cloud version.

Omada Identity offers a variety of pre-built connectors. These likely address the most common needs. Additionally, they provide connectors for specific products. However, the challenge lies in the flexibility of the standard REST connector. It provides many integration options, which can make it complex to use due to the sheer number of settings. While Omada deserves credit for offering a highly configurable solution, improved documentation could address this potential pain point. The extensive options and flexibility can lead to a lack of clear instructions and practical examples for using the product effectively.

I have been using Omada for 14 years and I would recommend it to others. For new implementations, I recommend the cloud platform.