Skip to main content
Help Center

Connect an Application Database in Batoi Build

Connect the App to its approved sandbox data service with explicit access and change authority and no exposed connection details.

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

What this page helps you accomplish

Connect the App to its approved sandbox data service with explicit access and change authority and no exposed connection details.

Batoi Platform · Build
Accountable roleWorkspace Admin, Builder
Business taskIntegration
Completion signalThe App has a tested sandbox data connection, approved access boundary, explicit change authority, and no exposed connection detail.
1 Confirm

Scope and authority

An active app and bounded sandbox target in Batoi Build Approved database credentials stored through the secure credential control

2 Act

Integration

Connect the App to its approved sandbox data service with explicit access and change authority and no exposed connection details.

3 Verify

Observable business result

The App has a tested sandbox data connection, approved access boundary, explicit change authority, and no exposed connection detail.

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 Admins and Builders who are authorized to complete or review this task. A consequential decision remains with the accountable person.

Before you begin

  • An active app and bounded sandbox target in Batoi Build
  • Approved database credentials stored through the secure credential control
  • Authority to test the connection and define schema change responsibility
  • Use approved sample or operational information only. Never enter a password, token, private key, or unnecessary personal information.

Open Database Connections

  1. Open the selected app in Build.
  2. Expand Settings and choose Database Connections.
  3. Use App Workspace after setup to confirm the App, environment, and approved data connection.
Application data connection workflow The selected App uses an approved environment-specific data connection with controlled access and change authority. Connect data without publishing secrets App Scope Selected app and sandbox environment Secure Connection Least privilege and tested adapter Approved Access App and environment access boundary Change Control Schema, seed, backup, and evidence owner
The data connection, access approval, and change authority must share the same App and environment boundary.

Create and test the connection

  1. Use an app- and environment-specific connection name.
  2. Select the approved data service and sandbox environment.
  3. Store all connection details only in the approved credential controls.
  4. Test connectivity through the provided action.
  5. Confirm the approved App and environment access boundary.
  6. Assign schema and migration authority, backup responsibility, and evidence ownership.
Batoi Build Database Connections
Reference screen: public guidance uses the safe register view and excludes connection details.

Verify App Workspace

  • The selected app shows a Ready sandbox database connection.
  • The intended access profile is active and approved.
  • The source, environment, data connection, and access records all belong to the same App.
  • Schema changes are applied only through the approved App connection.
  • Evidence records the migration outcome without copying secrets.
Batoi Build Database Connections
Reference screen: App Workspace is the cross-check for app-scoped setup records.

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 App has a tested sandbox data connection, approved access boundary, explicit change authority, and no exposed connection detail.

Next step

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