Configure activity types and the details they collect

Purpose

Administrators tailor interaction entry to the customer’s working practices.

How It Works

An administrator opens activity type configuration. They name the type and choose its icon, colour and starting behavior. Field modes shape the form for that type. Outcomes stay within the type’s own list. Saving the configuration uses the version the administrator read. Reordering changes the complete type list together. When a type or outcome has been used, deactivation provides the retirement path. Existing activities retain their earlier selections. The console’s duration and follow-up controls accept narrower ranges than the service, which remains a product consistency question.

Relationships

Activity logging uses the selected type and outcomes.
Baseline types provide the starting catalog.
Access controls reserve maintenance for administrators.

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: Useful choices for activity entryRetirement that preserves historical selectionsOrdered types and outcomes
Surfaces: consoleapijob
Intent sources: Andrew 2026-10-10 (configuration ids), recorded at services-crm:modules/tasks/db/task-configurations.ts

Controls

16 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-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003

Permissions

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

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Activity types are readable with reader permissions, while their creation, changes, reordering and deletion require administrator permissions. no proof recorded yet	permission	api	test services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses a type’s create to a caller who may only read types: 403
`02`must prove Proposed	An activity type has an immutable configuration identifier derived from its name when omitted, using lowercase letters, digits and single underscores with a leading letter and excluding the reserved reorder address. 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/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses the id order, the path of the reorder
`03`must prove Proposed	An activity type requires a workspace-unique name of at most 100 characters and permits a description of at most 1,000 characters. no proof recorded yet	validation	service, database	test services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses a name another type of the tenant has
`04`must prove Proposed	Subject, direction, duration, outcome, end time and attendees each have a hidden, optional or required field mode. no proof recorded yet	validation	database	test services-crm:modules/activities/tests/integration/db/activities.table.integration.spec.js#refuses a field mode other than hidden, optional or required
`05`must prove Proposed	Activity types choose Completed or Scheduled as the initial status, fixed icon and colour choices, an optional default duration of one to 1,440 minutes, and an optional follow-up interval of one to 365 days. no proof recorded yet	validation	service, database	test services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses a follow-up of 366 days, naming the field
`06`must prove Proposed	An activity type owns an ordered list of up to 50 uniquely named outcomes; supplying a list replaces it, while omitting the list preserves it. no proof recorded yet	policy	service, database	test services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#replaces the outcomes as a list: kept by id, created by name, removed when missing
`07`must prove Proposed	An outcome referenced by an activity and an activity type in use cannot be deleted; the refusal directs staff to deactivate instead. no proof recorded yet	invariant	service, database	test services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses to remove an outcome an activity has, saying to deactivate it instead
`08`must prove Proposed	Deactivation removes a type or outcome from new selections while retaining it on existing activities. no proof recorded yet	lifecycle	service	test services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#keeps an inactive type on an activity that already has it
`09`must prove Proposed	Reordering requires a complete list without duplicate or foreign-workspace entries and either moves all types or moves none. no proof recorded yet	validation	service	test services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#creates a type with its outcomes, lists it and puts the list in a new order
`10`must prove Proposed	A new activity type without an explicit position is appended to the list. no proof recorded yet	calculation	service	test services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#puts a create that states no display order at the end of the tenant’s list
`11`must prove Confirmed	An activity type edit uses the version read and is refused when stale or locked against updates. origin: services-crm:docs/milestones/CRM-M1-contacts-and-organizations.md#D-05 no proof recorded yet	validation	api, service	test services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses a version the type has moved on from
`12`must prove Proposed	The configuration screen accepts default durations from five to 480 minutes and follow-up intervals from one to 90 days, narrower than service limits. no proof recorded yet	validation	console	observed react-console:components/configuration/resources/activity-types.tsx:MIN_DURATION

Scenarios

Id	Given	When	Then	Provenance
`01`	Site visit has three outcomes and an activity using it.	Move the type upward, deactivate an outcome and attempt type deletion.	The list order changes, earlier outcome use remains, and deleting the used type is rejected.	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0698.spec.ts#CRM-ACC-0698

Edge Cases

Id	Given	When	Then	Provenance
`02`	Type input includes names at and beyond the length limit and a 366-day follow-up.	Save each configuration variant.	Boundary values succeed and out-of-range inputs identify their fields.	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0699.spec.ts#CRM-ACC-0699

Planning

Configure activity types and the details they collect ​

Purpose ​

How It Works ​

Relationships ​