Automations
Automations settings and access
Workspace defaults for new automations, catalog visibility, dry-run safety, retention — and who can build, run and stop automations.
On this page
Automations settings control how the workspace builds and keeps automations. One control — the emergency stop — is the Owner’s alone.
- Change settings
- any member of the workspace
- Pause or resume every automation
- Owner only
The settings#
| Section | What it controls |
|---|---|
| Workspace Defaults | Whether Create starts a rule (Linear Rule Builder) or a flow (Visual Flow Canvas), and which page Automations opens on |
| Catalog & Tool Visibility | Whether alpha and planned tools appear in the step palette. Turn them off to show only what runs |
| Flow Canvas Behavior | Zoom, node placement and editor defaults |
| Workspace Preferences | The preferred template category and the window the Overview’s metrics cover (7 days by default) |
| Diagnostics & Audit Logs | How much detail the Overview and run logs show, including whether runs show payload excerpts |
| Data Retention Policies | How long runs are kept (30 days by default) and how many saved versions each automation keeps (50) |
| Rotation & Automated Maintenance | How often webhook tokens should be rotated (30 days) and whether old data is pruned automatically |
Emergency stop#
The Emergency Organization Kill Switch, under Security & Emergency, pauses every automation in the organization at once: no triggers fire and no flows run. A banner tells everyone “Automations are currently PAUSED organization-wide”, and the Owner resumes them with Resume Automations.
Use it when an automation is misbehaving — sending too many messages, say — and you need everything to stop while you find which one.
Who can do what#
Automations belong to the workspace, not to a person. Any member can see, build, change and turn off any automation, and change these settings. Each automation records who created and last changed it. There is no Automations permission in Admin → Access yet.