Cohorts

A cohort is a named group of participants inside a tenant. It has its own sign-up code and picture, and shares everything else with its tenant: content, colours, tabs, administrators and default journeys. A journey can branch on it (cohort in a condition), which is how a cohort gets its own programme.

• code is fixed once created, and is how a bulk invitation names the cohort each row joins.
• signupCode (1 to 20 letters, numbers, - and _, stored in capitals) builds the cohort's sign-up link, signupUrl, worked out on every read. Codes are one pool with the tenants', so a code used anywhere is refused here. No code, no link.
• Archiving closes the link and changes nothing else; nobody is removed.
• A cohort with participants can't be deleted (cohort_in_use).
• A participant's cohort is set when they join: the link they followed, or the invitation's cohort. A journey's updateUser action moves them or unassigns their cohort; moving gives them no journeys, and a branch already taken stays taken.

Cohorts from an outside list

The cohorts.source configuration names a feed of companies ({ adapter, url, authHeader? }), and a daily job keeps the tenant's cohorts in step with it: a new entry becomes a cohort with a generated sign-up code and its externalId; one that leaves is archived, never deleted; one that returns is reported for a person to look at rather than reopened. The feed owns the name and nothing else. A feed that can't be read, or that would archive an unusually large share of the active cohorts, applies nothing and reports instead.