Pipeline Templates curates the global stage/status bundle teams install into their own Pipeline. Select a template from the list to open its detail view.
Creating a template
Use the New pipeline template button (top-right of the page) to start one from scratch — name it and pick its Slug (auto-filled from the name, editable — this can't be changed later, so get it right here), then it opens straight into the detail view to add stages and statuses. The same button appears in the empty state before any templates exist yet.
Adding stages and statuses
A new template starts with zero stages. Use the Add stage button (below the stage list, or in the "No stages yet" empty state) to add one by name — a slug and short label are derived automatically. Within a stage, use its Add status button to add a status by name. Set a stage's color or a status's Terminal toggle and lifecycle mapping afterward using their existing controls (see "Editing stages and statuses" below). Publish stays disabled until the template has at least one stage.
Editing stages and statuses
Drag a stage or a status to reorder it. Hover a stage or status for a pencil icon to rename it inline; a stage also has an editable short label and a color picker. Each status has a Terminal toggle and a lifecycle select mapping it to the deal status it drives (or — None —).
A status also defaults to every deal type. Hover it and select the tag icon to scope it to specific canonical deal types instead — a scoped status shows a compact pill (like Wholesale · Novation); a Terminal status is always locked to all types, since it has to apply no matter which deal type reaches the end of the stage. Scoping maps to the installing team's own deal types automatically when they install or update the template. Use the View as picker above the stage list to preview what a given deal type sees in this template.
Publishing
Select Publish, optionally add a What changed note, and confirm. This bumps the template's version and notifies every team that's installed it — it does not change any team's own pipeline automatically. There's no per-team auto-apply for structural pipeline changes.