Skip to content
Docsturbobase.io

Open your app

Shipped

Once the setup wizard finalizes, the instance’s row in the console’s instances list turns its slug into a link. Clicking that slug takes you to your Turbobase app at <your-slug>.turbobase.app, in a new tab.

A separate sign-in

Section titled “A separate sign-in”

Your Turbobase app is a different realm from the console, with its own credentials. The console sign-in (console.turbobase.io) is for managing your subscription — orgs, instances, billing. The app (<slug>.turbobase.app) is where your team does the actual work, and it has its own user store.

You set the first app admin during the Admin step of the setup wizard. Those are the credentials you use here — not your console email/password. From inside the app, that admin invites the rest of your team and manages their permissions; see Users and permissions and Auth levels.

What you see first

Section titled “What you see first”

When you sign in, the app is already populated from the source you connected during setup, Oracle NetSuite for most instances. From the app you can:

  • Browse your mirrored data under Data, across the data model — the canonical tables your source maps into.
  • Chat with Pilot, your AI assistant — grounded in your own data, once an administrator has enabled Pilot chat for your instance. That setting covers the app; asking Pilot from a connected channel works either way.
  • Check source health to confirm your source is syncing.
  • Add custom fields and custom tables on top of the mirrored data.
  • Open the knowledge base — your team’s living library of how the business runs.
  • Review the audit log of changes.

Administrators additionally get the Development pipeline — proposals, solutions, and tracked releases — and can build apps on your data.

Where to go from here

Section titled “Where to go from here”