Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Multiple Business Accounts Logged in (one) 1Password.app
We have a small support team, including a primary admin who needs 100% access to the supported 1Password business accounts. Many devices (iPhones, Macs, iPads, Androids) are work/personal blended with applied business/personal separation. In our case, our team uses 1Password for Business for support, but also logs into personal accounts with the same 1Password app on the same devices. When navigating Business support, the autofill/access displays user/passwords for ALL Business accounts logged into 1Password.app. Is there a streamlined way to dedicate specific access when on the Business side versus the personal side? When logging into Netflix (personally), I don't want to have to scroll through a list of client logins to find mine. We have tried using "Collections" with limited success, if any.
2 entries same password
Hi, is there a solution for the following scenario: i have a Windows Account and an EntraID Account that are fully synced in the background. So i have 2 entries with the same Password. Is there a way to sync this entries somehow so that i need only to change the password at 1 single point in a 1Password entry? Is this maybe a possible New Feature for 1Password? BR ThomasWhat’s new in 1Password Enterprise Password Manager (Q4 2025)
Hey everyone! 👋 We’ve been working closely with customers across industries this past year to understand where they need more flexibility, clarity, and control. That feedback shaped a new round of improvements that help teams deploy faster, manage more consistently, and stay secure without slowing anyone down. Here’s a quick rundown of what’s new: Security without friction New App Unlock presets give admins more flexibility in how people unlock 1Password. Organizations can align unlock behavior with their existing device policies, like allowing 1Password to unlock when the device unlocks while still enforcing auto-lock where needed. Teams can decide which presets are available, override them where required, or let users choose the option that fits their workflow. Vaults remain protected by device-level encryption – this simply changes when 1Password unlocks, not how it’s secured. Get teams set up in less time A couple of updates make it easier for new users to get started confidently: The new Browser Extension policy helps guide new users to install the 1Password browser extension during setup. Guided Setup now introduces people to the essentials of using 1Password in their environment and adapts to each organization’s configuration. Together, these reduce confusion during onboarding, minimize IT overhead, and help people start saving and filling credentials right away. New policies provide more control As organizations scale, admins often need fine-grained control over how credentials are saved and submitted. New policy options now allow admins to configure: Autosave: Choose which item types (Logins, Credit Cards, Addresses, 2FA) are saved automatically. Autosubmit: Turn off automatic form submission. Sign-in Attempts: Define how many failed login attempts are allowed before an IP address is temporarily locked for that user, helping safeguard against brute-force attacks. These updates help standardize behavior across the organization while still giving teams the right amount of flexibility. Set up your 1Password instance to reflect how your organization operates Multi-tenancy introduces a new account model designed for scale that brings more clarity and consistency to large or distributed organizations. Linked Accounts let you connect a parent account to any number of child accounts within the same data region, organized by geography, department, or business unit. Policy Templates make governance easier by letting the parent account create reusable templates, decide what child accounts can override, and apply standards instantly. It’s a flexible way to maintain consistent security while letting teams operate independently when they need to. Coming in 2026 A couple of updates already in motion: Automated Provisioning hosted by 1Password connects directly to Okta and Entra ID, eliminating the need for self-hosted SCIM bridges so teams can deploy faster with less infrastructure to maintain. A redesigned Audit Log that brings all user and admin activity into a unified, human-readable view, making investigations and compliance reviews much easier. These improvements are all steps toward making enterprise deployment smoother, governance clearer, and day-to-day work less of a lift for admins and teams alike. If you’d like a closer look (including screenshots and examples) you can find the full breakdown in our latest blog post.
SHaring a password securely with a team member VA
Hi, I have recently joined a business community, and they mentioned that they share a one off password generated in their password manager each time for their VA - I am considering getting a VA. What is the best way to manage a password when bringing on a team. I am one of your original customers in 1 password 5 so not on a plan, I paid one off for the app. It's been great! Rebecca
Failed login attempts
Hello, it appears that one may hack away at 1Password logins w/o concern for the number of failures. Is this true: if not, where may I find doc regarding such? The admin "Sign-In Attempts" report is eye-candy and of limited practical use. The Activity Log has a "Login Attempts Exceeded" option, but the value of the count is no where to be found. For a serious enterprise offering, the following should be available: 1. Account lockout after organization specified number of failures. 2. Alert mechanism to inform owners or admins of high number of login attempts (or at least the lockout occurred.) 3. A easy-to-find report showing suspicious activity. Please let me know I'm mis-informed on these items.
How do I transitioning from 1:1 mapping of authentication to authorization to simpler options?
I have never taken the following suggestion: In this example, let's say I work for Consult-o-rama, and the account referred to is Microsoft here is a login called Consult-o-Rama in my Consult-o-Rama vault dedicated to all things Consult-o-Rama. (I'm an employee of Consult-o-rama) the Sharepoint referred to here, then, is a SharePoint of a company which was a joint venture 30 years ago and with whom we have a close relationship. They have their own AD, but federatio nis such that we are allowed to log into their sites separately using our same login. Likewise we can switch orgs in Teams and use their separate teams with the same credentials. Sites appear in this login record in 1Password so that this credential can autopopulate on any sites i've put into the sites fields there. Other background: I have 4+ vaults. consult-o-rama, client 1, Client 2, Persional, and then Client <#> for however many clients I need to have them for. I use separate browser identities and have the vaults in the plugin filtering only on the relevant vaults. the login credential record "Consult-o-Rama' is one of 5-10 microsoft account. I log into at least that many SharePoints None of my login credential records are named Microsoft or SharePoint. How can I best use the funtcionality I'm being prompted to use without: Creating duplicate records of login credentials. Being clear about mapping identities an being able ot lble "Microsoft" in this example instead as "Consult o Rama', and "SharePoint" instead as "consult-o-rama" SharePoint. So that in the future I can map 1 to many and many to 1 logically and without confusion? Thanks!,Upcoming 1Password webinars
Hi folks, Just a heads up that in addition to tomorrow's fireside chat, Ask the experts: Navigating the security risks of AI agents, we have two other webinars coming up that you won't want to miss: Small IT teams, big risks: How to build credential security that scales Date: Tuesday, November 11th Time: 9 AM PST / 12 PM EST Credential-based attacks remain the #1 cause of breaches, and SMBs are still the most frequent targets. With small teams and limited budgets, how can you gain visibility, control, and protection across every sign-in and app your employees use? How Reddit scales secure access with 1Password Date: Wednesday, November 12th Time: 9:30 AM PST / 12:30 PM EST Passwords are the #1 cause of security breaches, and many companies struggle with decentralized credential management and painful onboarding/offboarding processes. Reddit was no different. Weak passwords, shadow IT, and manual access management were straining IT teams and creating hidden security gaps. They needed a solution that reduced credential risk without slowing down their employees. Join us as Reddit’s Sr. Manager of Enterprise Security & Systems, Nick Fohs, shares the inside story of how his team solved these challenges by adopting 1Password. You’ll get a first-hand look at the problems they faced, why they chose 1Password, and the impact it’s had on both security and efficiency.
