Syncing Main and Secondary vaults with each other.
I currently have all my items in my main vault and subsets in secondary vaults that I can share with my wife, my kids, and other subsets.
The secondary vaults sync from the other users to my secondary vaults via Drop-Box; But I have to manually maintain syncronization to my main vault.
We really need a better way to do this.
One idea is that I go to each secondary and click a command to sync and it will sync all items to the main vault.
Another idea is that there be an internal tag for a primary copy of an item and for a secondary that also points to the primary.
Then clicking a command to sync would sync all items with their primary copy and if a primary was in the vault would sync forward to all its copies.
Would be great if we could also set items to be primary. i.e. be able to change which is the primary copy.
Another idea would be for us to be able to sync on an item by item basis so I would click sync each time I updated an item.
In this case syncing all vaults and items, or to save cpu cycles sync each item we click sync on.
Another idea would be if all the syncing (using primaries and copies as above) would be automatic.
Why is it such a pain in the neck the way it is?
I have some items I share with group a, b, & c.
Others with a, c, d, another with just b, some with c, d, ...
When every I update an item I have to try and remember what other vaults it is in.
1Password Version: 1PW 4 Version 4.4.3 (443000)
Extension Version: 4.3.1 on Firefox 38.0.5
OS Version: OS X 10.8.2
Sync Type: Main: iCloud, Secondary: Dropbox
Comments
-
Hi @BobAllison,
Part of the reason is 1Password hasn't always had multiple vault support so certain mechanisms aren't as mature as others e.g. the copy and move vault actions. When we first introduced secondary vaults I suspect there was the assumption that a Login item would exist in one vault - not multiple ones. As we've discovered since then some people want to keep a single item in more than one place and to have them linked.
I don't know what may happen here but just to ensure you're not disappointed later, whatever might happen would either be in 1Password 5 or a future version only, it wouldn't be backported to 1Password 4.
As it stands about the one option that might help with maintaining this approach is the use of tags which will move with the item. You could tag an item with all the vaults it's in so you know where to copy the new item to when it's altered. At the moment that's about all I can think to suggest.
Part of it is that how secondary vaults are implemented isn't ideal for what you desire given that each vault contains it's own individual copy, what you really want is a vault view that connects to certain items but still where a single item exists and a change from any single view would change the underlying data. If I'm correct that would be a sweeping change but would be more robust (in my mind anyway) than syncing between vaults. The devs may disagree of course and they're in a much better position to so what is and isn't a good idea.
Sorry there isn't a better solution for you right now but we will take this on board.
0
