Companies

A company is lightweight context shared by work, not a CRM pipeline or owner boundary. Standalone tasks, process items and Orders can reference an owned company ID. Related IDs must belong to the same workspace. Name/code/contact/payment/notes properties are ordinary product context; customFields use configured keys and typed values. Read company field definitions/card visibility before constructing a replacement custom-value map.

Company fields support the schema's nine types with required presence, select options, finite numbers/currency, dates, boolean and owned company references. Table/card visibility does not make a required field optional. A false checkbox is a valid configured value. Company configuration and associations are versioned; send the documented company/configuration ETag and idempotency key.

Archiving a company does not archive related tasks, process items or Orders. The company leaves active pickers but existing work retains its association. Restore the company to make it active again. Do not emulate archival by deleting relationships.

A company future-order template must be an owned, published template in the Orders process, either unscoped or scoped to that company. An explicit order template wins; otherwise company default wins; otherwise the built-in Orders workflow is used. These settings affect future orders. Existing orders retain independent workflow copies. Editing the company's private template likewise does not retroactively change existing orders.

Permanent company deletion is separate from archive and requires its preview/confirmation and destructive scope. Inspect how links and private future-order configuration will be cleared; related work is not implicitly permission to delete that work. Use returned impact, not guessed cascade behavior. See archive/recover, fields, and order workflow.