Skip to main content
FlowFn
IntegrationsTemplatesPricingDocsBlogSign inStart free
All documentation

Form content moderation

UpdatedJun 1, 2026Reading time2 min read

FlowFn screens every public-facing form for content that violates the platform's Acceptable Use Policy and Content Moderation Policy. The check looks at the parts of the form you author — title, description, the success / response message, every section title and field label, dropdown options, the consent text, and the welcome & success screen copy.

When the check runs

  • On create and on save, whenever you edit any of the authored fields above.
  • On a background sweep, so forms stay in sync with policy as the platform evolves.
  • When you make the form public or enable embed. If the cached verdict says the form is blocked, the toggle is refused with a moderation reason.

What the verdict can be

  • Low — nothing of concern. The form works normally.
  • Medium — flagged for internal admin review. You can keep editing; the form still works.
  • High — policy violation detected. The form is taken off public surfaces automatically: it is set back to private and embed is disabled. You still see the form in your dashboard and can edit it.
  • Admin blocked — an admin manually blocked the form. Same effect as high, but only an admin can lift it.
  • Admin approved — an admin manually cleared the form. AI re-evaluations no longer flip the verdict back.

If your form is blocked

When a form is flagged high or admin-blocked, attempts to make it public (or enable embed) are refused with the moderation reason. Edit the flagged content, save, and the AI re-checks it — if the issue is resolved, the block clears on its own. For an admin block, contact support.

Notes

  • Form submissions (what your visitors enter) are not screened by this check — it only evaluates the form you authored. You remain responsible for the data your form collects under the Acceptable Use Policy.
  • The check uses the same evaluator the platform applies to workflows, agents, and playgrounds, so the rules and categories stay consistent across every surface.
  • The feature is opt-in per deployment. Where it's enabled, existing forms are evaluated by the background sweep on their next pass.

Spotted an issue or have feedback?

support@flowfn.com
Back to docs hub →