It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Change the width of the suggestion popup in a browser
Hi there, Is there a way to change the width of the suggestion popup in a browser when you want to login? We have a lot of passwords for all the sites we've build, and for maintainability we like to name each entry with something like [customername] - [optional websitename] - [logintype]. So it's pretty common to have an item named something like "MyCompany - Webshop - Editor" or "MyCompany - Webshop - Testuser". The problem we're facing is the popup with the login suggestions in the browser. Due to its limited width, we only see "My Company - Webshop...". And have no clue (other than maybe the e-mailaddress) which account is which. Is there a way to increase the width? To force it so show the full name?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.
Feature Request: Rename Employee Vault in 1Password Business
Hello 1Password Team, I’m writing on behalf of our organization, which uses 1Password Business. We find the default “Employee” vault name misleading for individual use, as many mistakenly assume it contains passwords for all employees. This confusion is even greater in the German translation where it appears as “Angestellte” making it unclear that this vault is for personal credentials. It would be far more intuitive if this built‑in vault could either be renamed freely or, at minimum, default to “Personal” as it does in Family and Individual plans. Proposed Improvement Clearer Naming: Changing “Employee” to “Personal” (or allowing custom names) eliminates ambiguity, especially in non‑English locales. Consistency: All other vaults in Business plans can be renamed; extending this to the default vault aligns with current functionality. Improved Usability: Allowing organizations to set a meaningful name (e.g., “Personal,” “Private,” “My Vault”) streamlines onboarding and vault management. References: Reddit: https://www.reddit.com/r/1Password/comments/ukj3rr/why_cant_i_change_the_name_of_the_personal_vault/ 1Password Community: Can’t Re‑Name my Vault 1Password Support: https://support.1password.com/create-share-vaults/ – “The built‑in Personal, Private, or Employee vault can’t be renamed or deleted.” 1Password Community: Any way to rename a vault in 1P8? 1Password Community: Renamed vault, can’t rename back 1Password Community: https://1password.community/discussions/1password/how-to-rename-main-vault/132742Password entropy
I would like to see the password entropy when creating a password. For example, What is the strength of this? Consider this article: https://blog.syss.com/posts/passphrases/ It would be very helpful to have some confidence of the strength. Note this password generator doesn't provide any sort of length information. While the specific length may reveal too much information, if this could at least provide a some idea what the entropy is, its better than nothing. Even the character count of the generated password is good feedback. As it is, this feature is designed for novice users and doesn't provide significant confidence when looking for fitting in with technical requirements. Finally, this random password: was generated by 1Password. Rather than simply putting "Weak", given that the generation specs were known, it would be really helpful to include the entropy alongside of this. How "weak" is "weak"? Thank you for the consideration.
Include deleted vaults name in activity log entry
Currently the activity log entry for deleting a vault only records who deleted it and when they deleted it, but doesn't include the name of the vault which was deleted. Based on the CSV download I'm guessing this is currently not available as it only records the vault's UUID and since it's now deleted it the UUID can't be used to look up the name.
[Feature request] Planned suspension of user accounts
In many corporate environments, security and compliance policies require that when an employee or collaborator leaves the company, their access to critical systems is revoked immediately, typically on the same day or the next. Given how sensitive the data stored in 1Password can be, it’s essential to be able to enforce timely account deactivation. Feature request: Allow administrators to schedule a future suspension date for user accounts. When this date arrives, the account should be automatically suspended, and all active sessions (including on native apps and browser extensions) should be invalidated (ideally even if the user is offline at that time). While SSO integration can centralize user lifecycle management, it’s a relatively heavy setup for many organizations. A built-in scheduled suspension feature would help teams that rely on manual user management achieve better compliance and security without the overhead of SSO.Password Generator Options could do with some "Advanced Options"
My company works with a lot of compliance demands from SWIFT, PCI, etc. and we commonly run into issues that relate to password complexity when wanting to generate randomized passwords. A feature that would greatly improve the experience. I'll give a couple of examples. In quite a few instances relating to a certain compliance demand, we may not use spaces or dashes (-). As we use passwords with many characters 60+ for the accounts in question, it can be a tedious process for the workers needing to generate these passwords often, when they must have symbols but are unable to exclude dashes specifically. Another example in another area, we have a demand that we must not use repeated characters. As these passwords need to be memorable, many prefer to use the password generator set to memorable passwords but we repeatedly receive complaints about the passwords generated not meeting the complexity requirements. I'm sure many companies have these kind of infuriatingly detailed password complexity requirements and often different ones in different locations. By integrating some more advanced complexity options in 1Password you could improve the UX and increase security for companies that will no longer have employees unchecking the symbols option or adding another number to the end of their reused password, simply because the generated password didn't work.Feature Request: Optionally allow sharing recipients to edit/update entries
Hi I love 1Password, cannot live without it in my personal and professional life. But one thing I struggle with is helping my customers maintain a safety first demeanor when it comes to sharing secrets. With 1Password it is easy enough for me to share secrets with them securely, but the inverse is not true UNLESS they also have 1Password, or similar. [2025.10.09 - Update] After looking into WHY this doesn't exist I now understand the problem that allowing an external non vault member to write directly into my vault would break the security model as that external non vault member would need my keys to write into my vault. So instead it could be something like this You initiate a “Secret Request” from 1Password: It generates a unique, signed URL. Optionally, you can label it (“Please send me your API key for X”). The recipient (your customer): Opens that link in their browser. Enters their secret (password, API key, etc.). Their browser encrypts it locally with a one-time symmetric key before upload. The key is only embedded in the returned “Send” link that comes back to you. You receive the “return link”: You open it once, decrypt locally, and copy the secret into your own vault. Optionally, the link auto-expires after one view or a set time. 1Password’s servers never see plaintext, they just store encrypted blobs. Full disclaimer, some AI servant came up with the above summary after I was trying to figure out why it may not be secure to just have people write directly into my vault and what the alternatives were. [Original not so secure feature request below] The feature I am looking for and would be willing to pay for, would be to allow sharing an entry, blank or otherwise, and then to optionally indicate that the sharing recipient may update the values or create new ones. Basically I want to allow someone external to be able to populate an entry in my vault as a mechanism for them to securely share secrets with me. Use case: I need to do an integration project with my customer's ERP system and I need a secret from them. They need to share this secret with me and may not have a great way to do that securely. So if I could securely send them a link to an entry in my vault with edit permissions, then they could easily just drop the secret in there. From a feature point of view, I guess it doesn't have to be limited to Update only, you could send someone a "Please create a new entry in my vault request", and then the entry would not have to exist prior to them getting the create request. Let me know what you thinkFeature request - Global setting for lock on OS lock
There is a global setting for idle time 1Password lock, but our users have given us feedback that what prevents them from using 1Password is when 1Password locks on OS lock (like Win+L). We have SSO, so logging back in doesn't require much input, but the padlock indicator in the browser extension isn't obvious to them. They just aren't getting in the habit of unlocking 1Password when they resume their computer session. There is an individual client setting to control this, but we have hundreds of users and we don't want to try educating them on finding this setting to change when clearly there's capacity to control client settings at a global level. I request on behalf of my users to add that global control so we can disable this setting.
