Workflows in practice
Bring every launch dependency to ready
Editorial Workflows
Run complex content operations as one coordinated system
Coordinate people, agents, and applications around your content, all within Sanity.
Content operations in Sanity
Coordinate the work around your content
Editorial Workflows gives people, agents, and applications shared process state around content in Sanity, with clear ownership, executable next steps, and durable history.
Make responsibility explicit
Represent stages, activities, assignments, and the decisions that move work forward.
Automate without surrendering judgment
Let applications and agents perform repeatable work, then route exceptions or consequential choices to people.
Coordinate related work
Bring parallel teams, content, assets, and dependent processes toward a shared readiness point.
Keep progress and history visible
Give interfaces and integrations the same workflow state, next actions, evaluation insights, and durable history.
Common coordination problems
Recognize the pattern. Shape the workflow.
See how Editorial Workflows makes ownership, decisions, and dependencies visible across complex content operations.
Designed for a composable stack
Let every participant work from the same process
The engine coordinates process state. Your content stays in the Content Lake, and each integration chooses the experience it needs.
Content teams in Sanity Studio
Show current stages, assignments, actions, and history beside the documents people already edit.
Teams in custom applications
Use reactive sessions and reusable controls to build purpose-specific workflow interfaces.
Services and operational tooling
Deploy definitions and drive workflows from servers or the CLI when work extends beyond an editor session.
Agents using defined tools
Let agents inspect and participate through MCP without inventing a separate process model.
Start small. Expand with confidence.
Choose one process worth improving
Begin with recurring work where coordination is slow, unclear, or spread across too many tools.
- Pick a process where several people or systems need to stay aligned.
- Agree on who owns each step and what must be true before work moves forward.
- Launch the simplest version, learn from real use, then add automation and more teams.
Start with a real process
Make the next handoff visible and executable
Explore the model, define the smallest useful workflow, and connect it to the surfaces where work already happens.