What is our primary use case?
My main use case for 1Password SaaS Manager is organizing all passwords in different vaults and, most importantly, sharing credentials with my teammates.
A specific example of how I use 1Password SaaS Manager to share credentials with my teammates is that I created a service account recently and needed to share it with the entire team. Rather than sending it through other means such as Slack, messages, or email, I go to the team's vault that we already have and create that credential. I share just the name of the credential with the entire team in a channel so that they can access it.
1Password SaaS Manager is mainly used for sharing credentials with the team and updating them from time to time. The only thing I think is missing is knowing who created the credentials.
What is most valuable?
The best features 1Password SaaS Manager offers include credential sharing, which is really useful, and easy access because anytime I type a password on the browser, it asks me if I want to save it on 1Password. It is very handy, and I appreciate how secure and easy it is to use.
In terms of security, I can create different vaults and give access to different people within the organization who I want to have access to the vault, so a vault becomes like a secure folder. When I save the password or credentials, it allows me to have it in a secure password format so that it appears as a dot rather than the actual password, preventing anyone from seeing it while minimizing shoulder surfing. 1Password SaaS Manager is very easy to use.
1Password SaaS Manager has positively impacted my organization because many automations depend on 1Password for authentication. They authenticate to 1Password and get the respected passwords or credentials they need, such as tokens and APIs. It is really easy to access via the codebase, so my major use case becomes automation that uses 1Password to log in and get the respective credentials.
What needs improvement?
The only thing I think is missing is knowing who created the credentials.
One major thing I think is missing from 1Password SaaS Manager is the ability to know who created credentials within a vault. I have ten teammates who create credentials, and from time to time, we have to update those credentials, but we never find out who created those passwords among the team. We currently write it down on notes, but it would be nice if we could have logs of who created or updated the passwords over the future, at least three to six months of logs within 1Password itself.
For how long have I used the solution?
I have been using 1Password SaaS Manager for more than four years and have been using it consistently for the last two years.
What do I think about the stability of the solution?
1Password SaaS Manager is very stable in my experience, and I do not have any concerns at this time.
What do I think about the scalability of the solution?
I have not looked into the scalability of 1Password SaaS Manager, but if there is one, I would like to explore it. Currently, almost everyone in the organization uses 1Password as a credential manager, but when it comes to adding more passwords, we do not have many that require scaling.
How are customer service and support?
I did not use customer support for 1Password SaaS Manager, but I believe that if others needed help, they might have reached out. I have not yet.
Which solution did I use previously and why did I switch?
I previously used LastPass and Google Password Manager before using 1Password SaaS Manager.
How was the initial setup?
We deploy 1Password SaaS Manager in a private cloud.
What about the implementation team?
I do not have the privilege to share which cloud provider we use for our private cloud deployment, but it is usually AWS or Azure.
What was our ROI?
I cannot comment on how much was invested in 1Password SaaS Manager, but I can see how it is useful because it saves a lot of time when doing automations. It has saved us time in updating passwords and accessing them easily and efficiently, but when it comes to fewer employees, that is not a metric I can use to evaluate if it was a good investment.
What's my experience with pricing, setup cost, and licensing?
I am not sure whether we purchased 1Password SaaS Manager through the AWS Marketplace, as I was not involved in that process.
Which other solutions did I evaluate?
In terms of security with 1Password SaaS Manager, I can create different vaults and give access to different people within the organization who I want to have access to the vault, so a vault becomes a secure folder. When I save the password or credentials, it allows me to have it in a secure password format so that it appears as a dot rather than the actual password, preventing anyone from seeing it while minimizing shoulder surfing. 1Password SaaS Manager is very easy to use.
What other advice do I have?
I would advise others looking into using 1Password SaaS Manager to use it because it is easy and secure. It has secure parameters where I can create a vault and share it with the team I want, and I also have an individual vault where I save my own passwords and can share them with different teams. I find the access control really nice, so if someone wants a one-stop place to save all their credentials, I recommend choosing 1Password.
I have not used 1Password SaaS Manager's governance or AI capabilities yet, but I think it would be nice to see those capabilities and if they can be used in automations.
I have not used the AI capabilities of 1Password SaaS Manager yet, so I am unable to comment on the accuracy and reliability of the output. If there is an MCP for 1Password, that would be very intriguing to explore and use.
I would rate this product an eight out of ten.