Insights from practice

Shared business logins: vaults, roles and offboarding

Share business access in an organised way: company ownership, individual vault accounts, suitable roles and a clear joining and leaving process.

Workplaces
DAXS mark above three separate symbols for a vault, individual roles and access revocation

An assistant needs the supplier login, accounting must provide cover during holidays and business access must remain available when someone leaves. A shared vault helps when account ownership, roles and handovers are agreed in advance.

Use individual accounts wherever the service supports them

If a portal supports individual users with different permissions, give each person their own access. This makes responsibilities and later revocation clearer. A password manager then stores individual credentials; it does not replace the service’s own user management.

Some supplier portals or older applications genuinely provide only one shared account. For these cases, set up a business team vault with named authorised people and provide the shared password through it. Nobody therefore needs to use the same personal password-manager account as a colleague.

Shared access needs a business owner

A hypothetical example: an employee originally registered a purchasing portal with her private email address. She later leaves the company; reset messages and the second factor remain tied to her personal identity. A vault entry alone does not resolve that dependency.

Business access therefore includes the service, company ownership, a responsible person, cover and a defined recovery route. The reset contact and billing information must match the agreed business responsibility. Personal accounts and private vaults remain separate from shared company access.

Using, editing and sharing are different tasks

The accounting group needs certain logins, without automatically needing every administrative permission in the password manager. Likewise, someone who manages membership need not be able to read every secret. In 1Password, vault management and access to contents are explicitly separate permissions; actual capabilities differ by plan and product.

Organisational example without secret values. Implement actual product permissions to suit the requirements.
Example role Use logins Edit entries New sharing permissions
Accounting Approved finance and supplier logins Agreed for the person’s area of responsibility Through the responsible approval process
Assistant / cover Required shared portals Only as needed for the task Through the responsible approval process
Vault administration Only separately granted content permissions According to separate authorisation With documented responsibility
Emergency cover Prepared for the defined emergency According to the approved emergency procedure No blanket permanent permission

The matrix describes an organisational requirement, not an identical feature set in every product. Visible or concealed password fields, copying, exporting and sharing have different technical protection. A simple interface setting does not reliably prevent every way of reading data. Permissions in the vault and target service remain decisive.

1Password: vault permissions (external link) · 1Password: permission enforcement (external link).

Make joining and cover normal processes

When someone joins, add them with their own account and assign a suitable group based on their duties. A brief functional test shows whether required logins are available and other areas are blocked. Handover includes how to use the system, report lost devices and contact someone with questions.

A deputy receives the required access before the first emergency. Second factors and reset methods are also arranged. If MFA is used for a shared target account, the approved cover route must suit that service. Sharing only the password is insufficient if every login requires a device available exclusively in someone’s private possession.

Emergency access is a separate authorisation for a defined reason, followed by review. Depending on the product, recovery features need preparation. Keeper, for example, points out that its optional account-transfer feature must be configured early. Test which data can actually be taken over in the selected model. Keeper: prepare account transfer (external link).

Shared business access lifecycle: ownership, roles, use, departure and targeted password changes.
Prepare joining and cover, act specifically on departure: revoking permissions and changing a password at the service remain separate steps. Conceptual example.

Removing someone from the vault may not be enough when they leave

At the agreed departure time, check individual target accounts, password-manager membership, groups and existing direct shares. Access granted through another group may still exist. Identity providers, active sessions and registered devices belong in the service-specific process.

Revoking vault access does not invalidate a shared password that someone already knows or has copied. Identify the affected shared logins and change passwords at the respective service where required. Consider integrations and other authorised users before changing them, so that workflows do not fail unintentionally.

Hand over business data using the agreed procedure before removing an account. Suspending membership, changing a vault entry and permanently deleting a user account are different steps. Do not assume personal content is company property without checking.

A short record provides clarity

For each handover, start with the service, affected role, approval, person carrying out the action and result. Records contain no passwords, reset codes or secret keys. They show that required steps were completed and unresolved dependencies passed to the responsible person.

A second review is useful for extensive administrative and emergency rights. Ongoing checks also ask whether groups still match actual duties. A clear initial setup remains understandable only with occasional maintenance.

Start with a manageable permissions matrix

DAXS can inventory shared logins, clarify company ownership and cover, and build a suitable role model with joining and leaving procedures. A pilot using a real business use case checks sharing, recovery and revocation. Scope, responsibilities and ongoing support are agreed together.

Organise business access and handovers · Compare cloud and self-hosted password management · Workplaces and collaboration

Frequently asked questions

Can a shared vault replace individual user accounts?

A vault governs how credentials are provided. Where the service supports individual users, manage their permissions and departures there. For unavoidable shared access, ownership remains explicitly defined.

Must every password be changed whenever someone leaves?

Check the affected logins. An individually blocked user account needs different treatment from a shared password that remains usable. Assess known shared secrets and their dependencies specifically.

Does management automatically have access to private vaults?

That depends on the product, account type and configured permissions. Keep company logins deliberately in the areas intended for them. An administrative role does not imply blanket permission to read private content.

Sources: Bitwarden: manage members and organisations (external link) · Keeper: roles and account transfer (external link). Examples are conceptual; specific plan, permission and recovery capabilities are checked for the environment concerned.