Seven Workflow Types Ship With Delivery Hub — Configure Your Process in Custom Metadata, Not Code

Most project management tools give you one workflow. Maybe two. Delivery Hub ships with seven, and the eighth one takes about fifteen minutes to build — without writing a line of Apex.

Why Seven?

Every team we've worked with does at least three different kinds of work simultaneously. The same Salesforce org runs software delivery, customer onboarding, change requests, and an internal IT queue. Forcing all of those into a single Kanban with the same stages is how spreadsheets win.

So we built the workflow engine around Custom Metadata from day one. Three CMT objects — WorkflowType__mdt, WorkflowStage__mdt, and WorkflowPersonaView__mdt — control every stage, color, persona view, transition, and gate. The Kanban board, the dashboards, the APIs, and the portal all read configuration from those records at runtime. Adding a workflow type is a metadata insert, not a code change.

The seven that ship today cover the most common patterns we kept seeing across implementations. Pick the closest one, customize it, or use it as a template for your own.

The Seven Workflow Types

Personas Are Half the Magic

Stages alone aren't enough. A 37-stage Software Delivery workflow is overwhelming if every user sees every column. Persona views collapse the board to what each role actually cares about.

A developer in Software Delivery sees Dev, Code Review, and Testing. A client sees Backlog, In Progress, UAT, and Done. A QA engineer sees Ready for QA, QA In Progress, and Ready for UAT. Same data, three completely different boards. None of it is hardcoded. WorkflowPersonaView__mdt records map a persona to a column name and the stages that roll up into that column.

Across the seven built-in workflow types there are 21+ persona views and 92 total stages. That's the surface area you get without configuring anything.

Building Your Own Takes 15 Minutes

If none of the seven fit, here's what creating an eighth looks like:

1. Add one WorkflowType__mdt record with your label, icon, and description.
2. Add a WorkflowStage__mdt record for each stage in your process. Each stage gets a display name, an API value, a card color, header colors, an owner persona, a phase, and forward + backtrack transition lists.
3. Add WorkflowPersonaView__mdt records to define what each persona sees on the board.
4. Set the WorkflowTypeTxt__c field on a Work Item to your new type. The board, dashboards, and APIs pick it up automatically.

No Apex changes. No LWC changes. No deployments. The board reads everything from @wire(getWorkflowConfig) at runtime, and dashboard cards live in their own CMT framework.

Why This Matters vs Jira/Asana/Monday

The big project management tools all ship one or two workflow types and lock the rest behind enterprise tiers. Custom workflows in Jira require admin access plus a paid plan plus a workflow scheme migration. Asana's rules engine is per-project. Monday.com's status columns are per-board. None of them are metadata-driven the way Salesforce admins expect.

Delivery Hub treats workflow configuration the same way every other Salesforce admin task works: open Setup, add some metadata, done. And because it's all metadata, your workflows participate in source control, change sets, and unmanaged-package deploys like everything else in your org.

How to Try It

Install Delivery Hub into a sandbox or scratch org. The seven workflow types install with the package. Open the Kanban board, switch the workflow picker to any of the seven, and the columns reconfigure instantly. Drop a Work Item on the board with WorkflowTypeTxt__c = Operations and you'll see the IT service desk view. Switch it to Change_Management and you'll see the CAB Review flow. No restart, no rebuild, no deploy.

For the full breakdown of every stage and persona in every workflow, see the workflow types reference page. For the technical details on the CMT data model, read the platform docs.

All seven workflow types are part of the free Delivery Hub package. There is no paid tier. There is no per-seat fee. The workflow engine, the seven types, the 92 stages, the 21 personas — all of it ships in the same managed package every other Delivery Hub feature lives in.