The keys that run your systems are often more powerful than any website login, yet they end up in text files, chat messages and old emails. The vault has an entry type for each kind of technical secret, so everything has a proper home behind your master password.
Choose the right entry type
Add an entry and pick the type that matches what you are storing. Each type has its own fields:
- API key. The service, the key and its secret, with an expiry date.
- AWS credentials. The account ID, access key ID, secret access key, an optional session token and the region.
- Database connection. Host, port, database name, username and password, or a full connection string.
- SSH key. The host, the public and private key and the passphrase.
- GitHub token or personal access token. The token, its scopes and when it expires.
- Environment variables. A whole set of variables for an app or environment in one entry.
Every type also has notes, for things like which server or project the secret belongs to.
Keep them in order
-
Use folders
Group entries by system or environment, such as Production, Staging or Payments.
-
Record expiry dates
Add the expiry date for keys and tokens that run out, so you can see what needs replacing before it stops working.
-
Copy, do not reveal
Copy a key with one click without showing it on screen, which is safer when you are sharing your screen.
Share with the right people
Share an entry only with the people who need it. A viewer can use it, an editor can update it when the key is rotated and an admin can also delete it and share it on. Remove a share as soon as someone no longer needs access.
For administrators. The vault and its browser extension can each be switched on or off for the whole workspace in Application Settings, under Password Vault.
New to the vault? Start with Keep Passwords in the Vault. For more, see the password vault.