Permit/block access to vault by IP?
I have a situation where we want to allow access to a specific vault when they're using a given source IP. When coming from that same IP, we would want to block access to all other vaults. When using other IPs, we would want to grant full access. It doesn't appear to be doable now, but I would like to put in a feature request.
Feature Request - Linked Entries
The ability to 'link' entries in different vaults. We often have shared passwords that are used by multiple departments. Right now we have to copy entries to each department vault and then update each when the password changes. It would be nice if we could create a read-only/shortcut entry that linked back to a single master entry.
"Type in window" feature
Hello, I still miss the abillity to let type a password into an opened window, i.e. when connecting via Teamviewer to a Windows Server login screen. With 1Password7 it was no problem and worked like a charm. With 1Password8 I always must type in the long generated passwords by hand. Drag and drop isn't working with Teamviewer, AnyDesk, .... . This is just pain when you are remote supporter and need to login to more than 20 different devices every day. This is only time consuming and frustrating.
Storing TLS cert and general private keys in 1password
Hi I'm sure there's perhaps a good reason as to why this is not a feature, but I was wondering if there's a way to store Apple Developer certificates in 1password in a similar fashion to how we currently store and use ssh keys? The use case is that we would like to allow certain employees to have access to our Apple developer ID keys so that they can sign binaries and installer packages. At the moment we have to give them the actual private key and then of course we have no idea what happens to that key after they are done. It would be good if 1password could be brought into play in situations like this so that the key can be referenced and used on the command line and then of course the access is audited in the 1password logs. Does something like this already exist, perhaps I am not looking in the correct place? ThanksNested folders in department vaults
The issue I am having is that we save a very large number of credentails and details in 1password, and currently, I am creating vaults with names of the department and a subsection name as part of the vault name As an example for illustration only: for HR, I have a vault called HR-References, another vault called HR-AnnualLeave, and another called HR-Attendance But this means we end up with a massively long list of vaults. It would be much much better if we could have nested vaults, or even folder to contains to store all the different sets of data in an organised manner under the one parent vault. so ideally we would have a vault called HR, and then within that vault, either subvaults, or folders/containers that could contain specific items by topic Hope this makes sense. ThanksFeature Request: Bulk Edit of Item Icons
As a user of 1Password managing a large number of entries (e.g., logins, servers, services), I would greatly benefit from a feature that allows me to change the icon for multiple items at once. Why this matters: Many items belong to the same company, project, or system, and having consistent icons improves visual recognition. Manually updating icons one by one is very time-consuming. Custom icons are already supported per item — enabling bulk updates would significantly improve efficiency. This would be especially useful for users managing shared vaults or teams with standardized visual structures. Suggestions for implementation: Add a bulk edit option in the desktop or web app (e.g., “Change icon for all selected items”). Allow drag-and-drop of an icon onto multiple selected entries. (Optional) Add CLI support via the op tool for automation workflows. Benefits: Greatly improved productivity for power users and teams. Saves time and reduces repetitive tasks. Enhances visual organization within vaults. Thank you for your continued work on making 1Password great. I hope you’ll consider adding this feature!
Kolide: Allow admins to set Checks to get re-checked soon after restart
In reference to this blog post: https://www.kolide.com/blog/improvements-to-rechecking-after-an-os-update At a minimum, can you include all built-in OS update related checks into this new mechanism that forces a re-check immediately after restart? The real feature request though is to allow admins to select checks to be re-checked at restart so that we have better control. This would apply to other situations where we'd want checks to be re-run soon after restart because there may be other changes that have taken place. For example, we might want to check that security agents are still enabled, re-run checks for app updates that might have taken place during reboot, ensure other security settings are still being enforced after reboot, etc.
Feature Request - Allow inject to run with missing references
Let's assume there is a config template like `.env.template` which I want to share with my team. This could be in a git repo that is committed as part of a code base. To run all of the tests you would need all of the env vars defined but to run a subset of the tests this isn't necessary (think unit, app and int tests). # .env.template file # SQL - Everyone has this access SQL_PASSWORD={{ op://User/sql/password }} SQL_USER={{ op://User/sql/user }} # AWS S3 - Only some people have/need to run these integration tests # aws/password doesn't exist in this user's 1password AWS_PASSWORD={{ op://User/aws/password }} AWS_USER={{ op://User/aws/user }} Now run `inject`: op inject -i .env.template -o .env -f [ERROR] 2025/07/02 13:38:51 could not resolve item UUID for item aws: could not find item aws in vault ... It would be very beneficial to have a flag that ignores missing: op inject -i .env.template -o .env -f -ignore-missing # .env file # SQL - Everyone has this access SQL_PASSWORD=abcdef SQL_USER=me # AWS S3 - Only some people have/need to run these integration tests # aws/password doesn't exist in this user's 1password AWS_PASSWORD= AWS_USER= This would really help with 1Password adoption across my team.
Feature Request: 1 item in more than 1 (shared) vault
I come upon this more and more often... I have a shared vault where users A, B and C have access and I am the administrator/owner. I have another shared vault where users X, Y and Z have access and I am the administrator/owner. I have an item that I need to share with all 6 of these users. I currently have 2 choices and I don't like either of them: 1/ Create a new shared folder where users A, B, C, X, Y and Z have access. This is fine in the cases of small teams. My situation however is a medium-sized business account with all of my clients in my umbrella/envelope account. Users A, B and C are not even aware of the existence of users X, Y and Z and may be uncomfortable sharing items with unknown users. 2/ Duplicate my item and store one copy in each of the shared folders. I dislike this option even more as maintaining the integrity of both copies is risky; there is always the possibility that one copy gets modified and the other does not. Feature Request: I would like to be able to assign/associate 1 item in more than 1 shared vault. The members of shared vault ABC do not need to see or be aware that the item is also in vault XYZ and vice-versa. I am open to other ways of treating this problem/situation as well... Thanks
