Worknano

Where to store API keys and secrets in a small company

Updated 2026-11-15

Where to store API keys and other secrets in a small company: in one password vault that belongs to the company. A vault is a protected store where each entry is visible only to the people who need it, and where you can look up who opened what. Today most secrets sit in chat messages, spreadsheets and emails. Each of those keeps a copy you can no longer take back.

What counts as a secret

An API key deserves the same care as a password. Whoever holds it can do everything the key allows, and nobody asks a second time.

Where secrets end up, and why that is a problem

PlaceWhy it happensThe problem
Chat messageIt is the quickest way to pass one onEveryone in the chat can still find it years later
SpreadsheetEverything else is in one tooAnyone with the file sees all entries, and nobody knows who looked
EmailThe provider sent it that wayCopies sit in several mailboxes
One person's headThat person set things upThe company is locked out when they are ill or leave

Four signs of a good home

  1. It is encrypted. The entries are stored in scrambled form. Without permission, nobody can read them.
  2. Access is set per entry. Sales sees the sales logins. The bookkeeper sees the bank. Nobody sees everything.
  3. It keeps a record. You can look up who opened or copied an entry, and when.
  4. It belongs to the company. The vault is still there when any one person leaves.

Three rules for API keys

The checklist for when someone leaves

The real test of your storage is the day a colleague leaves. With a vault and its record, this takes minutes.

Without a record, the only safe answer is to change everything.

Moving in, in one afternoon

  1. Search chat, email and shared files for the words "password", "login" and "key".
  2. Put each find into the vault with a name and the people who need it.
  3. Change every secret that was found in chat or email. Others may have seen it.
  4. Agree one rule: secrets are shared from the vault, never typed into a message.

How Worknano handles this

Worknano Secrets is a vault inside the workspace. It is encrypted and holds logins, API keys and notes. For each entry you choose who has access: everyone, a role, a team, named people or only you. People without access see the name only. You can allow colleagues to ask for an entry. The owner then approves the request under Approvals. A record shows who viewed or copied a secret and when. The vault uses the same permissions as the rest of the workspace, so access follows when someone changes role or team. The sign-in rules set for the workspace apply to the vault too.

Create a free workspace and move your first ten shared logins out of chat.