How it appears in the overview
On a cross-workspace journey, the Journey Overview shows one column per workspace involved. The owning workspace’s column comes first, followed by a column for each other workspace that owns work.
Access is per workspace
Everyone involved sees the whole journey, but you act only on your own workspace’s slice of it. You can only work on a task (e.g. submit its form, retry a run, open Run Details) in workspaces where you can manage journey tasks. In every other workspace’s column, tasks are view-only: you can open them and follow progress, but you can’t act on them. Each team retains control over the tasks in its workspace. For example, IT handles provisioning and Facilities handles badge access; their workspace permissions determine who can act on each task.Building cross-workspace journeys
A journey builder assigns a task to another workspace, and that task then uses the other workspace’s published workflows and runs inside that workspace. The task still belongs to the journey, so it shows up in the journey’s overview and counts toward completion like any other task. The full mechanics (e.g. assigning a task’s workspace, referencing that workspace’s workflows, and routing the work) live in the Building journeys guide.Related
Journeys
What journeys are and how the pieces fit together
Journey tasks
Overview of journey tasks
Journey admin and end user views
How admin and end users view journeys
Building journeys
Design and build journeys in Catalyst

