What is the best practice for organizing vaults among different departments?
Let's say we run one vault for IT and one for PR. Now it turns out both need access to a mailing tool like mailchimp.
IT had it first, so we would duplicate it for the PR vault. But once IT changes the password, PR has an outdated one.
We kinda work around this by naming one "copy of" and tagging its source, so users know whom to ask for an update. But that is a crutch. It does feel crutch-y.
In theory, we could run vaults for every login we have. But the sysadmins are already slightly crazy and that might push them over the edge.
We could try to structure the vaults around smaller topics (like "mails") or roles (like "sending mails"), but that is a very distracting and time consuming exercise in the topology of our business.
So: Any hints or recommendations? Any use of groups or tags that we might have missed?
Or maybe you are already working on separating logins from vaults? So one login can be in several vaults and gets updated on all of them?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided