Merged
Size
M
Change Breakdown
Feature70%
Security20%
Testing10%
#28001feat(editor): Put data redaction settings behind enterprise license

Workflow data redaction gated behind enterprise license

Workflow data redaction settings now require an enterprise license. Without it, the options are visible but disabled with an upgrade prompt.

Workflow data redaction settings are now protected by an enterprise license. When the dataRedaction license feature is not active, the redaction policy dropdowns remain visible in workflow settings but are greyed out and disabled. An "Upgrade" badge appears next to each setting, clicking it navigates users to the pricing page on self-hosted deployments or the billing page in cloud environments.

On the backend, any attempts to create or update workflows with a redaction policy are silently stripped when the license is absent. The execution redaction service also returns a 'none' policy when unlicensed, ensuring consistent behavior throughout the system. This approach mirrors the existing scope check pattern used elsewhere in the codebase.

The change affects both the CLI backend services handling workflow operations and the frontend editor where users configure their workflows.

View Original GitHub Description

Summary

Add enterprise license gating to workflow data redaction settings. When the dataRedaction license feature is not active:

  • Backend: Silently strips redactionPolicy from workflow update/create payloads (same pattern as the existing scope check)
  • Frontend: Shows both redaction rows greyed out with disabled dropdowns and an "Upgrade" pill badge next to each label. Clicking the badge navigates to the pricing page (self-hosted) or billing page (cloud).

When the license is active, everything renders normally with no badge.

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/IAM-516

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)
© 2026 · via Gitpulse