Assign Login to Multiple Groups

lancefisher

I'm using 1Password for Teams to store shared logins. I really like it so far. I'm using Vaults to share these logins to specific groups of people in our company.

e.g. I have the following Vaults: Dev, Support, Sales

We have some shared logins, e.g. BrowserStack. This has one username and password that many people use. So I've added BrowserStack to the Dev vault. Since support needs access as well, I've copied the login to the Support vault.

This works okay, but there are two shortcomings:

1. When I search "All Vaults" it shows up twice
2. When I change the password on Dev/BrowserStack, I also need to change the password on Support/BrowserStack

If I could put one login in multiple vaults, I think it would solve this. Or possibly have the concept of a "symlink" login.

Ultimately, I want to take any item and assign it to either 1 person or a group of people, and be able to update the item in one spot.

---

1Password Version: 6.1
Extension Version: 4.5.3.90
OS Version: OSX 10.11.2
Sync Type: Not Provided
Referrer: kb-search:assign login

[Deleted User]

Hello, @lancefisher! :)

My understanding is that the feature you describe is not currently available in 1Password for Teams.

At the moment, the official way to go about it would probably be to create a shared Vault for "Dev & Support" — or to continue to manage this one login by hand, ensuring that all updates are performed twice.

If you find yourself with multiple such shared logins, it might be worth taking a moment to organise your Vaults differently — by service type or workflow, for example, instead of by department. Since 1Password sports an All Vaults view, the default contents of which can be customised, it often pays to have numerous small Vaults.

This being said, I have seen a few requests for this feature on the forum since 1Password for Teams launched, and I am pretty sure that the good people at AgileBits are aware of it and looking into it. I believe the reason it cannot be implemented right away is that the multiple layers of encryption that keep our logins safe and prevent the Vaults from leaking into each other also preclude any kind of "bridging" between pools of data. What looks like a small interface-level feature apparently runs down to the very core of the security model, so I would not hold my breath for it to appear immediately. (But again, I am only a fellow user, so this is pure speculation on my part.)

Jacob

Hi @lancefisher! That's a very interesting situation, and one I'm sure you have a bit of company in. As mentioned in this thread, we're looking to add this functionality in the future, but at the moment we don't have it, as Deleted User noted. I do like his workaround, though. It's worth thinking about the vault setup a bit differently. If Teams doesn't quite fit this particular use case, don't worry. Things are still in beta and we're still adding new features every week, and sometimes twice a week. :) Thank you so much for the feedback and for using Teams.