Skip to main content

Sharing passwords in a small startup: set up a team vault in an afternoon

Your startup has five people and forty shared logins: the domain registrar, the cloud console, Stripe, the app store accounts, the social profiles. Today they live in a spreadsheet, a pinned Slack message and one founder's head. This post shows how to move them into a shared team vault in an afternoon, and what to decide so it stays safe when people join and leave.

Disclosure: we build DollarDeploy, a control plane that deploys and operates apps on servers you own. The setup below works on any server. Where DollarDeploy covers a step, we say so.

Why it matters: shared credentials are the part of "operations" nobody owns in a small team. The day someone leaves, or a laptop is lost, you find out which passwords were in a chat history.

The short version

  1. Pick a vault that your team will actually use.
  2. Deploy it with HTTPS, then close sign-ups.
  3. Protect the admin panel.
  4. Share by area, not by person.
  5. Back it up off the server, and test a restore.
  6. Write the offboarding steps now.

1. Pick a vault your team will use

The rule: the vault must work in the browser, on phones and from the command line, or people go back to the spreadsheet.

Two good options:

  • Bitwarden (hosted): the official service. Pick it if you need SSO, audit reports or a vendor contract.
  • Vaultwarden (self-hosted): an unofficial server for the Bitwarden apps, written in Rust. It works with the official Bitwarden browser extensions, desktop, mobile and CLI apps, and needs about 512 MB of memory. Pick it if you want the vault on a server you control.

The rest of this post uses Vaultwarden.

2. Deploy it with HTTPS, then close sign-ups

The rule: the vault gets its own HTTPS address, and only your team can create accounts.

Why: the Bitwarden web vault needs HTTPS to run its encryption in the browser. An open sign-up page lets anyone who finds the address create an account on your server.

How:

  • Deploy: in DollarDeploy, open the Vaultwarden template, pick a server and deploy. It asks for 1 CPU, 512 MB of memory and 5 GB of disk, so it fits next to your other apps. The app gets an HTTPS address with a Let's Encrypt certificate that renews on its own.
  • Create your account first. Open the address and register the first user: you.
  • Close sign-ups: set SIGNUPS_ALLOWED to false in the app's environment and redeploy. From now on, people join by invitation only.

3. Protect the admin panel

The rule: the /admin panel stays off unless you set a strong token, and that token never sits in a chat.

Why: the admin panel can invite and delete users and change server settings.

How:

  • Set ADMIN_TOKEN to a long random value. Vaultwarden recommends storing it as an Argon2 hash rather than in plain text (see the Vaultwarden wiki, "Enabling admin page").
  • Invite people from the admin panel. Add SMTP settings to the environment if you want Vaultwarden to send the invitation emails.
  • Optional: if the team works from a fixed office IP or a VPN, restrict the whole app to those addresses in DollarDeploy (app settings, Restrict access to specific IP addresses only). Phones outside that network will not reach the vault, so decide this with the team.

4. Share by area, not by person

The rule: create one organization for the company and a collection per area, then give people access to collections.

Why: when you share item by item, nobody can tell who sees what. Collections answer that question in one screen.

A starting layout:

  • Production: cloud console, server and database credentials, DNS. The CTO and one backup person.
  • Business: Stripe, banking portals, accounting. Founders.
  • Vendors: SaaS tools the whole team uses.
  • Marketing: social accounts, ad accounts, analytics.

Turn on two-factor login for every member, and store the shared two-factor codes in the vault too, not on one person's phone.

5. Back it up off the server, and test a restore

The rule: the vault's data folder is backed up to storage outside the server, on a schedule, and you have restored it once.

Why: the vault holds every key to the company. If the server dies and there is no copy, you are locked out of everything at once.

How: Vaultwarden keeps everything in its data folder (a SQLite database, attachments and keys). DollarDeploy's app backup archives the app directory, including that folder, and sends you a notification when a backup runs. Backups run manually on every plan and on a schedule on paid plans; you can point them at your own S3-compatible storage.

Yes, but: copying a live SQLite file can catch a write halfway. At a small team's write rate the risk is low, but it is not zero. Set a backup prepare command in the app settings that writes a consistent copy of the database first, and restore a backup to a second server once so you know it works.

6. Write the offboarding steps now

The rule: when someone leaves, three things happen the same day.

  1. Remove them from the organization in the vault.
  2. Rotate every shared credential in the collections they could see, starting with Production and Business.
  3. Remove their access to the servers and deploy tools (in DollarDeploy, remove them from the team).

Why: removing the account stops new access, but anything they could read before may already be in a browser or on a notebook. Rotation is what actually closes it.

The other side

Self-hosting a vault means you own its uptime and its updates. Vaultwarden is a community project, not the official Bitwarden server, and it has not been through the same audits. If a customer or investor asks for a vendor-run password manager with SSO and compliance reports, hosted Bitwarden (its business plans) is the honest answer.

The bottom line

A team vault takes an afternoon: deploy with HTTPS, close sign-ups, protect the admin panel, share by area, back it up off the server and write the offboarding steps. Do it before the next person joins, not after the next person leaves.

Go deeper: Running production without a DevOps hire: a checklist for the first-time CTO and Your first production incident: a runbook for a small team.


Team access is one more thing a first-time CTO ends up owning. DollarDeploy deploys your apps and tools, like this vault, from GitHub or a template to servers you own, and keeps them running: HTTPS that renews itself, 30 days of logs and monitoring, backups with notifications, and team members with roles per app. Nothing for you to maintain. Start free on DollarDeploy, no card needed.

All posts Share

Your app deserves a real URL. Ship it to production.