Flow.Documentation

Set up a vault

3 steps± 2 minVideoVerified 28 Oct 2026
  1. Step 1 · Choose the environment
  2. Step 2 · Choose another vault
  3. Step 3 · Propose, test and approve

Every environment keeps its secrets in a vault. That is Flow's own vault, unless you choose a vault in your own cloud. You set it per environment. An owner approves the move.

Watch the whole guide as a video3 steps in one film
Step 1 / 3

Choose the environment

On Environments, click the environment, for example Acceptance, and choose Secrets and keys. At the top you see in one sentence whether the vault works, and when that was last checked.

  1. Click A Acceptance no version yet Running
Choose the environment · Click A Acceptance no version yet Running
  1. Click Secrets and keys Vault · no AI key yet · own key
Choose the environment · Click Secrets and keys Vault · no AI key yet · own key
Step 2 / 3

Choose another vault

Choose Choose another vault. Choose your cloud: Azure Key Vault, AWS Secrets Manager or Google Cloud Secret Manager. Fill in where the vault is, and why you move. Nothing is moved: the names stay, you put the values in the new vault yourself. Flow never copies values.

  1. Click Choose another vault
Choose another vault · Click Choose another vault
Choose another vault · Flow's own vault, Azure Key Vault, AWS Secrets Manager and Google Cloud Secret Manager, with Propose the change.
Step 3 / 3

Propose, test and approve

Propose the change makes a proposal. The portal then shows step by step what to set up in your cloud, and tests the new vault without ever showing a value. An owner approves the move; the environment restarts and reads from the new vault afterwards. Check now shows at any moment whether the vault works.

Propose, test and approve · The Check now button.

This guide was carried out step by step on 28 Oct 2026 by an automated test on Flow (version 96971699).