IT Manager at INTERNATIONAL SCHOOL OF STAVANGER PARENT ASSOCIATION
Real User
Top 20
Feb 26, 2026
OneLogin's use case in my organization is for the entire infrastructure because it was very outdated, not secure, and it was built Windows heavy despite us being a Mac environment. I decided to go completely cloud-based instead. I rebuilt the whole school infrastructure into being fully cloud-based and software as a service most of the time, so we don't have any on-premise infrastructure for anything. OneLogin was one tool that I compared to two other tools, and it did everything I needed to do. It made our life much easier to switch to completely cloud-based authentication and everything.
Assistant IT Manager at a tech vendor with 1,001-5,000 employees
Real User
Feb 16, 2026
My main use cases for OneLogin are vaulting and secure authorization. I use password vaulting to securely save our passwords so that we can log in without any hassle with only one click, which saves our time and keeps our passwords safe. This leads to our systems being robust without any outside attacks, making it very beneficial for us.
My main use case for OneLogin is app aggregation and SSO. I use OneLogin for app aggregation, which is utilized for a single point of access, so it is used in facilitation of SSO.My main use case fits into my team's workflow as it reduces the work, decreases the time required, and increases the flexibility of the team.
OneLogin by One Identity serves the purpose of SSO, which we used in partnership with Kaseya. I forgot the original name of the program, but we used it because it stored all of our devices and client information. This allowed us to avoid having anyone share passwords.I used SmartFactor Authentication to adjust the flow in real time depending on the risk score associated with login attempts. My phone functioned almost as a key. I appreciated the ability to get access codes, which was particularly useful when I was away from my computer and needed to access the system through the client portal using codes generated specifically for me. The integration of phishing-resistant device trust makes the authentication processes stronger and safer because of the complexity it uses. It relies solely on your data, which makes it harder for someone to hack into because it used multiple layers of authentication through one portal. With the SSO feature, it was easy to integrate with third-party authentication providers.
My main use case for OneLogin at Maya's 24 is related to general user access. I use OneLogin for user access across various applications seamlessly. My main use case revolves around enhancing security while simplifying the login experience for my team. For example, multiple tools my team relies on daily, including project management software and document collaboration tools, are accessed through OneLogin.
I have been using OneLogin for a year now for its access management capabilities and as an authenticator. We integrate with customers that want MFA, so we are mostly using OneLogin for it. For a customer who needed MFA, they wanted to integrate OneLogin as an additional way to authenticate to Safeguard for external employees. We basically integrated OneLogin as an authentication provider to Safeguard. To connect via the Safeguard SPP UI, customers would be redirected to OneLogin.
Senior System Engineer at a tech vendor with 1,001-5,000 employees
Real User
Top 20
Dec 22, 2025
My main use case for OneLogin is managing all admin tasks related to OneLogin, which includes SSO integration, mapping, and role creations. A specific example of an SSO integration is the SSO integration with the SAML or OIDC protocol with third-party and internal applications. I handle the mapping feature, which is helpful for Google Groups data syncing via mapping to OneLogin role. We manage it ourselves, allowing us to bulk upload and bulk remove users in the Google Group, including roles and access review and user reconciliation processes.
System Engineer at a government with 10,001+ employees
Real User
Top 10
Dec 19, 2025
OneLogin is our main identity and access management tool. We use Active Roles for user provisioning, which allows us to delegate the provisioning to other people. OneLogin manages user access permissions and includes creating mailboxes.
Assistant Manager at a consultancy with 1-10 employees
Real User
Dec 16, 2025
My main use case for OneLogin is enhancing system security by storing all passwords and system credentials in one place. OneLogin integrates with different tools, such as Google Workspace and other active directory systems, and I have been using it mostly for the purpose of enhancing security. For example, in enhancing security in my organization using OneLogin, I enable single sign-on, which helps me improve security. OneLogin also supports multi-factor authentication, allowing me to use a strong authenticator to improve my login credentials for other software. What I think is important about my main use case for OneLogin is that it can accommodate many integrations on a single platform, which allows me to manage all the credentials of my activities without delay or loss. It helps detect weak passwords and enhances the security system.
I have been using OneLogin for about a month, and it has been a valuable experience as I have seen it integrate with our existing system and enhance our overall security posture. One of our main use cases is streamlining user access across multiple applications, and the Single Sign-On feature has been a game-changer for us. It simplifies the login process for users, allowing them to access various applications with just one set of credentials. Additionally, we are leveraging Multi-Factor Authentication to add an extra layer of security, which has been crucial given the sensitive nature of the data we handle. Integrating OneLogin with our existing systems was an interesting process. We primarily focused on a few applications that our users access frequently, including project management tools, internal communication platforms, and customer relationship management systems.
My main use case for OneLogin revolves around application integration and user authentication. I primarily utilize it to implement Single Sign-On across internal and external applications, which significantly simplifies the login process for users. I use OneLogin for Single Sign-On with an internal project management tool that our team uses alongside a customer relationship management CRM system. Before integrating OneLogin, users had to remember separate login credentials for each application, which was a hassle and often led to frustration. The process has become much smoother with login pages, authentication, and access granted.
My main use case for OneLogin by One Identity involves single sign-on, multifactor authorization, and role-based access. For example, we have an email platform called DID Mail where we use single sign-on from OneLogin by One Identity to authenticate our users and use that same authentication on our different platforms such as virtual info and different mail platforms. The important thing we use about OneLogin by One Identity is role-based access, where our employees sign up and can see a different interface on the same platform according to their roles.
We use OneLogin to log in to all our different systems. This means I only need to go to the OneLogin portal to access all my frequently used applications, like our CRM, Greenhouse for recruiting, Jira for ticketing, Workday for HR, Tableau for data visualization, and even Slack. It's a one-stop shop for everything I need!
Our goal was to eliminate our on-site Active Directory and legacy Windows infrastructure since we operate solely on Macs. We considered two options: one that precisely aligned with our needs, and another that functioned more like a public solution. Ultimately, I chose OneLogin due to its enterprise-grade features and the professionalism of its representatives. It provided a seamless transition to the cloud, consolidating all our access needs onto a single platform.
IT Director at Florida State College at Jacksonivlle
Real User
Jan 10, 2023
We use OneLogin for single sign-on to provide a consistent user experience with our in-house and external third-party applications. In addition to single sign-on, we use two additional modules: two-factor authentication and self-service password reset. It's a SaaS product.
Manager, Information Technology at a hospitality company with 51-200 employees
Real User
Jun 29, 2022
We use this solution predominantly as our authentication provider for most or all SAML single sign-on services. We also use it as a tool to share passwords between users that need to have a centralized password database. They are the authentication provider but we use it for multifactor authentication as well. The service we use is where the users are on-premise with the network, then they bypass any single sign-on features. It just logs in. We have six locations that are all connected by WAN VPN tunnels. Active Directory is being used to replicate the user accounts, and that replicates up to both Mircosoft, which is our primary single sign-on solution, and then to OneLogin. We use Microsoft for email, SharePoint, etc., and we use OneLogin as the authentication provider currently for that.
Director of IT at a venture capital & private equity firm with 11-50 employees
Real User
Jun 22, 2022
We use it primarily as an identity provider. Beyond that, we use the SSO and SAML components. Additionally, we utilize their SmartFactor Authentication to prevent dictionary attacks. This is an additional security measure.
Control System Cybersecurity Analyst at a energy/utilities company with 201-500 employees
Real User
Jan 12, 2022
The solution is a single sign-on for a control systems integrator startup that I was the systems administrator for. We linked it with several other applications just to give our employees a one-stop-shop portal to get to all of the other applications they needed to use, based on their role within the company and who needed access to what.
Team Manager at a tech services company with 51-200 employees
Real User
Feb 6, 2020
Currently, we use the solution for identity management. We wanted to have our own identity management on-premises as we did not want to use any third-party cloud solutions.
OneLogin offers organizations a user-friendly platform for single sign-on, multifactor authentication, and seamless access management. It enhances security and streamlines processes, making it vital for application management.Designed for ease of integration, OneLogin helps organizations efficiently manage access and improve cybersecurity through centralized application management. It simplifies onboarding and offboarding, enhancing remote work capabilities and offering robust user mapping....
OneLogin's use case in my organization is for the entire infrastructure because it was very outdated, not secure, and it was built Windows heavy despite us being a Mac environment. I decided to go completely cloud-based instead. I rebuilt the whole school infrastructure into being fully cloud-based and software as a service most of the time, so we don't have any on-premise infrastructure for anything. OneLogin was one tool that I compared to two other tools, and it did everything I needed to do. It made our life much easier to switch to completely cloud-based authentication and everything.
My main use cases for OneLogin are vaulting and secure authorization. I use password vaulting to securely save our passwords so that we can log in without any hassle with only one click, which saves our time and keeps our passwords safe. This leads to our systems being robust without any outside attacks, making it very beneficial for us.
My main use case for OneLogin is app aggregation and SSO. I use OneLogin for app aggregation, which is utilized for a single point of access, so it is used in facilitation of SSO.My main use case fits into my team's workflow as it reduces the work, decreases the time required, and increases the flexibility of the team.
OneLogin by One Identity serves the purpose of SSO, which we used in partnership with Kaseya. I forgot the original name of the program, but we used it because it stored all of our devices and client information. This allowed us to avoid having anyone share passwords.I used SmartFactor Authentication to adjust the flow in real time depending on the risk score associated with login attempts. My phone functioned almost as a key. I appreciated the ability to get access codes, which was particularly useful when I was away from my computer and needed to access the system through the client portal using codes generated specifically for me. The integration of phishing-resistant device trust makes the authentication processes stronger and safer because of the complexity it uses. It relies solely on your data, which makes it harder for someone to hack into because it used multiple layers of authentication through one portal. With the SSO feature, it was easy to integrate with third-party authentication providers.
My main use case for OneLogin at Maya's 24 is related to general user access. I use OneLogin for user access across various applications seamlessly. My main use case revolves around enhancing security while simplifying the login experience for my team. For example, multiple tools my team relies on daily, including project management software and document collaboration tools, are accessed through OneLogin.
I have been using OneLogin for a year now for its access management capabilities and as an authenticator. We integrate with customers that want MFA, so we are mostly using OneLogin for it. For a customer who needed MFA, they wanted to integrate OneLogin as an additional way to authenticate to Safeguard for external employees. We basically integrated OneLogin as an authentication provider to Safeguard. To connect via the Safeguard SPP UI, customers would be redirected to OneLogin.
My main use case for OneLogin is managing all admin tasks related to OneLogin, which includes SSO integration, mapping, and role creations. A specific example of an SSO integration is the SSO integration with the SAML or OIDC protocol with third-party and internal applications. I handle the mapping feature, which is helpful for Google Groups data syncing via mapping to OneLogin role. We manage it ourselves, allowing us to bulk upload and bulk remove users in the Google Group, including roles and access review and user reconciliation processes.
OneLogin is our main identity and access management tool. We use Active Roles for user provisioning, which allows us to delegate the provisioning to other people. OneLogin manages user access permissions and includes creating mailboxes.
My main use case for OneLogin is enhancing system security by storing all passwords and system credentials in one place. OneLogin integrates with different tools, such as Google Workspace and other active directory systems, and I have been using it mostly for the purpose of enhancing security. For example, in enhancing security in my organization using OneLogin, I enable single sign-on, which helps me improve security. OneLogin also supports multi-factor authentication, allowing me to use a strong authenticator to improve my login credentials for other software. What I think is important about my main use case for OneLogin is that it can accommodate many integrations on a single platform, which allows me to manage all the credentials of my activities without delay or loss. It helps detect weak passwords and enhances the security system.
I have been using OneLogin for about a month, and it has been a valuable experience as I have seen it integrate with our existing system and enhance our overall security posture. One of our main use cases is streamlining user access across multiple applications, and the Single Sign-On feature has been a game-changer for us. It simplifies the login process for users, allowing them to access various applications with just one set of credentials. Additionally, we are leveraging Multi-Factor Authentication to add an extra layer of security, which has been crucial given the sensitive nature of the data we handle. Integrating OneLogin with our existing systems was an interesting process. We primarily focused on a few applications that our users access frequently, including project management tools, internal communication platforms, and customer relationship management systems.
My main use case for OneLogin revolves around application integration and user authentication. I primarily utilize it to implement Single Sign-On across internal and external applications, which significantly simplifies the login process for users. I use OneLogin for Single Sign-On with an internal project management tool that our team uses alongside a customer relationship management CRM system. Before integrating OneLogin, users had to remember separate login credentials for each application, which was a hassle and often led to frustration. The process has become much smoother with login pages, authentication, and access granted.
My main use case for OneLogin by One Identity involves single sign-on, multifactor authorization, and role-based access. For example, we have an email platform called DID Mail where we use single sign-on from OneLogin by One Identity to authenticate our users and use that same authentication on our different platforms such as virtual info and different mail platforms. The important thing we use about OneLogin by One Identity is role-based access, where our employees sign up and can see a different interface on the same platform according to their roles.
We use OneLogin by One Identity to provide SAML authentication and single sign-on for all of our SaaS apps.
We use OneLogin to log in to all our different systems. This means I only need to go to the OneLogin portal to access all my frequently used applications, like our CRM, Greenhouse for recruiting, Jira for ticketing, Workday for HR, Tableau for data visualization, and even Slack. It's a one-stop shop for everything I need!
We used single sign-on, multifactor authentication, lifecycle management, and connectors.
Our goal was to eliminate our on-site Active Directory and legacy Windows infrastructure since we operate solely on Macs. We considered two options: one that precisely aligned with our needs, and another that functioned more like a public solution. Ultimately, I chose OneLogin due to its enterprise-grade features and the professionalism of its representatives. It provided a seamless transition to the cloud, consolidating all our access needs onto a single platform.
We use OneLogin for single sign-on to provide a consistent user experience with our in-house and external third-party applications. In addition to single sign-on, we use two additional modules: two-factor authentication and self-service password reset. It's a SaaS product.
We use this solution predominantly as our authentication provider for most or all SAML single sign-on services. We also use it as a tool to share passwords between users that need to have a centralized password database. They are the authentication provider but we use it for multifactor authentication as well. The service we use is where the users are on-premise with the network, then they bypass any single sign-on features. It just logs in. We have six locations that are all connected by WAN VPN tunnels. Active Directory is being used to replicate the user accounts, and that replicates up to both Mircosoft, which is our primary single sign-on solution, and then to OneLogin. We use Microsoft for email, SharePoint, etc., and we use OneLogin as the authentication provider currently for that.
We primarily use Onelogin for SSO, but have been using the service for device trust as well.
We use it primarily as an identity provider. Beyond that, we use the SSO and SAML components. Additionally, we utilize their SmartFactor Authentication to prevent dictionary attacks. This is an additional security measure.
The solution is a single sign-on for a control systems integrator startup that I was the systems administrator for. We linked it with several other applications just to give our employees a one-stop-shop portal to get to all of the other applications they needed to use, based on their role within the company and who needed access to what.
Currently, we use the solution for identity management. We wanted to have our own identity management on-premises as we did not want to use any third-party cloud solutions.
Our use case is to connect the users to the IDE and other endpoints. That is the basic use case that we have for OneLogin.