Maintain task classifications and shared queues

Purpose

Administrators organize work categories and the queues used by their teams.

How It Works

An administrator opens task type or queue configuration. They create a named entry or edit an existing one. A new entry normally joins the end of its list. Reordering supplies the entire list in one operation. Rhythm rejects a stale edit or a prohibited locked change. A type or queue referenced by tasks cannot be deleted. Deactivation keeps existing task references and still permits new work through the service. The queue screen also contains controls whose values have no stored behavior. The product should remove those controls or design their support before relying on them.

Relationships

Task recording selects a task type.
Task assignment uses queue references and arrival positions.
Platform responsibilities identify who oversees queue work.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Customer-defined categories and queuesConfiguration changes protected against stale savesIn-use records preserved
Surfaces: consoleapi
Intent sources: Andrew 2026-10-10 (configuration ids), recorded at services-crm:modules/tasks/db/task-configurations.tsservices-crm:docs/milestones/CRM-M8-activities-and-tasks.md#E-09

Controls

18 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-DAT-001 TC-DAT-003 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-TEN-001 TC-TEN-002 TC-TEN-003

Permissions

Key	Checked at	Scope
`crm.task-types.read`	api	tenant
`crm.task-types.create`	api	tenant
`crm.task-types.update`	api	tenant
`crm.task-types.delete`	api	tenant
`crm.task-types.bulk`	api	tenant
`crm.task-queues.read`	api	tenant
`crm.task-queues.create`	api	tenant
`crm.task-queues.update`	api	tenant
`crm.task-queues.delete`	api	tenant
`crm.task-queues.bulk`	api	tenant

Business Rules

10 rules, 9 to be proved before approval. A rule's product intent is derived from its origin: 3 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Readers can inspect task types and queues, while administrators maintain, reorder and delete them. no proof recorded yet	permission	api	test services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js#answers 403 to a caller who may only read task types
`02`must prove Proposed	Task types and queues use immutable configuration identifiers, derived from names when omitted and rejecting reserved or malformed values. origin: Andrew 2026-10-10 (configuration ids), recorded at services-crm:modules/tasks/db/task-configurations.ts no proof recorded yet	validation	service, database	test services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js#refuses an id that is not a configuration id, saying what an id may hold
`03`must prove Proposed	Task type and queue names are trimmed, nonblank, at most 100 characters and unique within their respective workspace lists. no proof recorded yet	validation	service, database	test services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js#refuses a create whose name another type of the tenant already has
`04`must prove Proposed	A referenced task type or queue cannot be deleted while any task still names it. no proof recorded yet	invariant	service, database	test services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js#refuses the delete of a task type a task is of (409)
`05`must prove Confirmed	Reordering supplies every list entry once, rejects incomplete or foreign lists without movement, and includes locked entries. origin: services-crm:docs/milestones/CRM-M8-activities-and-tasks.md#D-08 no proof recorded yet	validation	service	test services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js#refuses a list that leaves a type out, naming it, and moves no type at all
`06`must prove Proposed	New task types and queues append when no position is supplied, and their console forms omit that position. no proof recorded yet	calculation	service, console	test services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js#puts a create that states no display order at the end of the tenant’s list
`07`must prove Confirmed	Edits reject stale versions and full locks; replacement clears an omitted description and preserves an omitted position. origin: services-crm:docs/milestones/CRM-M1-contacts-and-organizations.md#D-05 no proof recorded yet	policy	api, service	test services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js#clears the description the replacement omitted
`08`must prove Proposed	Deactivating task configuration preserves existing references and does not prevent new tasks from using the inactive type or queue. no proof recorded yet	lifecycle	service	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0713.spec.ts#CRM-ACC-0713
`09`must prove Confirmed	The baseline supplies General, Follow-up, Call, Email and Meeting task types without overwriting customer edits and supplies no queues. origin: services-crm:docs/milestones/CRM-M8-activities-and-tasks.md#D-48 no proof recorded yet	policy	service	test services-crm:modules/tasks/tests/integration/services/persistence/task-types.integration.spec.js#adopts a record the tenant edited, which is what makes a seed a starting point
`10` Proposed	Queue configuration includes team, distribution, due-time and escalation controls that the service neither stores nor applies.	policy	console	observed react-console:lib/configuration/task-queues.ts:withUnperformedFields

Scenarios

Id	Given	When	Then	Provenance
`01`	An administrator creates a Site inspection task type.	Rename and reorder it, then attempt deletion while a task references it.	Reordering commits together and deletion of the used type fails.	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0713.spec.ts#CRM-ACC-0713

Edge Cases

Id	Given	When	Then	Provenance
`02`	Configuration inputs cover maximum names, longer names and malformed identifiers.	Save each variant.	Valid boundaries succeed and invalid fields produce refusals.	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0699.spec.ts#CRM-ACC-0699

Planning

Maintain task classifications and shared queues ​

Purpose ​

How It Works ​

Relationships ​