Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Can we get 1st-party support for keyboard shortcuts?
Now that the interface to edit/set keyboard shortcuts has been removed from 1Password running under Wayland, It would be preferable if the installation package made the shortcuts available to configure by default, rather than https://support.1password.com/keyboard-shortcuts/?linux#wayland. I wrote about this before under a blog of post yours, but it was ignored. It's trivial to add Desktop Action sections to your existing launcher file, and reference them in an Actions= directive: [Desktop Entry] Name=1Password Exec=/opt/1Password/1password %U Terminal=false Type=Application Icon=1password StartupWMClass=1Password Comment=Password manager and secure wallet MimeType=x-scheme-handler/onepassword;x-scheme-handler/onepassword8; Categories=Office; Actions=Show;QuickAccess;Lock;Fill; [Desktop Action Show] Name=Show 1Password Icon=window-symbolic Exec=1password --show [Desktop Action QuickAccess] Name=Show Quick Access Icon=search-symbolic Exec=1password --quick-access [Desktop Action Lock] Name=Lock 1Password Icon=lock-symbolic Exec=1password --show [Desktop Action Fill] Name=Fill in Browser Icon=web-browser-symbolic Exec=1password --fill Putting a symlink to this expanded .desktop file under /usr/share/kglobalaccel/ makes those keyboard shortcuts appear in KDE Plasma's Settings app:
Don't merge *.company.com. Treat company.com as a top level domain.
We've purchased 1password business to help employees manage internal passwords. Many of these systems are on the same *.company.com domain. 1Password keeps linking these different systems into the same record. Creating records and then manually changing the "Only fill on this exact host" option is extremely clunky. How can we: Set a default option for all our users for 1Password to always match on exact host? or Make 1Password treat our internal domains (e.g. company.com, company.local) as top level domains - ideally this would be a policy we can configure?
1Password in FileMaker Pro
As a longtime user of both 1Password and FileMaker Pro I still wonder if it isn’t possible to somehow use 1Password to automatically fill username/password when I open up a FileMaker database. Since I’m not just a user but a developer I need to open up different databases a lot every day. And although I store my passwords in 1Password there is no way to auto-enter them directly. I still need to copy-paste (that’s the downfall of using a different password for every login) the password from 1Password to FileMaker Pro.
Show the requested credential
I'm heavily using 1password now for agentic usage. All of my business is set up on it now, and all of my credentials are locally using op://, or service accounts. I've put in a lot of effort to try and isolate systems using least privilege, but one problem is that when agents (or applications) request a credential from the system, it doesn't say WHAT credential is being requested. Half the time it doesn't even say the correct name for the application making the request, either. This is a big problem, because I'm starting to get into the habit of just spamming "Accept" blindly. But the whole reason I have set up this whole pipeline is so I can catch malicious programs trying to gain access - for example, supply chain attack infections. Without seeing what credential is being requested, and the process information that is requesting it, I'm finding it's not actually adding much protection at all, because it's putting me into a false sense of security and promoting bad habits. If I'm running multiple agents in parallel, which is often the case, it might just say "Terminal requests access to your vault" or something similar. Which terminal is that? What is the underlying entity being requested? What credential? What is the process ID or terminal title, so I can isolate it to a terminal/agent? Etc. I think this is something that urgently needs to be added. Otherwise, as it stands, it's not really offering much protection because users will just go "oh, it's probably just that agent running - I'm sure it's fine" and accept everything. If that agent happened to have installed a malicious npm package, you'd probably catch it too late.Feature Request: “Mirror/Clone Entries” for Cross-Vault Access Without Duplication
Hello 1Password Team, I would like to propose a feature that addresses a practical operational constraint we are currently facing with vault management. Problem Statement In our workflow, we maintain certain login credentials that need to be accessible across multiple vaults. However, due to differing user access permissions between vaults, we are forced to duplicate the same login entries across multiple vaults. This creates the following challenges: Data duplication across vaults Inconsistent updates when credentials change Increased manual effort and risk of outdated information Using a single shared vault is not a viable solution because access requirements vary between teams and users. Proposed Solution: “Mirror” or “Clone” Entries We propose introducing a feature that allows creating view-only mirrored copies of an entry across multiple vaults. Key Concept A single source entry exists. Multiple mirror copies can be placed in different vaults. Mirror entries are view-only. Any update made to the source entry automatically reflects across all mirrors. Suggested Implementation Options Option 1: Mirror Hub (Preferred) Introduce a dedicated vault (e.g., “Mirror Hub”). A designated user or admin manages source entries in this vault. Users can create mirror copies of these entries into other vaults. Ensures centralized control and governance, especially in team environments. Option 2: Flexible Source Location Allow any vault item to act as a source. Users can create mirrors of that item in other vaults. Less centralized, but more flexible. User Experience Suggestion When creating a new item: Add a new option: “Mirror Entry” Selecting this option: Displays a dropdown/list of available source entries (e.g., from Mirror Hub) User selects the item Places a mirror copy in the desired vault Benefits Eliminates duplication of sensitive data Ensures real-time consistency across vaults Reduces operational overhead Maintains strict access control per vault Ideal for team-based environments with segmented permissions Closing Note This feature would significantly improve usability and data integrity for organizations managing multiple vaults with overlapping credential requirements. I strongly believe this would be a valuable addition to 1Password and hope the team will consider it seriously. Thank you for your time and continued innovation.Expiration report
I'm using the date field (new) and the alert expiration. But there is no view or report to list by this fields. and no pop up or something to have visibility of alerts. That means I have to go one by one entry to see that field. My question is if there is a expiration or alert report and how to access this?
How to customize the suggested item name in the auto-save prompt?
Hello. When a user saves a new login on our site (e.g. app.acme.io), the "Save in 1Password" prompt defaults to a name derived from the domain so we get "Acme" instead of "acme.io". It doesn't match our brand. We've already done what compatible-website-design recommends: brand-name <title>, application-name, apple-mobile-web-app-title, og:site_name, manifest.webmanifest (name / short_name), correct autocomplete attributes. None of these influence the suggested name. Questions: Is there a client-side mechanism (meta tag, well-known endpoint, JSON-LD…) we're missing to declare our brand name for the auto-save prompt? If not, what's the official process to submit a domain + brand name + logo to 1password Rich Icons / website database? Thanks.
Issue: 1Password prompts repeatedly to save the login
Hi, when logging in with SSO or Social Logins (Google/Microsoft/etc.), even if 1Password was used for signing-in, it again prompts to save the SSO method. It becomes annoying, because if I don't remember if I have saved it or not, I have to first check, and then dismiss it. Please fix this.
Feature Request - Step Up Auth Geo-restrictions
We are starting to have more users working overseas temporarily from locations outside our usual allow list. We'd like a middle ground option to allow these locations but only with an additional authentication factor, or allow them for a small number of users.
