Dashboard Tour

There is one console in BetterSuite. Live operations and configuration sit in the same sidebar, and you reach it at two addresses.

Same product, same pages, same sign-in. A setting you change at one address is changed at the other, because it is one console. Other pages in these docs call it the Owner Dashboard; that is this console.

Signing in

Sign in at bettersuite.io/login, or at your own console address, with the same email and password. Passkeys and Google / Apple sign-in are set up under Settings.

Your own console address only admits your workspace's staff — an operator from another business can't sign in there. Registration and the onboarding wizard live on bettersuite.io; if you open them from your own address you're sent across.

To give someone access, add them under Account → Staff and pick a role. See Team & Roles.

Where do I find…

• "How do I change my plan?" → Account → Billing
• "A ride is still waiting for a driver" → Taxi → Dispatch, or open the ride under Rides and use Assign driver
• "I want to add a dispatcher" → Account → Staff → New staff member
• "I want to limit what a role can do" → Account → Roles
• "Stripe webhook needs updating" → Payments → PSP Accounts
• "Refund or cancel this booking" → Rides / Orders / Reservations / Jobs → open the booking → Refund or Cancel booking
• "Approve this driver" → Taxi → Driver approvals

What you see depends on your role and on the services you run. Entries your role doesn't cover are hidden.

The sidebar, top to bottom

Dashboard (home)

A status read-out: your plan and billing state, and a "Where you operate" card with the cities, countries, and regions you cover. If onboarding isn't complete (specifically, plan selection), this page sends you back to /onboarding.

Launch Center

The guided setup checklist, plus a card for each of your apps with its web address, a QR code, and the test logins that work on it. One of those cards is your branded console address — the same dashboard, on your own domain.

Your services

Each service you run (Taxi, Shop, Parking, Services) gets its own group, with the day-to-day pages first and the setup pages after.

Every booking — a ride, an order, a reservation, a job — opens to a detail page with its transactions, reviews, chat and notes, and the actions that apply to it: Assign driver, Refund, Cancel booking.

Customers

One customer list across every service. A customer's page shows their orders, wallet, addresses, reviews, notes and signed-in devices.

Brand & apps

• Branding — logos, colors and app names. See Branding.
• Your Apps — the hub for shipping apps under your own name: Custom domains, Connected apps, Push credentials, Social sign-in, and Store release. Pro+; below that the page explains what the upgrade adds.
• Testers (Owner only) — test accounts with a fixed login code, so you can try your apps before you connect an SMS provider.

Custom Domains

Map your own domains to each app — passenger, driver, vendor, and the console itself. Each row shows the system subdomain and the CNAME target for your own domain. See Custom Domains for the DNS recipe.

Connected Apps

The mobile-app registration surface. This is not an integrations catalog — it's where you declare the iOS / Android apps you publish under your own App Store / Play Console accounts. The bundle IDs you enter here get surfaced in your workspace's /.well-known/apple-app-site-association and /.well-known/assetlinks.json files, which Apple and Google fetch from your verified domains to prove domain ↔ app ownership. That's what makes Universal Links and passkeys work against your branded apps.

PSP credentials, SMS gateways and KYC policies don't live here — they have their own entries under Payments, Messaging and Configuration.

Store Release

Pro+ only. Kick off the build pipeline that ships your branded passenger / driver / vendor apps to the App Store and Play Store under your own developer account. Below Pro, this page shows the upgrade prompt and a preview of the flow.

Messaging

• Email — the sending account (your own SendGrid or MailerSend account on Pro+) and the email templates.
• SMS Providers (Owner only) — your SMS gateway credentials and message templates.

Marketing

• Announcements — push and in-app notifications you create and target by audience.
• Gift Cards — issue or batch-create.
• Coupons — campaign-based discount codes with redemption rules.

Payments

Owner only.

• PSP Accounts — your payment gateway credentials. See Stripe Payments.
• Payout Methods — how drivers, vendors and providers can be paid out (Stripe Connect, bank transfer, manual), each bound to one of your PSP accounts.

Configuration

Settings that apply across services:

• Regional Settings — country, app languages, units, date and time formats, map starting point, wallet top-up amounts, support phone.
• Regions — where you operate, each with a boundary drawn on a map and its zones. Used by pricing and dispatch.
• KYC Policies — which documents each role must provide, and the certifications those policies can require.
• Tax — tax policies, zones, exemptions, provider configs.
• Feedback Criteria — rating criteria sets (per service).
• Cancel Reasons — the reasons a booking can be cancelled with, and what each refunds or charges.
• AI — Providers, Features and Usage as tabs on one page. See AI Providers.
• Migrations — the data-migration runner. It's a database-to-database tool that connects to a legacy app's MySQL/MariaDB and writes the rows into BetterSuite's Postgres. Exactly one provider ships today: legacy_ridy_taxi, for first-generation TypeORM-style self-hosted taxi platforms — see Migrating from a Legacy Ridy Taxi Platform for the full playbook. Uber Fleet, Yelo, and other SaaS-only competitors are not supported sources — leaving those is a relaunch with manual driver re-onboarding rather than a data migration.

API Keys

Under Developer. Create and revoke server-to-server API keys for the GraphQL endpoint. Owner only, Pro+. See API Keys for the developer-facing story.

Account

• Billing (Owner only) — your subscription plan, the services it covers, the card on file, invoices, and the renewal date. Plan changes (upgrade, downgrade, cancel) live here.
• Staff — the people who run your workspace from this console, and the role each holds.
• Roles — what each staff role can see and change.
• Support — open a ticket to the BetterSuite team. These route to us, not to your own customers.
• Settings — Workspace name, Profile, Password, Sessions, Passkeys, Connected accounts, Sign-in & Auth policy, Language, and (Owner only) Ownership transfer.

There's also an Audit Log page (/dashboard/audit-log) that doesn't appear in the sidebar — sensitive actions in the console are recorded there, searchable by member, action, and date range.

What isn't in the console today

A few screens from the retired ops console app have no equivalent yet, so you don't go looking:

• Payout sessions — scheduled batch payout runs for drivers, shops and parking providers. Payout methods are here; the batch runs are not.
• Accounting reports — the revenue dashboard and wallet lists. Per-customer and per-driver wallets are on their own pages.
• An inbox for tickets from your own customers. Support in the sidebar is your line to BetterSuite.
• Subscription plans you sell to your own customers — plans, subscribers, invoices, refunds.
• Partnerships, review moderation, customer tier settings, and the taxi dispatch-health view.

If your operation depends on one of these, open a Support ticket and tell us which.

URL patterns and custom domains

When your workspace is provisioned, BetterSuite creates a small family of system subdomains under bettersuite.io:

bettersuite.io/dashboard is not per-workspace — every workspace shares it and is identified by the signed-in session. acme-admin.bettersuite.io is per-workspace: it only ever shows Acme.

On Pro+ plans, the system subdomains can be replaced with verified custom domains. Once verification completes under Custom Domains, the custom URL becomes the canonical address and the system subdomain stays as a fallback. The console card in the Launch Center follows it: your verified custom console domain if you have one, otherwise the system subdomain.

What's next

• Plans & Billing — change plan or top up.
• Branding — your logo and colors, in your apps and on your console address.
• Team & Roles — add staff and decide what each role can do.
• Custom Domains — replace *.bettersuite.io with your own.