> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Journeys

> Create onboarding and activation journeys, apply them to partners, and track progress in Introw.

**Open in Introw:** [Journeys](https://app.introw.io/tasks)

## How it works

A journey is a reusable set of tasks. You build a journey once, then apply it to the
partners who should run it. Applying a journey copies its tasks onto each selected
partner, so every partner gets their own progress while the journey itself stays the
journey definition.

You choose how a journey's tasks behave. With a **flexible** order, partners can
complete tasks in any sequence. With a **sequential** order, a task only unlocks
after the previous one is done, which is useful when steps build on each other.
Introw provides starting templates for onboarding, activation, and certification so
you do not begin from a blank page, and you can also create a journey from scratch.

Progress is tracked per partner across **to do**, **in progress**, and **done**, and
you can view all the partners on a journey from the journey's own tabs.

### Activation best practices

Signing a partner is not the same as activating one. A few patterns, drawn from what
works across programs, turn new partners into productive ones:

* **Make the lifecycle explicit.** Put partners on a journey so the path to first value
  (first deal, first certification) is a clear checklist rather than something a partner
  manager carries in their head.
* **Give every step an owner and a deadline.** Use per-task assignees and due-date offsets
  so each step has accountability and a realistic timeframe relative to when onboarding
  starts.
* **Train early.** Pair the journey with onboarding courses so partners can sell and deliver,
  not just complete admin steps.
* **Nudge and recap.** Use partner notifications to keep deals moving and to recap progress,
  so a stalled partner gets a prompt instead of going quiet.

The aim is a repeatable activation motion: new partners reach their first win faster and
stall less often.

## Prerequisites

* Write access to Journeys to create and apply them.
* Partners in Introw to apply a journey to.

## Settings & configuration

Journeys are managed from the [Journeys](https://app.introw.io/tasks) page. Each
journey has its own configuration and progress views.

### Creating a journey

**Add** opens a chooser with built-in journeys (onboarding, activation, and
certification) and a **create from scratch** option. Picking a template seeds the
journey with a sensible set of starting tasks you can edit.

**Name** identifies the journey in the list and to your team. Give it a name that
says what stage it covers, like onboarding or activation.

**Task execution order** is the key behavior setting. **Flexible** lets partners
complete tasks in any order; **sequential** requires each task to be finished before
the next opens. Choose sequential when later steps genuinely depend on earlier ones.

### Tasks within a journey

On a journey's configuration view you add, edit, reorder, and remove the tasks
partners will complete. Order matters most when the journey is sequential, since it
sets the unlock sequence. On each task, **Add action** configures how the task
completes automatically when a partner watches an asset, submits a form, uploads a
file, opens a link, completes a course, or obtains a certificate. The course and
certificate actions pair naturally with a certification journey, closing the task the
moment the partner finishes the course or is issued the certificate.

### Applying and tracking

**Apply** publishes the journey to a chosen set of partners, copying its tasks to
each of them. The journey's progress tabs then show partners grouped by where they
are: to do, in progress, and done. You can also see and complete a partner's tasks
from that partner's own task list.

## Setup walkthrough

<Steps>
  <Step title="Create a journey">
    On [Journeys](https://app.introw.io/tasks), choose **Add** and start from a
    template or from scratch.
  </Step>

  <Step title="Set the task order">
    Choose **flexible** or **sequential** depending on whether steps depend on each
    other.
  </Step>

  <Step title="Build the task list">
    Add and order the tasks partners should complete.
  </Step>

  <Step title="Apply it to partners">
    Use **Apply** to publish the journey to the partners who should run it.
  </Step>

  <Step title="Track progress">
    Watch partners move across to do, in progress, and done from the journey's tabs.
  </Step>
</Steps>

## How-to guides

<CardGroup cols={2}>
  <Card title="Assign a journey and track progress" icon="book-open" href="/features/partners/journeys/guides/assign-a-journey-and-track-progress">
    Apply a journey to the right partners, then follow each one through to do, in progress, and done so you can step in before anyone stalls.
  </Card>

  <Card title="Auto-apply a journey from the experience" icon="book-open" href="/features/partners/journeys/guides/auto-apply-a-journey-from-the-experience">
    Use the tasks section in the experience builder to auto-assign a journey to every partner who gets the experience.
  </Card>

  <Card title="Build a journey from scratch" icon="book-open" href="/features/partners/journeys/guides/build-a-journey-from-scratch">
    Define your own ordered or flexible set of partner tasks, with each task's assignee, due date, visibility, and auto-complete action set.
  </Card>

  <Card title="Create a journey from a template" icon="book-open" href="/features/partners/journeys/guides/create-a-journey-from-a-template">
    Start from a built-in onboarding, activation, or certification journey, then tailor the tasks, order, assignees, and auto-complete actions to your program.
  </Card>
</CardGroup>

## Limits & gotchas

<Warning>
  Applying a journey copies its tasks onto each partner at that moment; editing the journey afterward does not rewrite tasks already applied. A sequential journey only opens the next task once the current one is done, so an unfinished early task blocks the rest for that partner.
</Warning>

## Troubleshooting

* **A partner cannot start a later task** - the journey is sequential and an earlier task is not done yet.
* **Edits to a journey did not reach a partner** - the partner was applied before the edit; re-apply or update their tasks directly.
* **A journey shows no partners** - it has not been applied yet; use **Apply** to publish it.