Where to store API keys and secrets in a small company
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
- Shared logins. The social media account, the supplier's website, the account for your web address.
- API keys. An API key is a long password that one program uses to work inside another. For example, your website uses one to pass orders to your accounting software.
- Bank and payment access.
- Everyday codes. The WiFi password, the alarm code.
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
| Place | Why it happens | The problem |
|---|---|---|
| Chat message | It is the quickest way to pass one on | Everyone in the chat can still find it years later |
| Spreadsheet | Everything else is in one too | Anyone with the file sees all entries, and nobody knows who looked |
| The provider sent it that way | Copies sit in several mailboxes | |
| One person's head | That person set things up | The company is locked out when they are ill or leave |
Four signs of a good home
- It is encrypted. The entries are stored in scrambled form. Without permission, nobody can read them.
- Access is set per entry. Sales sees the sales logins. The bookkeeper sees the bank. Nobody sees everything.
- It keeps a record. You can look up who opened or copied an entry, and when.
- It belongs to the company. The vault is still there when any one person leaves.
Three rules for API keys
- One key per use. If two programs share a key, you cannot replace it for one without stopping the other.
- Name each key after its purpose. Also note who created it.
- Never paste a key into a chat, an AI app or a screenshot.
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.
- Look up which secrets the person could see.
- Change the passwords of those shared logins.
- Replace the API keys the person could copy.
- Remove the person from the vault and from each tool.
Without a record, the only safe answer is to change everything.
Moving in, in one afternoon
- Search chat, email and shared files for the words "password", "login" and "key".
- Put each find into the vault with a name and the people who need it.
- Change every secret that was found in chat or email. Others may have seen it.
- 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.
- Secrets: a team password vault in your workspace
- How to add a shared secret and request access
- Approvals: where access requests are decided
Create a free workspace and move your first ten shared logins out of chat.