Chief Information Security Officer at a manufacturing company with 5,001-10,000 employees
Real User
Dec 22, 2022
We wanted a solution that could help us make HR the master of identities. We wanted a solution that could take that data and direct it into all our other directories and Active Directory.
Companies I work with use Omada Identity for compliance and governance purposes. They use the solution to have control over all of their business processes in terms of access control.
Project manager Identity & Access Management bij Fontys Hogescholen at a university with 1,001-5,000 employees
Real User
Nov 7, 2021
My primary use cases of this solution are to manage the life cycle of identities, manage authorizations for applications, and the re-certification of authorizations.
Application Consulting & Management Administrator at a computer software company with 201-500 employees
Reseller
Oct 24, 2021
Our primary use cases are around employee life cycle processes. Employees join us, extend their contracts, move around, and leave us. Omada is connected to our HR system as well as SAP, Microsoft Exchange, and Active Directory. We also use it for updating our employee master data and use the request management, covering about 900 employees. We are an Omada partner and reseller.
Solution Architect IAM at a energy/utilities company with 1,001-5,000 employees
Real User
Sep 13, 2021
Our primary use case is for the lifecycle management of employees. In addition to that, we use it to provision accounts and authorizations to target systems. We can do segregate of duties checks based on those authorizations.
As an Omada partner, we are integrating the Omada Identity Suite for our customers. Our customers primarily use it to align their identity lifecycle and access management. In some cases, they also use the integrated workflow engine that Omada has to migrate existing paper-based workflows to a digital platform.
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.
We are using it for rights and roles of our users. When we hire a new employee in our municipality, we have their information exported to Omada and, based on which department they are hired for, they will get roles and rights for the IT systems. That's what we use it for right now. We have plans to do more with it, but identity management is a life-long task to enjoy. The solution is on-premises.
We are provisioning new accounts. We are deprovisioning accounts that are gone. In Omada Identity, you can connect transfers (external employees who came to work for us) very easily. We have had trouble doing this with a new front-end system, not Omada Identity, where accounts are not connected. With Omada Identity, I can connect accounts and change everything that I have to do. We can manage access for everyone, including suppliers, partners, and maintenance staff. Now, in Active Directory, there is accountability for everyone. If someone is responsible for an account, we can see who is responsible. We use the main portal of Omada Identity. We are not using the solution fully, but we are getting there slowly.
I used it in my previous company for identity governance or identity administration. We used it for tracking who had access to the data warehouse and for workflows for requesting approval for access. We also had access verification to ensure that the right person had access. We were using its latest version, and we were upgrading it regularly.
Everything is related to identity governance, such as * Certification * Joiner, Mover, and Leaver (JML) use cases * Access request for use cases * Provisioning use cases * Workflow. In a fully implemented Omada Identity solution, all these use cases are equally important. We have on-prem Omada customers, then we also have the Omada SaaS customers. We always work with the latest version of this solution.
IAM Consultant at a computer software company with 10,001+ employees
Real User
Mar 25, 2020
Our general use cases include: * User onboarding * User out-boarding * Role-based access control, e.g., whenever a person's role is changed from one to another, then all the related roles need to be changed. * Role management * Asset management * Re-certification, audits that happen every quarter. Every quarter a manager has to certify all his subordinates' access, whether that expertise should be gained or not, or whether they'll be skipped.
Omada Identity is an identity governance and administration (IGA) solution designed to help organizations manage and secure digital identities and access across their IT environments. It focuses on enhancing security, compliance, and efficiency by automating identity management processes.
Omada Identity offers a robust set of features that streamline identity lifecycle management, access governance, and compliance reporting. It integrates with a wide range of IT systems, applications, and...
We wanted a solution that could help us make HR the master of identities. We wanted a solution that could take that data and direct it into all our other directories and Active Directory.
Companies I work with use Omada Identity for compliance and governance purposes. They use the solution to have control over all of their business processes in terms of access control.
My primary use cases of this solution are to manage the life cycle of identities, manage authorizations for applications, and the re-certification of authorizations.
Our primary use cases are around employee life cycle processes. Employees join us, extend their contracts, move around, and leave us. Omada is connected to our HR system as well as SAP, Microsoft Exchange, and Active Directory. We also use it for updating our employee master data and use the request management, covering about 900 employees. We are an Omada partner and reseller.
Our primary use case is for the lifecycle management of employees. In addition to that, we use it to provision accounts and authorizations to target systems. We can do segregate of duties checks based on those authorizations.
As an Omada partner, we are integrating the Omada Identity Suite for our customers. Our customers primarily use it to align their identity lifecycle and access management. In some cases, they also use the integrated workflow engine that Omada has to migrate existing paper-based workflows to a digital platform.
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.
We are using it for rights and roles of our users. When we hire a new employee in our municipality, we have their information exported to Omada and, based on which department they are hired for, they will get roles and rights for the IT systems. That's what we use it for right now. We have plans to do more with it, but identity management is a life-long task to enjoy. The solution is on-premises.
We are provisioning new accounts. We are deprovisioning accounts that are gone. In Omada Identity, you can connect transfers (external employees who came to work for us) very easily. We have had trouble doing this with a new front-end system, not Omada Identity, where accounts are not connected. With Omada Identity, I can connect accounts and change everything that I have to do. We can manage access for everyone, including suppliers, partners, and maintenance staff. Now, in Active Directory, there is accountability for everyone. If someone is responsible for an account, we can see who is responsible. We use the main portal of Omada Identity. We are not using the solution fully, but we are getting there slowly.
I used it in my previous company for identity governance or identity administration. We used it for tracking who had access to the data warehouse and for workflows for requesting approval for access. We also had access verification to ensure that the right person had access. We were using its latest version, and we were upgrading it regularly.
Everything is related to identity governance, such as * Certification * Joiner, Mover, and Leaver (JML) use cases * Access request for use cases * Provisioning use cases * Workflow. In a fully implemented Omada Identity solution, all these use cases are equally important. We have on-prem Omada customers, then we also have the Omada SaaS customers. We always work with the latest version of this solution.
Our general use cases include: * User onboarding * User out-boarding * Role-based access control, e.g., whenever a person's role is changed from one to another, then all the related roles need to be changed. * Role management * Asset management * Re-certification, audits that happen every quarter. Every quarter a manager has to certify all his subordinates' access, whether that expertise should be gained or not, or whether they'll be skipped.
I have this solution at two different sites and they are completely different setups.