Skip to main content
The Access panel controls who can work with a journey. By default, anyone in your organization can view a journey. You can grant editor or owner access to specific people, or make the journey private to restrict default visibility entirely.

​
When to use it

Open the Access panel when you need to:
  • Grant someone editor access to update the journey.
  • Assign or transfer ownership.
  • Restrict a journey to a specific set of people (private journey).
  • Review who currently has access.

​
Key concepts

  • Owners — can manage access, edit the journey, and make structural decisions like archiving or deleting. Ownership can be transferred. There is typically at least one owner per journey.
  • Editors — can update the journey: add and configure steps, modify values, update coverage, and change Details. Editors cannot manage access.
  • Viewers — can open and inspect the journey but cannot modify it. In a non-private journey, all organization members are viewers by default.
  • Private journeys — restrict default visibility. In a private journey, only explicitly granted users (owners, editors, or named viewers) can see it. Others in the organization have no access. See Admin: private journeys for organization-wide settings.

​
How it works

Open the Access panel from the Build-mode panel rail. The panel shows the current access list and lets owners make changes. Adding access: Search for a user or team and assign them a role (Editor or Viewer). Owners can add anyone in the organization. Changing roles: Existing access entries can be upgraded or downgraded. An editor can be made an owner; an owner can be reduced to an editor (as long as at least one owner remains). Removing access: Owners can remove access for any user or team. You cannot remove the last owner without first assigning ownership to someone else. Making a journey private: Toggle the Private setting to restrict default visibility. Once private, only listed users can access the journey — it disappears from the journey list for everyone else.
Making a journey private immediately restricts access for anyone not on the access list. If teammates are relying on the journey (in runbooks, CI, etc.), add them explicitly before toggling privacy.

​
Examples

A journey owned by the payments team with controlled access:
User / teamRole
@payments-teamOwner
@aliceEditor
@support-teamViewer
(everyone else)No access (private journey)
In this setup, the payments team owns the journey, Alice can update it, support can view and run it via Runbook, and no one else can see it.

Details

Journey name, description, owner label, and tags.

Private journeys (admin)

Organization-wide settings for private journey visibility.

Users and access (admin)

Manage users, teams, and organization-level access.

Build mode

Overview of Build-mode panels.