Skip to main content
By default, all workspace members with at least viewer access can see every journey. Private journeys flip that default: a journey is hidden from anyone not explicitly granted access, regardless of their workspace role.

​
When to use it

Mark a journey private when:
  • It contains sensitive request templates or data patterns you don’t want broadly visible.
  • It’s a work-in-progress that shouldn’t appear in the workspace journey list yet.
  • It’s scoped to a specific team or squad within a larger workspace.
  • You want to limit who can run it, not just who can edit it.

​
Key concepts

Visibility vs. role. A user’s workspace role (editor, viewer) determines what they can do in the workspace. Private status determines whether they can see a particular journey at all. A workspace editor who is not invited to a private journey cannot view or run it. Default visibility. When a workspace admin enables “private by default” for new journeys, every newly created journey starts as private and must have access explicitly granted. When off, new journeys are visible to all workspace members (the Reqflo default). Journey-level access. Once a journey is private, access is managed per journey using the Access panel inside the journey. Owners of that journey can add editors and viewers independently of the workspace-level user list.

​
How it works

1

Enable private visibility

Open the journey’s Access panel and toggle the journey to Private. This immediately hides it from users who are not already listed as owners, editors, or viewers of that journey.
2

Invite collaborators

Add users by email or workspace username inside the Access panel. Assign them the role they need: owner, editor, or viewer.
3

Set workspace default (optional)

In Admin → Private journeys, enable “new journeys are private by default” if your workspace should start all new journeys hidden.

​
Examples

Making a production-runbook journey private. You have a journey that triggers production-environment Runbooks. Open its Access panel, set it to Private, and add only the SRE team as editors. Everyone else — even workspace editors — will no longer see it in their journey list. Workspace-wide default. A security-conscious team enables the private-by-default setting in Admin. New journeys created by any workspace member start hidden. Creators must explicitly open access when a journey is ready for broader use.