> ## Documentation Index > Fetch the complete documentation index at: https://player-zero-slack-mcp-docs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Workflows Overview > Define multi-stage pipelines that govern how PlayerZero agents process work — with structured stages, transition rules, and human approval gates. ## What Is a Workflow? A Workflow is a customizable, multi-stage pipeline that controls how a PlayerZero agent processes work from start to finish. You define the stages, the allowed paths between them, and the rules that control progression. When a channel enters a workflow, it moves through the stages you have defined — for example intake, investigation, resolution, and close. Each stage will operate across one or more agent threads. Each thread receives workflow-specific instructions, performs its work, and then requests permission to advance. The most recent thread in the channel acts as the controlling thread that manages transitions to the next stage. Transitions can be auto-approved or gated behind human review. *** ## Multiple Workflows per Project A project can define **multiple workflows**, each modeling a distinct process — for example, support triage, engineering scoping, QA testing, or SRE response. Manage them from **Project Settings → Workflows**. Each workflow is **versioned**. You edit a draft, publish it when ready, and PlayerZero keeps the full version history so you can **roll back** to a previous published version at any time. The inbox, monitors, and ticketing all resolve against the published version of a workflow. *** ## Core Concepts ### Stages A stage is a node in the workflow graph. Each stage has a **name**, **instructions** that tell the agent what to do, a **type** (Entry, Work, or Terminal), and configuration for approvals and archival. * **Entry** stages are where work begins * **Work** stages are intermediate processing steps * **Terminal** stages are where work concludes ### Transitions Transitions are the allowed paths between stages. Each transition includes a target stage and conditions describing when the agent should take that path. Transitions are validated at runtime — the agent can only move to stages explicitly defined as valid next steps. The channel sidebar surfaces these as the **Possible next stages** for the current thread. ### Approvals When the agent completes work in a stage, it requests to move on. Depending on configuration: * **Auto-approve**: The agent transitions immediately without human intervention * **Manual approval**: A human reviews the completed work and approves the transition, optionally leaving notes for the agent Approval means accepting the work done in the current stage — confirming that the agent's output meets your expectations before it moves to the next step. ### Archival Completed threads can be archived manually or automatically after a configurable number of days. Archived threads can be restored at any time. *** ## Workflow Templates Every organization gets workflow templates out of the box, so you can start from a structured process instead of a blank canvas. The templates available today are Documentation, Engineering Scoping, L1 Support, PR Review, Product Scoping, QA Testing, and SRE Alert Response. Pick the template closest to the work, and save to create a draft. Then edit it directly, or adjust its stages to fit how your team operates using the **Improve** button to trigger an interactive Player chat that can guide you through customizing the workflow to your needs. PlayerZero's Support team also publishes new and updated templates over time, and you choose whether to take an update when one is released. For how to create a workflow from a template, and the rest of the builder, see [Configuring Workflows](/features/configuring-workflows). *** ## Default Workflows Project owners can mark one workflow as the **default** for each team role — Engineering, Support, Product, and so on. When someone starts work, the default for their role is already selected, so the intended process runs without anyone hunting for it. Your own choice is remembered per project and per role. If you take on a new role, that role's default applies until you pick something else, and **Reset to Default** clears your choice whenever you want to go back. *** ## Two Surfaces ### The Workflow Builder Design workflows using a visual drag-and-drop graph editor. Add stages, draw connections between them, configure transition rules, and export/import workflows across projects. ### The Workflow Inbox Manage active work across your team. Curate a sidebar of the workflow inboxes you care about, review work grouped by channel, and approve stage advances without leaving the inbox. [Learn more →](/features/workflow-inbox) *** ## Get Started * [Configuring Workflows](/features/configuring-workflows) — Set up stages, transitions, approvals, and archival * [Workflow Inbox](/features/workflow-inbox) — Manage active threads, approve transitions, and review work * [Usage Analytics](/features/additional-features/usage-analytics) — Track workflow activity and export usage data