Cadres IT Operations & Infrastructure
Products Architecture Docs Blog
Sheet SYN-12 Rev 2026.08
Start Trial

Sheet SYN-12 — Network Operations Manual

Governed Actions & Journeys

The action catalog with risk classes, journey automation with schedules and scope, the approval inbox, and signed exports.

Audience: Operators, approvers, and automation owners Focus: Change that waits for approval and leaves evidence

Scope

Operations is where Synapse changes things instead of observing them. This guide covers the governed action catalog, journey automation, the approval inbox, and the signed export endpoints that push data to downstream systems.

The action catalog

Every governed action is listed with a risk class badge (read, external-write, or device-write) and the specific permission it requires. Actions cover work such as rebooting a device, syncing an integration now, evaluating a compliance policy, generating a CSV report, changing device configuration through the collector, and pushing a signed export to a webhook endpoint. An action’s parameters render as a form generated from the action’s own schema, and the execute control only appears for an operator who holds both the blanket execute permission and that action’s own required permission: exactly what the platform enforces.

Journeys

A journey is a named sequence of catalog actions:

  • Steps pick actions and drive their parameters with the same schema-driven forms. A step can expand per device or per site across the journey’s scope, so “reboot every device at this site” is one step, not a hand-authored list.
  • Schedules run daily, weekly, or monthly, including nth-weekday forms such as the last Friday of the month.
  • Scope is the same organization, label, or site selector compliance policies use.
  • Saving validates the whole plan before it persists, so a bad action reference or an unresolvable scope surfaces at authoring time, never at run time.

A journey definition with run history cannot be deleted, only disabled: runs are audit history and stay reachable.

Approval and evidence

A run whose plan contains a device-write step, or whose journey requires approval, waits in the approval inbox instead of executing. Approving clears the gate; actually executing is a separate act under a separate permission, so approval and execution are never one keystroke.

Every run is a step timeline: per-step status, risk class, error text, and result evidence. For a configuration change, the run detail shows the live state of the collector round-trip and, once complete, the unified diff between the configuration before and after the change.

Signed webhook exports

Downstream systems (IP address management, configuration databases, business intelligence tooling) register an HTTPS endpoint and subscribe to export kinds such as inventory, compliance, and scores. Every delivery is signed so the receiver can verify its origin. The signing secret is revealed exactly once at creation and can be regenerated; a test-fire pushes a real signed delivery through the identical path; and delivery history records every attempt. An endpoint with delivery history is disabled rather than deleted, because deliveries are audit evidence.