Workflows overview
Understand visual, step-based workflows that admins build and members run.
A workflow is a visual, step-based map of how a piece of work gets done. Admins build workflows on a canvas, publish them, and members open them as a guided reference for the process.
What a workflow is made of
Each workflow is a set of steps laid out on a canvas and connected with arrows.
Every step has a step type that says who or what carries it out:
- Human — a person does the work.
- AI-assisted — a person does the work with AI help.
- AI Agent — an agent runs the step, with a person who owns it.
- Automation — an automated process runs the step, with a person who maintains it.
Beyond the type, a step can carry the context needed to actually run it:
- A description written in rich text, explaining what the step is and how to do it.
- A Data needed list — the inputs the step depends on.
- An assignee (or, for AI Agent and Automation steps, an owner), chosen from your team.
- The tools the step uses.
- Files attached to the step — pasted text or uploaded text and code files, such as prompts, scripts, or agent setup — so the details live inside the process itself.
Steps are connected with arrows to show order. Arrows can run in sequence, branch in parallel, or loop back to an earlier step.
Building and publishing (admins)
Admins create a workflow, give it a title, and optionally file it under a department. They add steps on the canvas, set each step's type and details, and connect them with arrows.
A workflow starts as a draft, visible only to its author while it's being shaped. When it's ready, an admin publishes it, which makes it visible to the whole company. Publishing can be reversed by unpublishing, which returns the workflow to a draft.
The workflow's detail view shows a summary — how many steps it has, a breakdown by step type, and who last edited it.
Building, editing, publishing, and deleting workflows are admin-only actions. These limits are enforced by the system, not just hidden in the UI.
Running a workflow (members)
Members open the Workflows area to browse published workflows and open any one as a map. Members see the same canvas and step details as admins, but read-only — they can't change the workflow. Drafts never appear to members; only published workflows do.
A published workflow gives a member a guided process to follow instead of a blank starting point.
Reuse and sharing
Two features help you reuse and share work instead of rebuilding it: