Vault and secrets
Add a secret once, attach it to the projects and jobs that read it, rotate it on a schedule, group secrets in bundles and import a .env file.
The Vault keeps your passwords and keys. A value is write-only: once saved it is never shown again in the console, in logs or to an AI assistant. Projects and jobs receive secrets as environment variables when they start.
Add a secret
Resources > Vault > New secret (or Create > New secret).
Fill in:
Field | Meaning |
|---|---|
Name | The variable name projects read, such as |
Owner | Who manages it: you, a team or the organisation. Changed later only by a transfer |
Value | Write-only: kept in the vault, never shown again |
Description | What it is for |
Kind | Password, API key, connection string and so on |
Handed over as | How projects receive it |
Rotate every | Days; owners are reminded when it is due. By hand means no reminder |
Expires on | Empty: never |
Click Save secret.
Attach it
On the secret's page click Attach, pick the project or job and the Variable name it should have there. It arrives at the next start. Where it is used lists every attachment. You can also attach from the project: Settings > Secrets and env > Pick from the Vault.
Auto-attach rules make new projects get a secret by themselves when they are created: Add rule with a Project type and a Team or organisation. A personal secret is attached project by project; transfer it to a team or the organisation to use rules.
Rotate, archive, transfer
Rotate: paste the New value and a Note ("Provider rotated the key"). Every attached project gets the new value on its next start.
Versions: every value it has had (values never shown). Roll back puts an older value in as a new version.
In use off: attached projects and jobs stop getting it at their next start; the attachments stay.
Archive and Restore; Transfer to a new owner (a team, the organisation, or a person in it).
Some actions (for example revealing a service password or changing a protected secret) ask you to confirm your password, and your one-time code if your account uses one.
Import a .env file
Import, paste lines like API_KEY=... and DB_PASSWORD=... (comments # and empty lines are skipped). Tick Also make a bundle to group them under a name such as payments-prod.
Bundles
A bundle is a group of secrets attached to a project or job in one go. Bundles > New bundle, give it a Name, Owner and Description, add secrets. Attaching the bundle attaches all of them.
Your own vault
With the outside-vault add-on, an organisation admin can attach the organisation's own vault by name; secrets then come from there.