Journey Designer
The screen where you set up and publish the start journeys that welcome new people, based on how the person arrived and which persona cell they fall into.
What's on this screen
The screen is in the platform menu under Build, as Journeys. The four columns are the four ways of arriving: founded, invited, provisioned, self_service. Each column holds the same twelve persona cells as cards (scope × intent, for example tenant × consume). Cells that serve no one aren't in the list at all. If a cell has a journey, the card shows its status (draft, published) and its key.
A journey's key is its arrival and cell, for example provisioned-tenant-consume. It never changes, and it is how a capability's Contents lists the journey when a package carries it. A package carries a journey only once it is published.
What you can do
- On a card with no journey, choose Compose. The journey is created as a draft with an automatic name and a fixed set of four steps (
welcome,identity,intent,first_value). - While the card shows a draft, Edit steps chooses which steps run and in what order (
welcome,identity,intent,first_value— the ones the first run can run; at least one), then Publish. - A published journey's steps do not change. Start version N+1 opens the next version as a draft with the same steps; the published version keeps running until the new one is published, and is then deprecated.
The card shows the latest version, its status and how many steps it has. The name is not changed from this screen. What happened, or why a change was refused, appears above the grid.
Who can do what
| Task | Permission key needed (in the platform scope) |
|---|---|
| See the screen | journey.read |
| Compose | journey.write |
| Publish | journey.publish |
Keep in mind A separate journey is set up for each way of arriving: a journey you set up in one column appears only in that column; the same cell in the other columns can be set up separately with Compose.