Security and governance you can demonstrate

Case history is write-once and protected at database level. Critical operations succeed only if the audit is recorded, otherwise they are rolled back in the same transaction. The activity log says who, when, through which channel and on what, including logins, failed attempts and two-step verification, with export up to 50,000 rows and retention from 30 days to 10 years.

The four roles, Admin, FlowDesigner, Operator and ReadOnly, are joined by folder permissions, from Optimize, which can only restrict, and by custom roles for who starts flows. Two-step verification is mandatory for administrators, with 10 recovery codes and per-device sessions. FlowSharp support always appears as such in the history and cannot create credentials.

For data retention, retention is distinct for completed cases, audit, AI call log and webhook receipts. Legal hold, in Enterprise, blocks retention, deletion and purge with a mandatory reason. Federation, white label and multi-tenant support partners and groups, with instantly revocable access. Enterprise Single Sign-On is coming soon. Deployment is EU SaaS or on-premise Docker, even air-gapped with a signed offline license.

For whoever must answer a client or a reviewer, the question is always the same: which function helps me demonstrate this requirement. Table in hand: for traceability you need immutable history and activity log; for minimization, Data Shield and data schema; for human oversight, fallback and start confirmation; for retention, retention settings and legal hold. Each row is a tool, not a guarantee.

On the operational side, many security choices are already in the default settings: keys have an expiry, exports are tracked, sensitive fields are masked for read-only users, and a critical action without a recorded audit is rolled back. The Admin does not have to remember to switch on prudence: they must decide where to loosen it, and every loosening leaves a trace that can be read back.