> ## Documentation Index
> Fetch the complete documentation index at: https://help.doozy.live/llms.txt
> Use this file to discover all available pages before exploring further.
# Cohorts: Run onboarding and learning in groups
> Group people who start together into cohorts, and run tracks for the whole group and for each person.
**Cohorts** group people who start around the same time, such as an onboarding
intake, a training group, or a bootcamp, so they move through the experience
together. You describe how cohorts should form once, and Doozy creates each one,
fills it with the right people, opens its Slack channel if you want one, and runs
your tracks.
Cohorts is rolling out gradually. Once it's enabled for your workspace, admins
and managers see **Cohorts** in the dashboard menu. Everyone else sees it once
they're on a program's [People list](/cohorts/set-up-cohorts#people). If your
workspace doesn't have cohorts yet, contact
[support@doozy.live](mailto:support@doozy.live) to get it enabled.
## How the pieces fit together
There are three layers:
| Layer | Example | What it is |
| ------------------ | ------------------------------------- | -------------------------------------------------------------------------------------------------- |
| **Cohort program** | "Engineering onboarding" | The container: how cohorts form, whether they get a channel, who facilitates, and which tracks run |
| **Cohort** | "Jul 14, 2026" | One group of people whose start dates fall in the same range |
| **Tracks** | "Week 1 kickoff", "Security training" | What actually happens, attached to the program with the [Cohort](/tracks/triggers/cohort) trigger |
A program creates a new cohort on the schedule you choose, or you create each one
yourself. Every cohort runs the same tracks.
## Two kinds of cohort tracks
| Track | Run mode | Use it for |
| -------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cohort track** | Once per cohort | Shared moments: a kickoff message in the cohort channel, weekly group content, a shared quiz |
| **Per-person track** | For each person | Individual journeys: onboarding sequences, check-ins, and quizzes delivered by DM, timed from the cohort's start in each person's own timezone |
A program can mix both. See [Cohort](/tracks/triggers/cohort) for how run modes
work in the track builder.
## Who can do what
Workspace admins and managers can create a cohort program, and the creator
becomes its admin. From there, access is granted per program through the
**People** list on the program's page:
* Each person on the list is a **viewer**, an **editor**, or an **admin**. See
[the People list](/cohorts/set-up-cohorts#people) for what each role can do.
* **Workspace admins** see and manage every program without being on its People
list. That is the only blanket access. Workspace **managers** get no implicit
access to programs they didn't create: like everyone else, they see one only
once they're added to its People list.
* **Facilitators** are the people in each cohort's Slack channel supporting the
group. That's a channel setting on the People list, not an access level. See
[Facilitators](/cohorts/facilitators).
## Get started
Create a program: membership, schedule, and channel
Attach tracks that run once per cohort or for each person
Put the people running each cohort in its channel
Group people by their real start dates