What is our primary use case?
My main use case for OneLogin is for identity management.
OneLogin helps me manage employees across apps, databases, clouds, and other platforms. For example, when someone joins or changes teams or leaves, access is created, changed, and removed properly. It also helps secure admin root access to accounts.
For a more practical example regarding my main use case, suppose a developer needs temporary admin access to a production server. Instead of giving them a permanent password, OneLogin can help me approve the request, grant them access for a limited time, record the session activity, and remove them afterwards.
A couple of features that I like about OneLogin is firstly the centralized access management that helps manage my users, groups, and permissions from one place instead of handling everything from multiple locations. Secondly, there is automation for onboarding and offboarding that specifically comes in handy when employees join, change teams, or leave. Access can be provisioned or removed with workflows instead of manual IT steps. Lastly, the self-service password reset is beneficial since OneLogin allows us to reset forgotten passwords or unlock accounts ourselves, greatly reducing the help desk workload.
What is most valuable?
OneLogin has positively impacted my organization by greatly reducing the manual workload for identity management. It has also made onboarding and offboarding feel more structured, faster, and less dependent on manual IT work. Now, new users can get the right access based on their role.
The ability to provide a seamless end-user experience for signing in and authenticating to needed applications is very important because it improves both security and user productivity. Employees can access tools they need through a single consistent login experience instead of remembering multiple passwords or going through different login flows for each application.
What needs improvement?
OneLogin can be improved by making the initial setup and configuration process simpler, especially for teams like mine that are new to identity and access management. Some workflows and policy integrations felt complex during setup. Better guided onboarding, clear documentation, and more in-product demonstrations would help admins get started faster.
Some points I want to mention regarding needed improvements include a faster and simpler setup for SSO and MFA policies, a better UI for admins, more helpful error messages during integration setups, and stronger reporting and audit dashboards.
The AI capability needs to be easier for admins and teams to use and to make governance and security easier to understand and act on. The output must be reliable and explainable, accessible to both technical and non-technical admins. Since access decisions are sensitive, AI should provide recommendations and risk signals, but final decisions should take place after thorough review.
For how long have I used the solution?
I have been working in my current field for over two years now.
What do I think about the stability of the solution?
OneLogin is stable as far as my experience goes.
What do I think about the scalability of the solution?
From a pricing perspective, OneLogin is really scalable since the pricing depends on the number of users and is per seat. Adding or removing a user is not much of a hassle for us, and there is no one-time fee up front that we have to pay.
How are customer service and support?
We required some help while onboarding to OneLogin, and the customer support was greatly helpful.
I would rate the customer support a nine out of ten.
Which solution did I use previously and why did I switch?
After switching to OneLogin, I noticed a return on investment. Previously, we primarily used a manual centralized identity management approach, which worked for a while. However, as our organization kept growing, managing SSO, MFA, and user provisioning became harder. We needed a more centralized and scalable solution for authentication and access management.
We evaluated several options before choosing OneLogin, including Okta, Microsoft Entra ID and Azure AD, and JumpCloud. We chose OneLogin because it offered a strong balance of SSO and MFA, directory integrations, user provisioning, and centralized access management at a practical cost.
How was the initial setup?
My advice for others looking into using OneLogin is to plan for immediate implementation properly before rollout. It is best to start by identifying the most important applications, user groups, MFA requirements, and directory integrations. A phased rollout works better in our case than trying to move everything at once.
What was our ROI?
Previously, the process required multiple manual steps and follow-ups with the IT and admin team. With OneLogin, role-based access and approval workflows have made the process more structured, reducing our onboarding time from weeks down to days.
After switching to OneLogin, I noticed a return on investment. Previously, we primarily used a manual centralized identity management approach, which worked for a while. However, as our organization kept growing, managing SSO, MFA, and user provisioning became harder. We needed a more centralized and scalable solution for authentication and access management.
What's my experience with pricing, setup cost, and licensing?
Regarding my experience with pricing, setup costs, and licensing, the pricing and licensing are generally based on a per-user subscription model, which makes it easier for us to scale as the organization grows. The cost depends on the plan and number of users. Feature requirements such as SSO, MFA, and advanced directory integrations are all included or mostly add-ons that can be managed easily.
What other advice do I have?
The AI capabilities that OneLogin offers can be useful in identity and governance. It can provide strong value in governance security by detecting risky access and unusual login behavior, finding patterns in data for large organizations. Additionally, it can prioritize access reviews and suggest least privileged improvements. However, AI decisions should be explainable and reviewed by admins, especially for sensitive security actions.
I feel that switching to OneLogin is a good move for us in terms of centralized access and identity management, and since we have transitioned to OneLogin, it has greatly reduced our manual work and offloaded much of our IT tasks. I would rate this product an eight out of ten overall.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Disclosure: My company does not have a business relationship with this vendor other than being a customer.