Omada Identity Reviews

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.

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. 

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. 

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.

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

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.

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.