Flow.Documentation

Follow up on security advice

4 steps± 3 minVideoVerified 22 Oct 2026
  1. Step 1 · Open your development environment
  2. Step 2 · Open Security advice
  3. Step 3 · Fix the finding
  4. Step 4 · Check the result

Flow checks your environment continuously: keys that never expire, tables open to everyone, APIs with too generous a limit. Under Security advice you see every finding with why it is a risk, which standard it belongs to, and usually a button that fixes it for you.

Watch the whole guide as a video4 steps in one film
Step 1 / 4

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 / 4

Open Security advice

Click Security in the bar on the left and choose Security advice. At the top are a score and the number of findings per severity. Below is every finding: what it is, why it is a risk and which standard it belongs to. Here the API Prices allows 5000 calls per minute.

  1. Click Security
Open Security advice · Click Security
  1. Click Security advice
Open Security advice · Click Security advice
Open Security advice · The finding about the API Prices, with the reason and the standard.
Step 3 / 4

Fix the finding

Click Fix. Flow first says exactly what will happen — here the limit goes to 600 calls per minute per consumer — and only does it once you confirm. The fix goes into the audit log.

  1. Click Fix
Fix the finding · Click Fix
Fix the finding · What will happen: the limit goes to 600.
  1. Click Fix
Fix the finding · Click Fix
Fix the finding · The notice Resolved.
Step 4 / 4

Check the result

Open the API in the explorer. The plain-language explanation now gives the new limit of 600 calls per minute.

  1. Click the API
Check the result · Click the API
Check the result · The limit is 600 per minute.

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