Flow.Documentation
ProfessionalConnectionsSecrets and key vaults

Replacing a secret while others work

6 steps± 4 minVideoVerified 22 Oct 2026
  1. Step 1 · Open your development environment
  2. Step 2 · A new version of the key
  3. Step 3 · Switching a leaked key off
  4. Step 4 · What your colleague sees
  5. Step 5 · Your colleague works on the same connection
  6. Step 6 · Both kept, and who did it

You do not replace a key at night when nobody works: it happens while colleagues run workflows and update connections. A new version applies from the next call, also in a workflow that is already running; a version you switch off is no longer used anywhere. The list of connections says which secret no longer works, and when a colleague works on the same connection at the same time, both their change and yours are kept. Below you see both people's screens side by side.

Watch the whole guide as a video6 steps in one film
Step 1 / 6

Open your development environment

In the portal, under Environments, click Development, and there Open. Flow opens in a new tab and you are signed in straight away.

  1. Click Development
Open your development environment · Click Development
  1. Click Open ↗
Open your development environment · Click Open ↗
Step 2 / 6

A new version of the key

Open Security → Secrets, choose the secret and click New version. Type the new key and save: from the next call every connection and workflow uses it, also a colleague's workflow that is already running.

  1. Click Security
A new version of the key · Click Security
  1. Click Secrets
A new version of the key · Click Secrets
  1. Click the secret ‘webshop-sleutel’
A new version of the key · Click the secret ‘webshop-sleutel’
  1. Click New version
A new version of the key · Click New version
  1. In Value, type ••••••••
A new version of the key · In Value, type ••••••••
  1. Click Save
A new version of the key · Click Save
A new version of the key · Version 2, the latest, made by Ada Street.
Step 3 / 6

Switching a leaked key off

If a key has leaked, switch that version off. A workflow running at that moment no longer sends it from its next step. Here you switch off the only version of the old secret.

  1. Click the secret ‘oude-sleutel’
Switching a leaked key off · Click the secret ‘oude-sleutel’
  1. Click Disable
Switching a leaked key off · Click Disable
Switching a leaked key off · Disabled, with when and by whom.
Step 4 / 6

What your colleague sees

Bob has the connections open. After a refresh the list says which secret no longer works, by name, instead of Key stored. The web shop simply carries on with the new version.

What your colleague sees · Secret ‘oude-sleutel’ has no working version.
Step 5 / 6

Your colleague works on the same connection

Bob opens the web shop connection to give it a clearer name. Meanwhile you choose another secret for that connection. Bob saves: Flow does not overwrite your choice, but says what each of you changed. Review lists it.

  1. Click Edit
Your colleague works on the same connection · Click Edit
  1. In Name, type Web shop · orders
Your colleague works on the same connection · In Name, type Web shop · orders
  1. Click Save
Your colleague works on the same connection · Click Save
  1. Click Review
Your colleague works on the same connection · Click Review
Your colleague works on the same connection · Changed only by Ada Street: the key. Only by Bob: the name. Nothing collides.
  1. Click Merge
Your colleague works on the same connection · Click Merge
Step 6 / 6

Both kept, and who did it

The connection now has Bob's name and the secret you chose. The list shows who last changed the connection; Tested only shows after a real test.

  1. Click Explorer
Both kept, and who did it · Click Explorer
Both kept, and who did it · For both of you: Bob's name, your secret, ‘changed by Bob White’.

This guide was carried out step by step on 22 Oct 2026 by an automated test on Flow (version 3e563176).