Flow.Documentation

The security overview

8 steps± 6 minVideoVerified 22 Oct 2026
  1. Step 1 · Open your development environment
  2. Step 2 · Open the security overview
  3. Step 3 · See that the audit log is untouched
  4. Step 4 · Read a finding
  5. Step 5 · Fix it from the finding
  6. Step 6 · Check again: the score goes up
  7. Step 7 · Publish the home: the check looks along
  8. Step 8 · Or accept the risk, with a reason

What is open or weak in how your Flow is set up? The security overview finds out for you: open links, menus that show confidential data to everyone, workflows without requirements, keys without an end date, builders without two-step verification. Every finding says why it matters and opens the place where you fix it with one click. Before the home goes live, the same check looks along: something critical stops the publishing.

Watch the whole guide as a video8 steps in one film
Step 1 / 8

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

Open the security overview

Click Security in the bar on the left and choose Security. At the top is the score (100 is nothing found), the number of findings per severity and a score per module. Below are the findings, the most serious first. They are also in the Problems panel.

  1. Click Security
Open the security overview · Click Security
  1. Click Security
Open the security overview · Click Security
Open the security overview · The score (85), the findings per severity and per module.
Step 3 / 8

See that the audit log is untouched

Below the score is one line about the audit log. Every entry of the audit log is sealed with the entry before it: whoever changes, removes or moves something afterwards breaks that chain. 'Chain intact' means everything is still as it was recorded. If something changed, this line says at which number the chain breaks (never what it said). Only people who may read the audit log see this line.

See that the audit log is untouched · Audit log: chain intact, with the number of entries.
Step 4 / 8

Read a finding

The dashboard Weekly sales overview is open to anyone with the link: whoever has the link sees it without signing in, and a forwarded link cannot be taken back. Every finding says in plain words why it matters. The same link has no end date either: that is a second, lighter finding.

Read a finding · High: Dashboard is open to anyone with the link, with why it matters.
Step 5 / 8

Fix it from the finding

Click Fix it: the dashboard opens. Click Share and choose Colleagues in this environment: only people who may view dashboards in this environment still see it, with their own rights. The open link stops working at once.

  1. Click Fix it: Weekly sales overview
Fix it from the finding · Click Fix it: Weekly sales overview
  1. Click Share
Fix it from the finding · Click Share
  1. Click Colleagues in this environment
Fix it from the finding · Click Colleagues in this environment
  1. Click Apply
Fix it from the finding · Click Apply
Step 6 / 8

Check again: the score goes up

Back in the security overview, click Check again. The findings about the open link are gone and the score is higher.

  1. Click Security
Check again: the score goes up · Click Security
  1. Click Security
Check again: the score goes up · Click Security
  1. Click Check again
Check again: the score goes up · Click Check again
Check again: the score goes up · The score: from 85 to 100.
Step 7 / 8

Publish the home: the check looks along

In the explorer, under Home for colleagues, open Home and click Publish. First the check looks for anything left open. Here everyone's menu offers the HR colleague, who reads the confidential salary handbook: critical. Then you cannot just publish.

  1. Click Explorer
Publish the home: the check looks along · Click Explorer
  1. Click Home
Publish the home: the check looks along · Click Home
  1. Click Publish
Publish the home: the check looks along · Click Publish
Publish the home: the check looks along · Critical: everyone sees confidential data through the home. Publish anyway is off.
Step 8 / 8

Or accept the risk, with a reason

Best is to fix it: show the HR colleague only to the audience that needs it. If it really is intended, tick I accept the risk and write why. Only then is Publish anyway possible; who took the risk and why is in the audit log.

  1. Click I accept the risk
Or accept the risk, with a reason · Click I accept the risk
  1. In Why is this acceptable?, type Every employee may read their own pay scheme; agreed with HR.
Or accept the risk, with a reason · In Why is this acceptable?, type Every employee may read their own pay scheme; agreed with HR.
  1. Click Publish anyway
Or accept the risk, with a reason · Click Publish anyway
Or accept the risk, with a reason · Version 1 is published and active.

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