Controlling shared credentials in a team vault
Use named accounts where possible and manage unavoidable shared credentials with limited vault access, recovery plans and a departure process.

Some services still require a shared credential. A team password vault can control who receives it and keep ownership with the business, but the underlying account remains shared.
First check whether the service supports named users, delegated access or a supported integration identity. Use a shared credential only where the business has accepted the limitation.
Create a business-owned item
Store the credential in an organization-controlled vault or collection. Record the service owner, who may use the item and why.
Keep recovery methods and administrator access under the business’s control. Confirm the account doesn’t depend on one employee’s personal email or phone.
Use the shared-login guide to review service-level accountability and alternatives.
Limit vault permissions
Grant access only to the people who need the item. Check group membership and inherited permissions as well as individual assignments.
Separate permission to use a credential from permission to edit, export or change sharing where the product supports it. Review the administrator roles that can override those settings.
For example, Bitwarden’s collection permissions describe different access levels and the limits of hidden-password settings. Test how those settings behave in your own vault before you rely on them.
Treat hidden passwords as shared secrets
A setting that hides password text may reduce casual copying. Someone who can autofill a password can often still recover it, and may already have copied it.
So when someone’s access is removed, plan to change the password as well. Check active sessions, saved credentials and the account’s recovery options too.
The vault’s audit log can show that someone opened an item. It won’t show what they did in the service afterwards.
Test sign-in and recovery
Protect vault access with the supported authentication controls. Have the vault administrators practise the recovery process with a test account.
Decide how staff complete work when the vault or a second-factor device is unavailable. Keep emergency access controlled, recorded and reviewed.
For a shared service’s MFA, confirm the supported arrangement with the provider. Avoid improvising a process that depends on sending codes through ordinary chat.
Plan departures and changes
Remove a departing person’s vault and service access promptly. Assess whether the shared credential needs rotation, along with recovery methods and active sessions.
Changing the password can affect integrations and other staff. Have the service owner coordinate the update and verify that required work still functions.
Review shared items periodically and replace them with named access when supported. Keep the list small enough that ownership, permitted use and recovery remain clear.


