> ## Documentation Index
> Fetch the complete documentation index at: https://player-zero-drop-coordinator-docs-updates.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 stages like **Intake & Triage → RCA → Fix → Test → Document & 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.

***

## The Default Workflow

Every project starts with a five-stage defect resolution workflow:

| Stage                | Type     | Auto-approve | What Happens                                                                         |
| -------------------- | -------- | ------------ | ------------------------------------------------------------------------------------ |
| **Intake & Triage**  | Entry    | Yes          | Assess the issue, classify severity, gather context, check for known issues          |
| **RCA**              | Entry    | Yes          | Deep investigation — study codebase, generate hypotheses, run diagnostic simulations |
| **Fix**              | Work     | No           | Implement a surgical fix, verify with simulations                                    |
| **Test**             | Work     | No           | Comprehensive QA — happy path, edge cases, regression, security                      |
| **Document & Close** | Terminal | No           | Summarize the issue, document root cause and fix, capture learnings                  |

Triage and RCA auto-approve so the agent moves through them autonomously. Fix, Test, and Close require human approval — putting humans in the loop where high-stakes decisions happen.

Beyond the default, you can start a new workflow from a built-in template or build your own. See [Configuring Workflows](/features/configuring-workflows).

***

## 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. Filter by workflow, stage, approval status, ownership, and time range. Review threads inline and approve transitions 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