Workflow Settings: Choose the Path, Don’t Redraw It

The workflow engine (see the workflows category) runs on definitions that say which stages exist, what completes them and what they generate. /settings/core/workflows is the tenant-facing view of those definitions: which preset paths are switched on for this organization, and which one new contracts get by default. It is a picker, not a drawing board.

Presets

The platform ships eight preset workflows: Standard ITAD, Lease Return Processing, Data Destruction Only, Recycle Only, Buyback / Trade-in, Broker / Resale, Refurbishment Workshop and Logistics Only. Each covers a recognizable shape of ITAD work — Standard ITAD walks from collection through receiving, diagnostics, erasure, inspection and grading to listing, shipping and settlement; Lease Return adds a manifest check and a charge-back calculation; Data Destruction Only stops at the certificate and the disposition. The list page shows counts for presets, enabled workflows, stages and actions, so the operations lead can see the size of what they are switching on.

Enable, disable, default

The tenant’s choices are exactly three: enable or disable a preset, choose one enabled preset as the default, and save. A disabled preset stays visible in Settings for reference but stops being a valid choice in new operational work, which is the general rule for tenant settings — a switched-off option may exist for administration, never as a live pick. There is no duplicate, no edit, no extra stage between testing and grading. The engine keeps the definitions consistent across every contract precisely because nobody can hand-tune one of them on a Tuesday.

Workflow detail

/settings/core/workflows/[id] inspects one preset before you make it the default: its stages, required and optional actions, exit conditions, SLA information, role assignment, applicable categories, the companies using it, active assets per stage, the actions in use and an SLA breakdown. Read it before you promote it. A default workflow is a promise your floor makes to every new contract.

Default means new contracts

The default workflow is applied to new contracts for as long as it is enabled. Inbound orders and received assets under that contract then follow the workflow saved on the contract. Change the default later and existing contracts do not quietly change with it; the workflow written on a contract is the one it keeps. /core/contracts/[slug] shows the assigned workflow. One setting. New contracts only. Old promises kept.