Skip to main content
Permissions are derived from the saved workflow revision. They are not granted by hiding a button or trusting node prose.
Permission summary

Review boundaries

  • File nodes and downloads use paths chosen through operating-system pickers.
  • HTTP and browser work declare network destinations.
  • Browser sessions use specific managed profile IDs.
  • Run Command declares the executable separately from its argument array.
  • Python and JavaScript Code nodes in run mode use the same command-execution boundary. A material source edit revokes the previous approval.
  • Schedule, file-watch, and Gmail triggers require background execution.
  • Gmail, Discord, Slack, and plugin external actions require communication review.
Source-mode Code nodes do not execute their contents. Web Builder starts a server bound only to 127.0.0.1; it is local-only and is replaced when the same node runs again.

Revision-bound approval

Changing a material setting can revoke the matching approval. This prevents an approved harmless revision from being edited into a broader one without another review. Imports and templates remain disabled until their boundaries are chosen locally.
A connection reference grants access only through the provider operations implemented for that node. It never exposes the underlying OAuth token or webhook URL to workflow data.