# Example: onboard a new hire (video)

A video of one onboarding from start to finish: a new hire added in Rippling starts an automation that sets up their accounts, waits for an admin to approve the access steps, and tells IT in Slack.

Watch one onboarding from start to finish. Your HR team adds a new hire in Rippling, and the **New hire onboarding** automation does the rest, with an admin approving the steps that change access. This example has no setup steps: to build the automation, see [Automations](https://www.tryrisotto.com/docs/dashboard/automations), and to connect Rippling, see [Rippling](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/rippling).

[Video: Example: onboard a new hire](https://media.tryrisotto.com/videos/onboarding-desktop.mp4)

The automation is the [New hire onboarding](https://www.tryrisotto.com/library/automations/rippling-new-hire-onboarding) example from the library. It starts on Rippling's **Employee created** trigger and asks for approval on **Destructive changes**.

## What happens

1. **HR adds the new hire in Rippling**

   Northwind's HR team adds Maya Okafor in Rippling, with her work email, her
   department (Engineering) and her start date. Rippling sends events only for
   employees with access to Risotto in Rippling. See [Automation
   triggers](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/rippling#automation-triggers).

2. **The automation starts**

   About five minutes later, Rippling sends Risotto an `employee.created` event.
   That starts the **New hire onboarding** automation. Its instructions are six
   plain-language steps, each with a tool. See [Rippling
   triggers](https://www.tryrisotto.com/docs/dashboard/automations#rippling-triggers).

3. **The run looks her up and creates her Google Workspace account**

   First, the agent looks Maya up in Rippling to find her department. Then it
   creates her Google Workspace account, in Engineering's organizational unit.
   Neither step waits: the first only reads, and the second is not a
   destructive change.

4. **Three access steps wait for approval**

   The next three steps change access: activate her Okta account, add her to
   the Engineering group in Okta, and add her to the `#general` and `#eng`
   channels in Slack. At **Destructive changes**, these tools wait for an admin,
   so the run shows **Awaiting approval**. Dana, an IT admin, opens the run,
   checks each call in the **Tool approval** card, clicks **Approve all**, then
   **Submit decisions**. See [Approving a paused
   run](https://www.tryrisotto.com/docs/dashboard/automations#approving-a-paused-run).

5. **The run picks up where it stopped**

   In Slack, Maya is now in `#general` and `#eng`, and her team sees her join.
   Then Risotto posts in `#it-onboarding`: who she is, her department, and her
   start date.

6. **Read the run's record**

   In the dashboard, the automation's **Run history** lists the run as an
   **Event** run, marked **Success**. Open it to see the event Rippling sent,
   the agent's summary under **Result**, and the **Transcript**, with who
   approved each change, and when. See [Run
   history](https://www.tryrisotto.com/docs/dashboard/automations#run-history).

## Related

- [Automations](https://www.tryrisotto.com/docs/dashboard/automations): triggers, approvals, runs and run history
- [Rippling](https://www.tryrisotto.com/docs/dashboard/settings/people/connect/rippling): connect Rippling and use its automation triggers

Source: https://www.tryrisotto.com/docs/guides/examples/onboarding-video
