Administer
Security
Two-factor sign-in, passkeys, SSO, encrypted credentials and the outbound network policy.
Sign-in
- Two-factor sign-in with an authenticator app, and passkeys or security keys. Owners can require two-factor for everyone.
- Google sign-in, single sign-on with SAML 2.0 or OpenID Connect (Business plan), and LDAP (Enterprise plan).
- New password accounts confirm their email address.
Credentials
- Encrypted with AES-256 before they're stored; secrets are never sent back to the browser.
- On the Enterprise plan, credentials can read secrets from an external store (such as a vault) instead of storing them.
Who can do what
Roles control what each member can see and change, and sharing can make workflows and credentials private.
Outbound network policy
Workflows can't reach private, loopback or link-local addresses (your internal network, cloud metadata services) unless an administrator allows specific hosts or ranges. This protects your servers from workflows that call unexpected URLs.
Code
The Code node runs in a sandbox with no network or file access, and with memory and time limits. Expressions are interpreted safely and never passed to eval.
Sensitive data in executions
On the Business plan, workflows can redact execution data so inputs and outputs aren't stored for production or manual runs.
Everything on record
Important actions are recorded in the audit log.