Omada Identity Reviews

We leverage Omada Identity for access control. Our journey began with a focus on access management, recognizing that identity management is its foundation. To strengthen our access controls, we sought guidance and prioritized security by developing a security roadmap through IAM Vision. This initiative addressed access control challenges, including separation of duties, privileged accounts, and orphaned accounts.

Omada Identity's role-based access control has significantly reduced manual work and streamlined financial Electronic Access Provisioning systems. We've gained greater control, achieved compliance, and improved transparency through enhanced reporting. Additionally, Omada Identity empowers us to implement granular security measures, further enhancing our security posture.

Omada Identity offers valuable control capabilities. As a comprehensive solution, it prioritizes business needs.

It has helped automate a lot of manual processes, reducing errors and making the work more reliable.

It has helped put us in control of our identity and access management.

Omada Identity helps us accelerate our decision-making processes through its insightful reports and improved control overview.

It is set up to remove employee access as soon as they leave our organization. This has improved our security by ensuring there are no possibilities for a breach.

We use Omada's certification surveys to recertify roles and determine which ones are still relevant.

Omada's role-based access control improves our security posture.

Omada Identity helps us save time when provisioning access for identities by reducing manpower. 

Surveying is a valuable feature because it allows us to import data and see who has access to what data, for example.

The support response time has room for improvement.

We have had issues with some out-of-the-box connectors that required some fine-tuning on our end.

I have been using Omada Identity for almost 4 years.

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

I would rate the scalability of Omada Identity 9 out of 10. We started with 4,000 users and are now over 10,000.

The response time can be slow at times. They are knowledgeable but seem to be so busy that they can't respond to our issues promptly.

Neutral

We previously used a legacy tool that was integrated with our Active Directory.

The deployment took a year to complete due to the complexity of our environment. We encountered dependencies on a log server, firewall ports, and various other infrastructure elements, which significantly extended the lead time. Otherwise, it would have been a straightforward deployment.

While Omada Identity carries a premium price tag, it proves to be cost-effective. This is because, unlike competing solutions that necessitate additional customer interfaces, Omada offers a wider range of standard functionalities out-of-the-box.

I would rate Omada Identity 8 out of 10.

We're working with an Omada partner for Identity Governance and Administration implementation. While they offered a twelve-week timeframe for a typical deployment, our more complex environment necessitated a significantly longer lead time. In our case, the implementation took over a year to complete. It's important to note that this extended timeframe was due to internal factors within our organization, not any delays from Omada or their partner.

Omada Identity is deployed in a complex environment spanning multiple applications, Active Directory domains, Azure Active Directory, two countries, and several cloud data centers with over 10,000 users and 15 IT members.

Omada Identity is a strong product offering from a reputable vendor. While some users might find the level of support lacking, I've been satisfied with the solution and would recommend it to others.

We use Omada to onboard and delete employee accounts, set permissions, and handle access requests. Our company has around 650 to 700 users and seven IT team staff working with it regularly. 

As someone who handles the accounts and Active Directory permissions, I think the greatest benefit is that the account creation, provisioning, permission assignment, and other processes are all automatic. It also handles Exchange provisioning, home folder creation, etc. We're saving many hours each week from that. That's about 5 or 6 hours across the whole team. 

We previously had a lot of manual processing where we had to determine whether end users should be given access. Now, we have a simplified process where the users request access and are approved. It saves us about 10 or 15 minutes per user, and the team saves a couple of hours weekly. 

From the end-user perspective, the biggest benefit is that there's only one portal to request permissions and see what you can access.  They can go into Omada and request something they need, so it's simplified for the end user. The analytics have helped with our manual overhead. Some systems contain multiple machines, and we've bundled them into one resource. Omada has improved our compliance. We're getting closer to a complete overview of our systems, permissions, and access. 

Omada's best feature is creating accounts, automatically assigning permissions, and distributing resources based on assignment policies. It also provides a clear roadmap. We have been to a couple of user groups where they discuss upcoming releases, which you can see in the pending release notes. They also host webinars about new major versions to notify you about something that you might want to utilize. 

With role-based access controls, system owners have a better overview of who has access to their system and the permissions. They can see for themselves what is possible. We previously lacked an adequate overview of the systems, so users could potentially have access to things that they shouldn't.

Omada's reporting makes us more aware of which systems have duplicates or do the same thing when we're talking about the system owners and onboarding systems, so we can skip one of them. Omada removes access automatically when employees leave the organization. It feels good to know that when an employee becomes inactive, all their resources are deprovisioned, and they're locked out. After a couple of months, the account, home folder, mailbox, etc., get deleted, so there's nothing left for them to access.

Improved traceability would be helpful for administrators. For example, let's say a user's permission is being revoked. We can only see the system that has carried out a particular action but not what triggered it. If an event definition or something has changed in the criteria for the permission being removed or something like that, we don't have immediate access to that information. It takes a little detective work. 

We started using Omada in May 2023

I rate Omada 8 out of 10 for stability. It requires minimal effort to maintain, but there are a few errors and quirks. 

I rate Omada 10 out of 10 for scalability. They have many APIs to work with. Omada has a comprehensive set of connectors. We are mostly using the connectors for our HR solution, Microsoft Exchange, and Active Directory, and those work well. 

I rate Omada support 9 out of 10. We haven't had an SLA in place for long. They respond quickly when we submit service requests, and I'm receiving excellent assistance in most cases. 

Positive

We had a homegrown identity management system with many scripts that we've retired. That has been nice because it involved many lines of PowerShell scripting that we had to maintain. It was somewhat difficult to troubleshoot or add and remove things.

The guy who built it left the company. It was a complex solution. It was hard to maintain and support. We also felt we had no control and lacked an overview of our systems. We had them in an Excel document. 

Things went well when we finally deployed Omada. There were a few issues to iron out, but it was smooth when we went live. All in all, it was a good implementation. It took about two or three working days to complete. 

Omada requires minimal maintenance after deployment. You need to review some of the reported data, but that probably has more to do with the HR information we're fed. There are also periodic updates or things that aren't working correctly that must be fixed. Overall, you don't need to put much effort into the solution to keep it running. 

I rate Omada Identity 9 out of 10. 

We used Omada Identity to control the entitlement catalog of most or all of the access rights in the company. The main use of the solution was to control the catalog that determines the possible accesses and who has them. That's the foundation to get control over the existing accesses.

Omada Identity has benefits that are in common with all of the IGA vendors that Omada competes with. The benefits of Omada Identity include a holistic way of viewing access, the ability to give people access, and automation.

There seem to be many different and complex ways to do things in Omada Identity. I would like to simplify how configuration is done and also have fewer different ways of doing things. The solution should be made more agile for customers to own or configure.

Omada Identity needs to invest more in analytics capabilities. Currently, identity and access analytics are add-ons that you do in Power BI on the side. It's not a part of the product, and it's not directly accessible to the customers. I would like to see identity analytics capabilities in Omada Identity.

I worked with Omada Identity for half a year.

My team had contacted Omada Identity's technical support for a few things, and I think they were generally satisfied.

Before Omada Identity, I worked mainly with Oracle and CA Identity Manager, who are not a big part of the market.

The main advantage of Omada Identity that needs to be mentioned is that for a SaaS solution sold to a European company, it is compliant with GDPR. None of the other companies can comply with GDPR as a SaaS service because they are either US-based or use non-European personnel to administer the SaaS solution.

I don't have the details about the solution's deployment since I wasn't directly involved in the setup. I just know that it wasn't as smooth and straightforward as we had hoped for.

We got help from Omada professional services to implement the solution. They were absolutely helpful and knowledgeable. We had senior resources from Omada who really knew what they were doing. Omada Identity's deployment took two months.

Omada Identity is very reasonably and competitively priced.

Omada Identity has a pretty simple licensing model, with not so many things to pay extra for. Compared to other solutions with different prices for different modules, it's easy to plan and pay for Omada Identity.

I haven't directly worked with any of the current big vendors, such as Saviynt or SailPoint. I've only evaluated them.

Omada Identity is quite good at providing a clear roadmap for getting additional features deployed. We've always been able to have good discussions with Omada's product managers about the features we would like to have. It's a good environment for discussion, and I've heard from others that Omada is good at listening to customers and getting features into production within a year or so.

Omada partially helped us to deploy IGA. However, the company I was working for needed to take more charge and do things a bit differently. It was not possible for Omada to do that for us. Omada did help, and it was not Omada's fault that it took longer.

It's too early to say if the solution's identity analytics has affected the manual overhead involved with our identity management. It should have had a positive effect because it should be easier to request more things automatically. Since that's not in production yet, we couldn't measure the effect, but it looked promising.

Our Omada solution is set up to remove an employee's access as soon as that employee leaves our organization. This setup has positively affected our organization's security because we have less overall access.

Omada Identity was deployed as a SaaS solution in our organization.

I think Omada Identity is flexible enough to be used by both smaller and bigger companies.

Based on what I've seen, Omada's out-of-the-box connectors are more than sufficient.

I advise users to assess their data quality and make a clear cleanup plan before using the solution because Omada is not well-suited as a cleanup tool.

Overall, I rate Omada Identity a seven out of ten.

We use Omada Identity to promptly disable access upon termination of an identity, regardless of whether it's a contractor or a full-time equivalent employee.

Our secondary use case is to conduct access reviews. During these reviews, we examine user access across different applications to ensure it remains appropriate for their current needs.

Our third use case involves provisioning new access and updating access changes in an automated fashion.

The biggest benefit for us is ensuring compliance with timely termination of access. This helps us maintain our security compliance with various frameworks like SOC 2 and SOC 4. Ultimately, it gives us confidence that we're unlikely to have any findings during an audit. Additionally, it strengthens our overall security posture by enabling us to effectively manage the lifecycle of user accounts and their associated identities. Omada Identity has improved our security, governance, and business user automation functionality. It has enabled us more efficiently to provision access for people and reduce the time it takes to get a person access to what they need by providing us with the capabilities to create roles and automate a lot of the activities.

It helped us deploy our cloud portal and set up 3 environments within 12 weeks. However, getting everything fully operational, including integrating various applications, took longer than 12 weeks.

Omada Identity's analytics have helped us make informed decisions faster than we could without them.

It is set up to remove an employee's access as soon as the employee leaves the organization or a contract has ended. This improves our security because we don't rely on managers to submit a request to remove access.

Omada can significantly reduce the time it takes to provision access identities, but its effectiveness depends on how well our systems are integrated and the maturity of our identity governance processes.

It has streamlined the process of reviewing access requests by automating tasks and routing them to the relevant personnel. This has significantly benefited our governance team, as what was previously a manual process now features a much cleaner user interface for both managers and reviewers.

The community forum is a valuable resource. It provides a wealth of information and lessons learned from other customers as they implement the product. This helps us identify and avoid common pain points.

Two valuable features of Omada Identity are the ability to discover accounts and link them to identities, and the automatic disabling of inactive accounts or identities.

The roadmap that Omada Identity provides for deploying additional features is adequate, but it would benefit from more frequent communication with its customers. They occasionally hold advisory board calls where multiple customers participate. During these calls, they discuss the roadmap and what they're working on. However, they also have several community forums. Frankly, most people don't have the time to monitor all those resources for updates.

While the Omada certification survey is a helpful tool for verifying user roles, creating the survey itself can be challenging. The process is not very user-friendly, and the available documentation is not sufficient to get started easily. For more complex surveys, it may be necessary to resort to professional services.

Omada's reporting functionality is limited and could benefit from greater customization. Unlike other solutions that allow users with SQL knowledge to create tailored reports, Omada restricts users to pre-defined reports offering only generic data that may not be relevant to specific needs.

Omada currently forces users to install the newest version. We would appreciate the flexibility to choose an earlier version, such as the one preceding the latest release.

I have been using Omada Identity for 2 years.

The technical support team is constantly working to improve, but resolving complex issues can still be time-consuming. Omada, a highly customizable tool designed to integrate with various target systems, presents a challenge for support since its complexity can make it difficult to diagnose problems quickly. However, the Omada team understands the difficulties users face when troubleshooting these issues.

Neutral

The initial deployment was difficult and took over one year to complete.

Several teams came together to deploy and integrate Omada into the baseline systems required for the IGA to add value. 

We used Omada to help with the implementation.

Omada is expensive. In addition to the licensing cost, support can also be expensive.

I would rate Omada Identity 7 out of 10.

Omada does require maintenance after it is deployed.

The out-of-the-box connectors are hit or miss.

For Omada users, understanding the account and identity lifecycle is crucial. Additionally, familiarity with the data, including potential inconsistencies, is essential.

We use Omada Identity for identity management and access management for requesting mailboxes or user-based policies.

Omada provides us with a clear roadmap for getting additional features deployed. AI integration is expected shortly, which could offer valuable capabilities like machine learning. The possibility of creating new security group functionalities is also being explored, allowing for the automated assignment of specific access permissions to designated individuals.

Omada's Identity Analytics helps us make informed decisions faster than we could without them. Creating new security measures or setting new rules is both easier and faster.

When someone leaves the company, Omada automatically disables their account. This process is entirely automated.

Omada's role-based access control helps our security posture by enabling us to assign certain rights to people based on their roles.

Omada helps automate reviews for access requests and reroute them to the appropriate people in charge.

Omada Identity is easy to use. The interface is good and customizable.

Since implementing Omada Identity our IT team's operational efficiency has improved. 

The most valuable aspects of Omada Identity for me are the automation capabilities. These include user-based policies, user-based access controls, and automated group creation. Overall, it simplifies the management of both users and policies.

Omada Identity has a steep learning curve. Due to the abundance of features, I have still been relying on Omada University for assistance even after six months of use.

I have been using Omada Identity for almost six months.

Omada Identity is stable. Any bugs we have encountered are part of the implementation issues.

I would rate the stability a nine out of ten.

Omada Identity is a cloud-based solution so it is scalable.

The technical support is the best.

Positive

Before I joined the organization they were using another solution that was old and needed to be upgraded.

I would rate Omada Identity eight out of ten.

We have several users of Omada in our organization. This includes both administrators and regular users. We currently have a small group of four administrators managing the system for approximately 20-30 users. However, we anticipate needing to grant access to Omada to a much larger group of students in the future. These students would have varying levels of access based on their needs. They would likely request access through a system like Home Holter, which would manage start and end dates for their permissions. This could potentially involve access for up to 30,000 students, teachers, and colleagues.

Monthly maintenance is required for Omada Identity.

I recommend Omada Identity to others. The solution is widespread and there are many options to choose from.

In general, we use Omada Identity for managing the lifecycle of identity access. This includes onboarding new employees and granting them access to various resources within our company, such as File Share or Ship Insight, among others. Additionally, for organizational transfers, when employees change departments or switch to a subsidiary, we rely on the old identity lifecycle management for the workforce.

Omada Identity provides a clear roadmap for deploying additional features. We maintain regular communication with Omada, engaging in daily contact. They organize various meetings, team meetings, and Omada user groups where they provide us with insights regarding their upcoming plans. 

The Roadmap helps us to get additional features into production. Omada has a user voice portal where customers can vote on different feature requests, contributing to the advancement of the roadmap. Omada listens to the customer and responds to our requests. 

Before we had Omada Identity, we had developed our own solution, which was somewhat redundant from a process standpoint. Consequently, there was a lack of connection between systems. We faced a shortage of connections and connectors to other IT systems. Omada Identity presented a significant improvement for our IT department. For instance, SAP and our HR system were not integrated with our identity access management systems at all. Therefore, every onboarding, offboarding, or organizational transfer required manual entry into both SAP or HR system and the IdentityX management system. However, with the implementation of the Omada Identity Suite and its connector, these processes now occur automatically.

Omada Identity Analytics enables us to make informed decisions more quickly than we could without it. Previously, we lacked any form of reporting. Our previous version had its own developed Identity Management system, but there was no reporting capability. In the past, we had to extract data from CSV and Excel files. Since implementing Omada Identity, we have extensively utilized the reporting and Key Performance Indicators along with the compliance dashboard to identify unapproved access. This is particularly important for access management and understanding what is happening in the background. We can now easily identify instances where there are no approvals or instances of non-compliant access permissions that have been manually granted by an administrator, bypassing the IM process. This has been tremendously helpful. Additionally, we now have the ability to provide heads of departments or team leaders with specific reports on their employees and their access permissions, which was not possible before.

The manual overhead from an IT perspective is practically nonexistent now unless we need to deploy another report. Previously, when we didn't have it at all, the IT workload perspective was at 100 percent. Currently, I would estimate it to be around five percent. However, this five percent only applies if there are questions regarding specific reports or KPIs, or if a new KPI or report needs to be defined or created. But when it comes to generating them, the workload is reduced to zero. The type of work has shifted from creating reports, KPIs, and views to the current situation, whereas before it also involved creating exports and delivering them to the department head or team leader.

Omada Identity Analytics has helped to reduce the cost of our IGA program. Every manager or project leader can generate their own report with just a click of a button, without having to wait for filing a service ticket. Instead of relying on a support person to pull the ticket, create the report, and send it back, there is now minimal back and forth to ensure the answer is appropriate for the question, thus saving time.

Omada Identity is configured to revoke an employee's access immediately upon their departure from our organization. If an employee encounters an issue during the day or engages in activities that violate company policy and are non-compliant, there is an emergency lockout procedure in place to swiftly restrict access to their account.

We frequently utilize Omada certification surveys to certify positions and ascertain their relevance to our audit requirements, such as ISO or TFAX, as well as when an employee undergoes a role or department change.

The recertification is primarily based on resource levels. There are only a few roles assigned by HR. For example, if the head of a department has specific access to certain resources such as mailing lists or SharePoint sites. However, if they lose this title, they will automatically lose these permissions or access. This is the only aspect related to roles. Everything else is based on explicit resource permissions. Therefore, it requires explicit requests and approvals, and it also needs to be explicitly recertified. 

Omada Identity helps us maintain compliance and security. We no longer encounter the classic scenario where a student or someone moves between departments, collecting permissions from each department along the way. As a result, we don't end up with the most powerful employee in the company. This is because every time someone changes departments, a recertification process is initiated to verify if their access is still appropriate for their current or future role. Additionally, this system helps us identify obsolete resources. We can now see resources that have been inaccessible to individuals for months. This enables us to reach out to the resource owner and inquire if it is still necessary to maintain access to a particular File Share or SharePoint site, given that nobody has accessed it for the past three months or so.

Omada Identity helps save time on provisioning access for identities. Because we have a better ability to utilize connectors, such as those for SAP or Azure Active Directory, we have been able to connect an increasing number of systems over the past two and a half years. This is a significant improvement compared to our previous capabilities thanks to the ability to set up connectors. I understand that this improvement is not unique to Omada, but it has greatly enhanced our operations compared to what we had before. The process of connecting, provisioning, and de-provisioning is all automated.

Omada Identity is more sophisticated than the previous version, so we transferred the access request reviews to Omada. As a result, we now have the ability to incorporate more approval steps for medium-level permissions. This process is automated through the workflow. While we had this capability before, it doesn't represent a significant gain for us. The only advantage we have now is the inclusion of multiple improvement steps that were previously absent. For instance, the head of a department and someone from the finance team can both provide oversight since this involves financial reporting and control. Additionally, these steps must be approved by someone from the controlling or finance department.

The most valuable feature for us is the ability to set up connectors to various IT systems and offer a wide range of supported connectors. These predefined connectors include ones for SAP or Azure Active Directory. Moreover, if these are insufficient, we have the option to create our own connectors by scripting using different script languages.

The web GUI can be improved. 

I have been using Omada Identity for two and a half years.

The technical support team has specific response times. Additionally, we have an Omada consultant present on our site every day. In case the discussion with the support team veers off track, the consultant steps in to redirect it. Moreover, they have access to internal information and can communicate with the support team internally. Having these on-site consultants gives us an advantage, as we are not solely dependent on tech support.

Neutral

We switched from our previous solution because we wanted to eliminate the platform. Our previous solution was driven by IBM Lotus Notes, and we had a significant project years ago when we transitioned from IBM. At that time, we moved from IBM Lotus Notes, which included email, shared collaboration, and identity access management, to Outlook, Skype Teams, and SharePoint. The decision to move away from the IBM Lotus Notes platform was primarily driven by the need for a different platform. 

Due to our prior experience with the system, which had thousands of users and resources, the migration process was relatively straightforward for us. Since it was not related to the grid field, we had all our necessary resources. We had to migrate both our system and our processes, including company policies for onboarding employees and the necessary steps that should occur, such as setting up an executive account. Overall, the migration process was relatively straightforward due to our existing processes and the commitment of our management.

I give Omada Identity an eight out of ten.

The user-facing web front end has some confusing features. For instance, while the website is loading, it does not block user input. This means we can type while the website is loading, but everything we typed is lost once the loading is finished. So, to simplify, both the web front end and the user-facing interface need improvement. Omada is aware of this and acknowledges it. Although it may not be openly discussed, the people behind the product are dedicated to making it better. It's actually a compliment that the people are more impressive than the product itself, and it should always be this way. They are actively working on addressing the issues and we have seen some improvements over the years. In the last couple of months, they introduced a new user interface, but there is still room for further enhancement.

We use Omada Identity for role-based access control when the roles are coming from HR, the head of a department, the project manager, and a few others. These are the only roles we currently have and use. However, I wouldn't blame Omada for this. It is because our organization has not yet defined these company roles. Currently, we are in the process of identifying the first responders within the company. These roles include IT service desk agents and similar positions, but they are still being developed from the company side. Once that is completed, we will discuss it with Omada and, in fact, we have already begun the setup process in Identity Suite over the past few weeks. But for now, it is mainly driven by HR.

We have centralized IdentityX management for the entire organization. This was the case before the introduction of Omada Identity, and it continues to be the case with Omada Identity. There are certain situations, particularly those involving high confidentiality and secure financing matters, where we do not use Omada for provisioning and de-provisioning. For instance, we do not utilize it for high-privileged domain administrative accounts. The reason for this is that if we were to do so, the consultants working with us on a daily basis would have implicit full permissions to our critical systems. Hence, we have imposed an access level limit. In cases where we do not fully integrate Omada Identity, we manually set and provide the highest level of permissions, in line with company policy.

For training reasons, we were unable to keep pace with the accelerated development in the warehouse. We lacked the necessary system connectors, and HR was handling onboarding in the HR system and our IAM solution. Developing an HR connector internally proved to be beyond our capabilities, as it falls outside our core competence in the current business cases. Therefore, this becomes an additional reason for considering the Omada Identity platform.

The comprehensiveness of Omada's out-of-the-box connectors for the applications we use is, for the most part, satisfactory. They generally perform their intended functions effectively. If we have specific requirements, they accommodate them by allowing us to input our username, password, or tenant ID for Azure Active Directory. They continue to fulfill their designated tasks without issues. Therefore, there are no complaints about this aspect. However, if we have additional requirements, we may need to make adjustments accordingly. Nevertheless, for the most part, we can configure everything within the web portal without resorting to complex modifications in files or the database.

The primary use cases are identity lifecycle, provisioning, and authorizations to our IT infrastructure. We use it for provisioning to our SAP platform. We also need it to make a survey of the IT authorizations. We need to make sure that our managers can review the authorizations of the employees in our company. 

We have a couple of secondary use cases as well, such as segregation of duties on provisionings to make sure that we have correct approval flows for authorizations. 

The automatic provisioning of a lot of authorizations has definitely lightened the load on the manual part of authorization management. It has not directly caused savings in our operations, but our administrators have seen a dip in the number of manual tasks they had to do. So, that's a direct business value for us from the platform.

It has helped in reducing the number of helpdesk tickets and requests by at least 30%.

The identity lifecycle support is definitely valuable because we are a complex organization, and there is a lot of onboarding, movement, and offboarding in our organization. We have 31,000 users, and there are a lot of users who are constantly onboarding, offboarding, and moving. So, we need to make sure that these activities are supported. In old times, we used to do everything manually. Everyone was onboarded, offboarded, or moved manually. So, from a business point of view and an economics point of view, identity lifecycle is most valuable. From a security point of view, access review is the most important feature for us.

Our internal customers are quite happy with the product, and we receive a lot of positive feedback. Its identity-governance and administration features are very broad. It can support a lot of use cases. I don't think we use a broad part of the product, but it is a very broad platform that can be used for a lot of different things.

It provides a lot of flexibility for our security operations. We can combine the security operations of the product with other security operations, such as logging, surveillance of our infrastructures, and things like that. I sit in the security office primarily, and identity governance is a part of our operations in security. So, it provides a lot of flexibility for a lot of different use cases.

Error handling can be improved. From an on-premise perspective, internal support can be improved. It is quite a technical and difficult application to maintain. A very specialized skill set is required to operate and maintain it, which is the most difficult part. The process to upgrade versions is also quite tricky.

One thing that we are not so happy about is the user interface. It is a bit dated. I know that they are working on that, but the user interface is quite dated. Currently, it is a little bit difficult to customize the user interface to the need of the business, which is a little bit disappointing. It needs it to be a little bit easier to operate, and it should have a better user interface.

Their technical support is good, but there is room for improvement. It is not an easy product to support. They helped us set it up a little bit, but it gets difficult for them to handle more complex problems.

I have been using this solution for the last year.

The product itself is quite stable. The problem is that it is quite complex with all the integrations, which is applicable to all IGA solutions. There is a lot of need for surveillance on the solution itself, but it is not because of the solution itself. It is because of all the integrations. So, the solution itself is quite stable, but the integrations make it quite vulnerable to all kinds of stuff.

It seems quite scalable in terms of performance and in terms of the ability to scale itself.

Their technical support is good, but there is room for improvement. One problem that we have discussed with Omada several times is their handling of a customer-specific problem and a solution-specific problem. The coordination between their technical support and their backend developers can be better. It becomes an issue when a problem is more complex. It is not an easy product to support. They helped us set it up a little bit, but it gets difficult for them to handle more complex problems.

It was an internally developed solution. We switched to Omada because our previous solution didn't support governance. It was only for ordering new authorizations, and the level of automation was limited.

It was a complex process in terms of technicality and the amount of effort needed for setting it up from Omada's point of view.

We started in August 2018, and we finally deployed the solution and were ready for production in June 2020. So, it took 18 months.

We had to deploy or onboard a part of our infrastructure at once. We onboarded a couple of applications and our SAP solution on day one. Omada would probably call it the big bang, but it was definitely not the big bang. We deployed a lot of functionalities at once, but it was a very limited part of our total application portfolio that we deployed with Omada. It is not yet done. The first one and a half or two years will go into implementing the rest of our application portfolio in the solution.

We used Omada itself as an implementation partner. The consultants themselves were quite adept at handling the product. From a technical standpoint, they were definitely above average. From a project management point of view, we would have liked to see some improvements. This is from the perspective of a very large customer. The problem for us was handling an organization of our size. If I have to choose again, instead of Omada, I would choose an implementation partner who is more used to handling large enterprises. That was definitely a pain point for us.

It is quite a technical and difficult application to maintain. It is a standard solution, but some parts of the solution make it difficult to upgrade and maintain the solution. A very specialized skill set is required to operate and maintain it. You should either pay Omada or another consultancy firm to maintain the solution, or you should have internal resources for maintaining the solution. 

We have around 10 people who are directly involved in its maintenance. They are on the business side, such as for onboarding new applications, front-end problem-solving, and incident-handling, as well as on the operations side, such as for ensuring data validation, handling integrations, and things like that. 

It is very difficult to say at this point. We are a municipal organization, and we do not, as such, do a very systematic review on the return on investment. I would say we have seen a positive ROI, but I'm not sure.

It is also very difficult to say whether it has reduced the total cost of ownership. My gut feeling is that it has, but we have not made a precise estimate of what economic impact it has had on us.

Our business is regulated and subject to audit fines, but again, it is too difficult to estimate whether it has reduced the number of audit fines we have received. It is too early to estimate that, but I would guess it has.

From an on-prem point of view, the cost is quite transparent and reasonable. The direct cost is primarily for licenses and maintenance on licenses.

We evaluated other solutions. I don't remember them all. We did a market analysis where we considered SailPoint. We definitely reached out to Microsoft as well but not for their identity solution as such. We reached out to them for their future solutions in this environment.

We only did a market analysis. Being in the public sector, we have a very strictly EU-regulated process for procurement. So, it is quite difficult to do a look-and-feel kind of selection of tools.

I was not directly involved in the market analysis. As far as I know, our tender showed that from a technical standpoint, all evaluated solutions were comparable in functions and features for our intent and purpose. They were not identical, but they were comparable in functions and features.

Any business interested in using this product needs to make sure that they are ready to either pay Omada or another consultancy firm to maintain the solution, or they should have the internal resources for maintaining the solution. It is quite a difficult solution in terms of maintenance.

It is very important to make sure that the master data is correct and is controlled by processes rather than humans. This is very important. We thought that we had a very good understanding of our master data, and it was mostly supported by processes and not by people, but we certainly were caught a bit by some of the things. So, having control over your master data is the most important thing. 

If you are a reasonable-sized organization, you should be very careful and make sure that the implementation partner has the correct implementation model that suits your need. You need to make sure that you have the correct support, or the means to find the correct support, for the application itself when you go live. These are definitely the three most important things.

I would rate Omada Identity a seven out of 10. There is definitely room for improvement, but it is not a bad product. It is a good product, and seven, in my book, is for a good product. 

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.