Skip to main content
Workspace admins configure the shared infrastructure that every journey in your workspace depends on — users, secrets, environments, runners, and visibility rules. Changes here affect everyone, so admin settings are separated from journey-level configuration.

​
When to use it

Visit Admin when you need to:
  • Add teammates or adjust their workspace roles.
  • Configure environment values for a service (base URLs, service-level config).
  • Register or rotate secrets available to Cloud Runner executions.
  • Set up or update runner configuration for cloud execution.
  • Review who changed what in the audit log.
  • Control default visibility for journeys in the workspace.

​
What admins manage

Users and access

Add users and assign workspace roles: owner, editor, or viewer.

Private journeys

Restrict default journey visibility so only invited members can see a journey.

Service environments

Configure base URLs and environment-specific values per service.

Secrets management

Manage cloud-managed secrets referenced by name in journeys and resolved at run time.

Audit log

Track who changed what across the workspace.

Runners

Configure the Cloud Runner for durable, cloud-based journey execution.

​
Key concepts

Workspace scope. Admin settings apply across the entire workspace. Journey-level configuration — values, cases, step definitions, per-journey access — is managed inside each journey. Admin is for the shared foundation underneath. Separation of concerns. Environments describe the system target (which services, which base URLs). Secrets hold sensitive credentials. Runners determine where execution happens. These are intentionally separate so each can be changed without disturbing the others.