At a glance

The small set of concepts behind Editorial Workflows, and how they fit together.

Editorial Workflows turns content processes into data that people, agents, and applications can operate consistently.

Editorial Workflows is organization-wide by design. One workflow can coordinate content across projects, datasets, Canvas, and Media Library through global document references.

• Engine: the TypeScript library that evaluates and commits workflow instances.
• Definitions and instances: a definition describes a process; an instance is one run of it.
• Stages and transitions: stages mark where an instance is; transitions define where it can move.
• Fields: data carried by an instance, such as its subject, reviewer, or approval.
• Activities and actions: activities model work associated with a stage; actions are caller-fired or triggered events.
• Conditions and operations: conditions control gates and movement; operations describe state changes.
• Effects and runtimes: effects queue external work; runtimes complete it.
• Guards and enforcement: guards declare rules enforced by the Content Lake.
• Subworkflows: compose a larger process from smaller workflow definitions.
• Global document references: connect workflow instances to content across projects, datasets, and other Sanity resources.
• The reactive session: the live application layer used by App SDK and Studio experiences.

The engine is a TypeScript library, not a hosted service. It owns the workflow domain model and commits every change to an instance through explicit verbs.

The CLI and MCP server operate the engine directly. The App SDK layer supplies reactive document access, and the Studio plugin sits on top of that layer to provide the Editorial Workflows interface.

A definition describes a process; an instance is one run, currently in one stage. Actions change its state, and transitions move it when their conditions hold. The engine continues that cascade until the instance settles.

Conditions express decisions in GROQ. Effects queue external work for a runtime. Guards deploy rules to the Content Lake. Reactive sessions keep application experiences current.

Choose what you need next:

• Getting started: deploy and run your first workflow.
• Cookbook: adapt complete workflow examples.
• Reference: look up exact types, fields, defaults, and engine verbs.