Skip to main content
Flow settings live under the Settings icon in the top-right of the canvas. Anything set here applies to every Agent, every Tool, every run — unless the block overrides it.

​
Global limits

Cap resource usage across the whole Flow:
  • Global max turns — the total tool-call round-trips allowed in a single run. Sums across every Agent block.
  • Global max tokens — total model tokens per run.
  • Global max cost (USD) — hard ceiling per run in dollars.
  • Global timeout — max wall-clock time before a run is aborted.
Per-block limits override globals when they’re stricter. Globals win when they’re stricter.

​
Default model

The model new Agent blocks pick up by default. Existing Agents keep their explicit choice.

​
Approvals defaults

  • Require approval for new Actions — when on, any Action added to the Flow starts with approvals required. Team hardens this for high-risk Flows.
  • Approval webhook URL — where approval requests are POSTed if you want to review outside Nora (Slack bot, custom queue). See Approvals.

​
Session memory defaults

Controls how much conversation history the Flow’s chat interface remembers:
  • Turns to keep — sliding window.
  • Summary strategy — after the window fills, older turns are summarized rather than dropped. Off / rolling / on-overflow.

​
Variables

Flow-level variables are named values available in every block (via {vars.NAME}). Use for:
  • Environment strings ({vars.SUPPORT_EMAIL})
  • Tunable prompts ({vars.TONE_PROFILE})
  • Feature flags ({vars.SHOW_DEBUG_INFO})
Variables have a name, type, default, and optional description. Draft and Published each carry their own values, so you can rehearse changes in Draft.

​
Access

  • Editors — who can change the Draft. Owners and Managers by default.
  • Publishers — who can push a Publish. Owners and Managers only, by default.
  • Runners — who can trigger runs. All workspace members by default.
  • Public link — surfaces the Flow as an unauthenticated chat URL. Off by default.

​
Data retention

How long Traces from this Flow are kept:
  • Trace retention — days. Default 90. Longer requires an Enterprise plan.
  • Payload retention — how long the full Trace payloads (prompts, tool arguments, tool responses) stay attached. Shorter values keep metadata but scrub payloads. Useful for regulated workloads.

​
Danger zone

  • Archive — hides the Flow from lists. All published versions keep running until you unpublish.
  • Delete — permanent after a 7-day grace period. Deletes Draft, Traces, and unpublished versions. Published versions remain reachable by ID.