> ## 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.

# First Day Trigger

> Run onboarding tracks on someone's first day, once they've joined Slack.

The **First day** trigger runs a track on someone's first day, once they've joined
Slack. It's the standard way to start onboarding automatically, so every new joiner
gets the same welcome without anyone having to remember to enroll them.

<Note>
  This trigger used to be called "User Joined". It's the same trigger, with the
  first-day behavior described below.
</Note>

## How the first day is decided

What counts as someone's first day depends on whether you have an
[HRIS connected](/integrations/how-to-connect-my-hris):

### With an HRIS connected

Start dates come from your HRIS, and the track waits for **both** of these before it
runs:

1. The person's **start date** has arrived
2. The person has **joined Slack**

Whichever happens second releases the track:

| Order of events | When the track runs |
| - | - |
| Joins Slack early, then their start date arrives | On their start date |
| Start date passes, then they join Slack | The day they join Slack |

This means onboarding never fires for someone who was added to your HRIS but hasn't
started yet, and never silently skips someone who joined Slack a few days late. If a
person's start date passes and they still haven't joined Slack, Doozy holds their
enrollment and starts the track when they join.

### Without an HRIS

The day someone joins Slack is their first day, and joining Slack alone triggers the
track.

## Day 1 is the day they're enrolled

The track starts when the person is enrolled, and that day is **Day 1** for them:
the later of their start date and the day they join Slack. [Day-scheduled
steps](/tracks/steps/timing) count from Day 1:

* Someone added later, such as a new hire who joins Slack a week late, or a tenured
  employee added by hand, simply begins at Day 1 when they enroll. Earlier days
  never stack up and arrive at once.
* Each step's send time is evaluated in the member's timezone. Working days
  determine when a future step can run. Start and end times can delay overdue
  catch-up until the next opening.

## Seeing who's waiting

The First day trigger's configuration panel in the track builder shows both halves of
this picture:

* **Where start dates come from** - the name of your connected HRIS, or a note that
  first day means the day someone joins Slack when no HRIS is connected
* **Who's waiting** - people whose start date has arrived but who haven't joined
  Slack yet, for example "2 people are waiting: in Workday but not yet in Slack"

People whose start date has passed stay in the waiting list (it shows anyone up to
90 days past their start date), so nobody quietly falls through the gap between your
HRIS and your workspace. Their enrollment stays held either way: the track runs when
they join Slack.

## Getting started

To set up a First day trigger:

1. Go to [doozy.live/app](https://doozy.live/app) and open **Tracks**
2. Create a new track
3. Select the first-day trigger - the card reads **New Hire** when an HRIS is
   connected, and **User added to Slack** when one isn't
4. Check the panel below the trigger cards to confirm where start dates come from
5. Add your onboarding steps and activate the track

## Targeting the right people

Use **Advanced filters** on the trigger to limit who enters the track by group,
country, work location, or manager status. For example, run one onboarding track for
managers and another for individual contributors, or a separate track per department.

<Tip>
  Connect your HRIS (like Workday, BambooHR, or Personio) so start dates,
  departments, and manager relationships are accurate from day one.
</Tip>

## Common use cases

* **New hire onboarding**: Welcome messages, introductions, and first-week tasks
* **30/60/90 day check-ins**: Surveys scheduled on Day 30, 60, and 90 of the track
* **Compliance and policy training**: Required reading and quizzes for every new joiner
* **Team connection**: Introductions and buddy assignments as soon as someone arrives

<Note>
  Onboarding classes that should move through content **together** are a better
  fit for [cohorts](/cohorts/overview) - group people who start in the same
  window and run tracks per cohort.
</Note>

<Note>
  Want to reach new hires **before** their first day, while they're still off
  Slack? See [Preboarding](/preboarding/overview) - it adds before-first-day
  steps, then hands them off to this trigger on day one. Because the hire isn't
  in Slack yet, only some step types can run before the first day; see
  [Preboarding in tracks](/preboarding/overview#preboarding-in-tracks) for which
  ones.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.