Skip to main content
Help Center

Create an Application Workspace in Batoi Build

Create the stable app record and Core Project binding that anchor every Batoi Build connection and delivery record.

3 min readVerified Jul 24, 2026Batoi Platform
Guide navigation 4 of 42
Browse all 42 articles
Business view

What this page helps you accomplish

Create the stable app record and Core Project binding that anchor every Batoi Build connection and delivery record.

Batoi Platform · Build
Accountable roleWorkspace Owner, Workspace Admin, Builder
Business taskGetting Started
Completion signalThe Build app has a stable identity, one owning project, an accountable owner, and explicit readiness gaps for every connection not yet configured.
1 Confirm

Scope and authority

Access to the intended authenticated workspace through My Batoi Authority to create or manage the app and bind its owning Core Project

2 Act

Getting Started

Create the stable app record and Core Project binding that anchor every Batoi Build connection and delivery record.

3 Verify

Observable business result

The Build app has a stable identity, one owning project, an accountable owner, and explicit readiness gaps for every connection not yet configured.

Potential issue and recovery

The expected record or action is missing.

Recommended recovery: Return to the intended context and ask an Owner or Admin to confirm access. Do not use another person’s account.

Who should use this article

This article is for Workspace Owners, Workspace Admins, and Builders who are authorized to complete or review this task. A consequential decision remains with the accountable person.

Before you begin

  • Access to the intended authenticated workspace through My Batoi
  • Authority to create or manage the app and bind its owning Core Project
  • Use approved sample or operational information only. Never enter a password, token, private key, or unnecessary personal information.

Open the app setup

  1. Enter the authorized workspace through My Batoi.
  2. Open Build and choose Applications.
  3. Create an app or open the intended app, then use App Overview and App Settings to review its identity.
Application context setup The app record, Core Project binding, and accountable owner establish the context for all later Batoi Build work. Establish one bounded app context App Record Name, stable key, mode, type, runtime, status Project Binding One owning Core Project and no fallback records Accountable Owner Authority, status, and next setup responsibility
The app record and project binding must be correct before connecting delivery infrastructure.

Complete the App Record

  1. Enter a distinct business-facing App Name and stable lowercase App Key.
  2. Select RAD Build App only when the app uses the Batoi RAD application model. Otherwise choose the applicable non-RAD mode.
  3. Choose the delivery App Type, implementation Language, and actual Runtime Stack.
  4. Assign the accountable Owner.
  5. Set Status to Active only when the identity and ownership are correct.

Bind the owning project

  1. Select the Core Project that owns the business outcome.
  2. Open the Core Project Overview and Build Project Overview.
  3. Confirm both views identify the same project and app.
  4. If a repository, database, sandbox, or deployment is not connected, require a setup-needed state. Do not substitute records from another app or the current platform runtime.
Batoi Build App Overview
Reference screen: App Overview confirms identity and exposes remaining source, data, runtime, delivery, or governance gaps.

Completion check

  • The workspace, project, app, owner, build mode, and runtime are correct.
  • The selected-app navigation appears and remains in the intended app context.
  • App Overview shows honest setup-needed states instead of unrelated fallback data.
  • No credential, private path, or unnecessary personal information appears in the app description or screenshots.

Continue with Connect a Source Repository to Batoi Build.

Troubleshooting and recovery

What you seeWhat to checkSafe next action
The expected record or action is missing.Workspace, project/app context, role, status filters, and prerequisites.Return to the intended context and ask an Owner or Admin to confirm access. Do not use another person’s account.
The status remains incomplete or needs review.Required fields, evidence, approvals, source connections, checks, and owners.Record the missing item and owner. Do not mark the task complete until it can be independently verified.
The result conflicts with policy or evidence.Scope, source recency, exception authority, decision conditions, and reviewer independence.Do not bypass the control. Return the item for correction or escalate it through the authorized route.

Safety and governance

Protect sensitive information. Do not place credentials, secrets, private keys, raw tokens, unnecessary personal information, private repository content, customer identifiers, or restricted documents in a public note, screenshot, prompt, export, or evidence caption. Use approved secret references and permission-controlled workspace records.

Final verification

Expected result: The Build app has a stable identity, one owning project, an accountable owner, and explicit readiness gaps for every connection not yet configured.

Next step

Continue with the next verified article in this Product Guide, or return to the Batoi Platform Product Guide.