> ## 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. # Create a Track > Build multi-step workflows for onboarding, training, and recurring processes. Tracks are automated workflows that guide users through a sequence of steps - messages, quizzes, surveys, tasks, introductions, and more. Perfect for onboarding, training, and recurring processes. Anyone can create a Track, and a Track can be edited by an Owner or by anyone added as an admin of that Track. Activating a Track requires an Owner or Manager. Cohort Tracks are managed by their cohort program's editors - see [Cohort](/tracks/triggers/cohort). *** ## 🚀 Getting Started 1. Go to [doozy.live/app](https://doozy.live/app) and open **Tracks** 2. Click to create a new track 3. Either **describe your track to the AI builder** (it drafts the steps and timing for you to review) or choose **Build manually** 4. Set a trigger, add steps, then save or activate The more you tell the builder about how your team actually works, the more of the track is yours rather than generic. Where it has to fall back on general knowledge of the topic it says so in its reply, and names what it was missing, so you know what to send. For a quiz, survey, or poll step, the AI builder first checks whether your account already has one that clearly fits - anything you could already pick by hand from your library (your own active quizzes and scheduled surveys/polls, each with real questions in them). On a confident match it attaches that instead of writing new content, and names it in its reply; anything less certain writes fresh content, same as before. Remove the activity from its step to bring back the picker and choose something else, or tell the AI to write new content and it'll skip your library for that track. The same item is never reused twice in one track, and editing a reused item updates it everywhere it's used. *** ## 🧱 The Track Builder A track is built on a visual canvas: a **trigger** at the top, followed by a sequence of **steps** connected in a flow. Give your track a **name** (and an optional description) in the builder. ### 1. Choose a trigger The trigger decides how people enter the track. Pick one: | Trigger | Description | | - | - | | **First day** | Runs on someone's first day, once they've joined Slack | | **Manual enrollment** | You enroll people yourself, from the dashboard or via the API | | **On a schedule** | Runs on a recurring schedule for a chosen set of people | | **Work anniversary** | Runs around people's work anniversaries | | **Cohort** | Runs when a cohort opens or when people join it - attach it from the trigger picker or from a cohort program's page while the track is a draft; once it's live, the program and run mode lock | You can also turn on **Allow people to self-join this track**, and use **Advanced filters** to limit who enters by group, country, work location, or manager status. [Learn more about triggers →](/tracks/triggers/overview) ### 2. Add steps Add steps with the **+** button on the canvas. Steps are grouped by purpose: | Group | Steps | | - | - | | **Communication** | Message | | **Activities** | Quiz, Survey, Poll, Tasks | | **People** | Introductions, Mentor Assignment | | **Automation** | Add to Track, Webhook | Each step has a **destination** (who receives it) and its own settings. Reorder steps on the canvas to control the flow. A track can include only one Mentor Assignment step. [Learn more about step types →](/tracks/steps/overview) ### 3. Set the timing Every step runs on a day of the track (Day 1, Day 7) at a **send time** shown next to its title (9:00 AM by default). Click the **+** between steps and choose **Send on a day** to start a new day; day dividers group the steps on the canvas. Days count the Track's **working days** (Monday to Friday by default), so steps skip any day the Track does not run. Day 1 is the member's first day on the Track. New Tracks use the workspace's working days and hours unless you override them. A legacy Track with no `working_hours` keeps its previous working days while inheriting the workspace (or default) hours. Working days and overdue catch-up hours use each recipient's time zone. If a recipient has no time zone, Doozy uses the default timezone in the policy. Working hours do not move a future step's send time. See [Step timing](/tracks/steps/timing) for defaults, time zone behavior, and validation. ### 4. Save or activate The builder has two actions: * **Save Draft** - saves your track without running it * **Activate** - validates the track and makes it live so it starts triggering for users Editing an active track that already has people partway through it applies your changes to them as they reach their next step. For larger changes, duplicate the track instead so current enrollees finish the version they started. *** ## ⚙️ Managing a track Open a track from the **Tracks** list to reach its detail page, where you can: * **Edit** the track in the builder * **Pause** and **Resume** it. Pausing stops anyone new being added; people already part-way through finish their remaining steps, and a cohort track's running cohorts deliver to the end. To stop a track for everyone, including those mid-track, archive it instead * **Archive**, **Duplicate**, or **Delete** it. Archiving a track attached to a [cohort program](/cohorts/overview) warns you first, naming the program (see [Cohort](/tracks/triggers/cohort#attach-a-track-to-a-cohort-program)) * Manage **Admins** - other people who can manage the track * **Enroll users** manually and view each enrollee's progress *** ## 📋 Example: Onboarding Track | Day | Step | Description | | - | - | - | | Day 1 | Message | Welcome message with first-day info | | Day 1 | Introductions | Connect with their buddy | | Day 3 | Poll | "How's your first week going?" | | Day 7 | Survey | First week feedback survey | | Day 14 | Tasks | Complete compliance training | | Day 30 | Survey | 30-day check-in | *** ## ⭐ Best Practices | Practice | Why It Works | | - | - | | **Start simple** | Begin with a few steps and add more over time | | **Space steps across days** | Pace steps so users aren't overwhelmed | | **Review before activating** | Read the track top to bottom and check the flow end to end | | **Keep content fresh** | Review and update tracks regularly | | **Assign multiple admins** | Ensure continuity if someone leaves | *** ## 🔗 Related How users enter tracks All available step types Monitor user progress through tracks Manually add users to a track This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.