Editing Journey Steps
Elyes Graba avatar
Written by Elyes Graba
Updated over a week ago

Overview

Journey Steps are how you configure the candidate-facing step tracker on Journey pages, as well as the content on each step. Note that "steps" in Journeys correspond to "stages" in your ATS.

Reference

This is a reference for configuring the "Steps" Page in Journeys:

  1. The Steps tab.

  2. Select the active Journey step here. Changing this will update the Journey step that you are currently editing. Hit "publish updates" to update the current Step on the public Journey page.

  3. Greenhouse Job stages. These are pulled directly from your ATS.

  4. Journey steps. Here you can select which Journey Step Template to show for a given Journey step:

    1. As noted on the page, we will automatically select the Journey Step Template that you choose here the next time a journey is created with the same job stage.

    2. Example: Let’s say that for the “Face to Face” ATS job stage here, you select the “Onsite” Journey Step Template, and hit publish updates. Now, for all future Journeys, when we see the “Face to Face” ATS stage, we will automatically select the “Onsite” page template.

    3. This is not something you need to worry about. As you create Journeys, we learn how you want them set up, and use your past choices to automatically inform defaults going forward. Magic!

  5. The current job stage in Greenhouse will be marked in bold. Note that changing stages in Greenhouse will not update the “active step” of the Journey, that has to be done manually.

  6. If you don't select a journey step template, we will omit that stage/step on the Journey page.

  7. The currently active Journey step will be marked as bold.

  8. This is the final step tracker that will be shown on the Journey page. Note that the current stage is highlighted.

  9. Publish updates! Don’t forget to hit this to make your changes live for the candidate. You can always use the Preview tab to preview changes, and hit the Journey link in the bottom-left to double-check that everything looks good after publishing updates.

Did this answer your question?