Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Date format inconsistency when setting an alert
Are all the date format entry/display problems EVER going to be fixed?? It's now a whopping 4+ YEARS at least since these have been a problem, and ALL fields (including the relatively new Alerts field!) still have massive issues in both date entry and final display. Just look at the how many search results —128; with the oldest being July 2021 on this new forum system (so likely even longer than that!)— there are for date format issues: search - Date format problems Here's another more recent thread with the same old issue being mentioned, yet only placation responses being given as unsatisfactory answers by 1P staffers! New Feature "Expiry date" - Where is the alert? And here we are today, and the same issues persist... See how the date 2 September 2027 appears on one field (as: 02/09/2027) yet on the related Alert field directly underneath it completely differently (as: August 26, 2027)! ...Even more bizarre, given my system settings on all my devices are set as a third way to show differently again (as: 2027.09.02.Thu)!! Who on earth at 1P thinks this is acceptable and in no way confusing to your users – going on for several YEARS now?!
Improved date formatting in the 1Password desktop app
Hello 1Password Community! With the next update to the 1Password desktop app (version 8.10.80), we have improved how date formats are handled when viewing and editing an item. Leading up to this update, there has been some inconsistency with how the desktop application has handled date formats when viewing and editing items. In some cases, date formats were being determined by the display language set in 1Password whereas in other cases, date formats were being determined by the language set against the device. This has led to some users seeing different date formats within the desktop app causing confusion. With this update, we've made things consistent by ensuring that dates saved against items always appear in a format determined by the locale set against your device (both when viewing and editing items) and never by the display language set in 1Password. This way, the desktop application can support more date formats than just the ones tied to the display languages that we support. Along with the recent improvements that we made to the date picker, we are hoping that you enjoy a much improved experience with dates in the 1Password desktop application! Thank you!
Allow configuration of Quick Access Hotkeys and auto pasting
Hi 1password Team, After launching Quick Access, it's cumbersome to have to enter another three key combination for the e-mail, password etc. If the login page isn't recognised due to missing HTML elements (I acknowledge this is the fault of the website developer but a frequent occurrence), this could be six separate three combinations key (Quick Access > Email, Quick Access > Password, Quick Access> 2FA). This more than an annoyance for work or even home use, especially for those of us with limited mobility. Throw in working across multiples OSs and muscle memory goes out the window. Feature Request: Option to customize the shortcuts within Quick Access preferably allowing a single key. Auto-Paste would greatly be appreciated as well. Either via a global setting or a modifier. Best,Show favorites on Quick Access
It would be a great feature to show the user's favorites on the Quick Access panel. Then you could press your keyboard shortcut and arrow down to the favorite you want to auto type. This was the flow I used to use with KeePassXC and it worked nicely. Additionally, a button below the favorites to browse the whole list of items would be nice. That way, if you didn't remember what you called something and you pressed the Quick Access key you could scroll and find it.
August at 1Password: Android filling updates, Pax8 Marketplace, and AI security insights
Welcome to your monthly roundup of what’s going on in the world of 1Password! Updates to autofill in Chrome and Brave on Android devices Google’s recent changes to Chromium browsers on Android introduced improvements, but also created points of friction for third-party password managers like 1Password. In response, we’ve updated 1Password for Android’s integrations with Chrome and Brave to provide a stable native autofill experience. Install the latest version of Chrome or Brave, then follow the steps in our guide to get your browser integrated with 1Password for Android. You can learn more in a detailed post from Patrick, our Android developer extraordinaire! 1Password MSP edition now available on the Pax8 Marketplace After the general access launch of 1Password MSP edition earlier this year, we’re excited to announce our enterprise password manager is now available in the Pax8 Marketplace. The MSP edition of our enterprise password manager has been purpose-built in collaboration with over 1,000 MSPs to offer simple yet comprehensive tools for managing multiple clients, improving profitability while scaling, and protecting client data. Enhanced access review features with Trelica by 1Password Trelica by 1Password is helping to close security gaps created by unmanaged app access, shadow IT, and more. We’ve made this process easier and more efficient than ever with new access reviews. These new capabilities allow security teams to conduct continuous and scheduled reviews supporting proactive deprovisioning and access auditing across all apps. Reviews are automated and fully auditable with clear, detailed reporting. Research on security challenges caused by AI AI is front of mind for tech and security experts alike. In our ongoing work to lead security conversations relating to AI, we commissioned a survey of 200 North American security leaders which identified four key concerns around AI governance and security controls: Limited visibility into AI tool usage AI and security policy enforcement Unintentional exposure via AI access Unmanaged AI You can find more about these security concerns, and how to mitigate them with 1Password, in our blog post. Random but Memorable episodes in August How AI is supercharging social engineering attacks with Rachel Tobac 7 steps to secure digital parenting with Alanna Powers from FOSI Release note highlights Browser Extension An issue with “Hide on this page” has been fixed Improvements to performance with reduced input/output on page load An issue where the extension could become unresponsive in Firefox has been resolved Fixes and enhancements to saving, singing in with, and authenticating passkeys Improved filling behaviour on payhoa.com, ticketmaster.com, and chexsystem.com Mac, Windows, and Linux Hardware acceleration has been enabled by default on Wayland Fixes for incorrect update notices, incorrect banners requesting Git commit signing reconfiguration, erroneous “Item created in” notifications, and formatting for some right-to left-text locales A filling issue with Universal Autofill has been resolved iOS, and Android Fixes for a crash on unlock, and an autofill crash Passkey support for related URLs and subdomains, plus other passkey related enhancements A fix for an issue affecting SSO users that could prevent unlock after an email change
Linux client fails to save 2FA token when gnome-keyring is running
I am running NixOS using Gnome, and I have enabled gnome-keyring (and I have verified that gnome-keyring is in fact running and that the org.gnome.keyring bus is bound using busctl). 1Password consistently fails to save its 2FA token. The log file contains this line: WARN 2025-04-14T07:45:16.372+00:00 runtime-worker(ThreadId(2)) [1P:op-b5-client/src/internal/unauthorized_session.rs:1054] Failed to save an account's 2FA token with an error of SystemKeyringError(LinuxError(DBus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name org.kde.kwalletd5 was not provided by any .service files"), Msg { type: Error, sender: UniqueName(Str(Borrowed("org.freedesktop.DBus"))), reply-serial: 2, body: Signature("s") })))). 2FA will only be valid for this unlock session! This suggests that 1Password is attempting to use KDE's kwallet as a storage backend rather than gnome-keyring. How does 1Password determine what keyring backend to use? Is there a way to override this choice?
