Skip to main content
Help Center

Start and Complete Work with Workspace Guided Paths

Learn how to choose, start, resume, verify, cancel, and review outcome-led Guided Paths from the Batoi Workspace Start page.

6 min readVerified Aug 8, 2026Batoi Platform
Guide navigation 42 of 42
Browse all 42 articles
Business view

What this page helps you accomplish

Learn how to choose, start, resume, verify, cancel, and review outcome-led Guided Paths from the Batoi Workspace Start page.

Batoi Platform · Workspace, Guided Paths
Accountable roleWorkspace Owner, Workspace Admin, Operator, Builder, Analyst, Viewer
Business taskGetting Started
Completion signalChoose an outcome, start or resume one governed Journey Run, and rely on canonical Batoi product state for verified progress.
1 Confirm

Scope and authority

Access to the intended authenticated Batoi Workspace A Workspace role permitted to view or start the selected Guided Path

2 Act

Getting Started

Learn how to choose, start, resume, verify, cancel, and review outcome-led Guided Paths from the Batoi Workspace Start page.

3 Verify

Observable business result

Choose an outcome, start or resume one governed Journey Run, and rely on canonical Batoi product state for verified progress.

Potential issue and recovery

A path is not enabled or not entitled.

Recommended recovery: Use Quick Create when suitable, or ask an Owner or Admin to review Workspace readiness and subscription access.

Workspace Guided Paths turn a business outcome into an ordered, resumable sequence across the Batoi products that own the work.

Who should use this article

This article is for Workspace Owners, Admins, Operators, Builders, Analysts, and Viewers who want to find the right starting point, follow verified progress, or review a completed result. Viewers can review permitted information but cannot start or change a path.

Before you begin

  • Sign in to the intended Batoi Workspace and confirm that you have the role required for the outcome.
  • Identify the Project or App context that should own the work, when the path asks for one.
  • Confirm that the required Batoi products and provider connections are available.
  • Never enter credentials, private keys, tokens, or unnecessary personal information in a Guided Path context.

How a Guided Path works

A Guided Path coordinates an outcome without taking ownership away from the Batoi products that create, approve, deploy, or verify the underlying records.

Workspace Guided Path lifecycle Choose an outcome, review the path, select permitted context, complete work in the owning product, refresh verified progress, and complete or review the result. From outcome to verified result The Journey coordinates the sequence; canonical Batoi product records remain authoritative. 1 Choose an outcome Start from the result you need. 2 Review the path Inspect outcome, steps, and roles. 3 Select permitted context Bind only the declared Project or App. 4 Work in the owning product Create, approve, deploy, or verify there. 5 Refresh progress Recheck authoritative product state. 6 Complete and review Retain a traceable verified result.
A Guided Path gives you one governed next action while each product continues to own its records and decisions.

Open Start and choose the right approach

  1. Open your Workspace.
  2. Select Start from the Workspace navigation.
  3. Use Continue where you left off to resume active work.
  4. Choose a Guided Path for a complete outcome, or use Quick Create when you already know the exact record you need.
Workspace Start page showing five outcome-led Guided Path cards with Batoi-blue accents
Start presents all five outcome-led paths together; Quick Create begins immediately below this focused view.
Guided or Advanced? The segmented View control changes how much operating detail is shown. It does not change permissions, canonical records, approvals, or completion rules.

Review a Guided Path before starting

Select Review path to inspect the expected outcome, intended audience, participating products, ordered steps, and required context. A preview is read-only: no Journey Run or business record is created until you submit Start Path.

Guided Path preview showing the expected outcome, six ordered steps, Project context selector, and Start Path action
Review the outcome and sequence, then select only the context declared by the path.

Start with safe context

  1. Select an existing Project or App when the path requests it, or select later when that option is available.
  2. Confirm that the selected record belongs to the current Workspace and represents the intended work.
  3. Select Start Path. Repeated submission resumes the matching active run instead of creating a duplicate lifecycle.

Follow verified progress

The run page shows progress, the governed next action, accountable owner, selected context, related canonical records, and every path step. Opening a link does not complete a step. Progress changes only when the owning Batoi product contains the required record, approval, decision, deployment, evidence, or verification result.

Guided Path coordination and canonical product ownership The Journey Run coordinates next action and progress while Core, Build, Govern, and Guard retain ownership of canonical records, approvals, evidence, and verification. Coordination is not record ownership The Journey reads authoritative state; it does not replace approvals, evidence, or product history. Workspace Journey Run • next action and accountable owner • derived progress and blocker • resumable coordination history verifies Canonical Batoi product state Core Project and members Build App and deployment Govern / Guard Approval and evidence Records, decisions, permissions, and audit history remain here. Cancelling coordination preserves canonical product records and traceable Journey history.
Completion is derived from authoritative product state, never from opening a link or manually claiming progress.
Active Workspace Guided Path showing 40 percent progress, related records, accountable owner, selected context, and completed steps
Return to the run and refresh progress after completing work in the owning product.

Understand common states

  • Ready — the step can be opened now.
  • Waiting approval — complete the approval in the owning product; the Guided Path does not bypass it.
  • Blocked — review the stated prerequisite, setup gap, risk decision, or record condition.
  • Completed — canonical product state satisfies the step resolver.
  • Cancelled — coordination stops, but canonical records and Journey history are preserved.
  • Archived — a terminal run is retained as reviewable history and removed from active work.

Cancel safely when the outcome should stop

Use Cancel Guided Path only when coordination should stop. Cancellation does not delete Projects, Apps, files, assessments, evidence, releases, or other records created in their owning products. An Owner or Admin can archive the terminal Journey history later.

Cancelled Workspace Guided Path with preserved progress, related record, restart action, archive action, and retained steps
A cancelled path preserves canonical records and offers a separate, traceable restart lifecycle.

Safety and governance

  • Use only a Project or App that belongs to the intended Workspace and business outcome.
  • Keep approvals, exceptions, attestations, evidence acceptance, deployments, and security decisions in their owning products.
  • Do not enter credentials, private keys, access tokens, or unnecessary personal information into Journey context.
  • Cancel only the coordination lifecycle. Review canonical records separately before deleting, archiving, rolling back, or withdrawing them.
  • Use Advanced for additional operating context, not as a way to bypass permissions or completion rules.

Troubleshooting and recovery

What you seeWhat to checkSafe next action
A path is not enabled or not entitled.Workspace rollout, subscription, role, and required product availability.Use Quick Create when suitable, or ask an Owner or Admin to review Workspace readiness and subscription access.
Progress does not change after opening a step.The required canonical record, status, approval, evidence, or verification result in the owning product.Complete or correct the authoritative work, then return and select Refresh Progress.
A Project or App is unavailable.Current Workspace, record status, path context declaration, and your permission to view the record.Return to the correct Workspace or select another authorized context. Do not use another person’s account.
The run is blocked or waiting.The highlighted blocker, accountable product, prerequisite, and approver.Resolve the condition in the owning product; do not manually claim completion or bypass approval.

Final verification

Expected result: You can choose an outcome from Start, review its sequence, bind only authorized context, follow one governed next action, and rely on canonical product state for progress.

Next step

Return to Start in your Workspace to continue a path or choose another outcome. Owners and Admins can use Creation Analytics to review aggregate completion, blockers, duration, cancellation points, and the separation between organic and controlled acceptance runs.