Omada Identity Primary Use Case
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.View full review »
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.View full review »
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.View full review »
Functional Administrator at Gemeente Utrecht
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.View full review »
IT Security Architect at CARL IT Solutions GmbH
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.View full review »
Chief Security Strategist at Clango
Everything is related to identity governance, such as
- Joiner, Mover, and Leaver (JML) use cases
- Access request for use cases
- Provisioning use cases
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.View full review »
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.View full review »
IAM Senior Consultant at a computer software company with 10,001+ employees
I've been working on a big project for a public sector in Sweden. We permission the identities coming from the HR system to go to the active directory.View full review »
Identity and Access Program Owner at a government with 10,001+ employees
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.View full review »
IAM Consultant at a computer software company with 10,001+ employees
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.