Data, users and integrations
Your app is a real application with its own database, its own user accounts and its own connections to payment and email providers. This page covers how you manage all three without touching code.
Data#
Open the Database tab in the workshop.
- Tables are listed with plain names (Customers, Bookings, Services) and fields are labelled the way the app shows them, with a hint for each.
- Edit in place. Add, change or delete records with forms. Validation matches the app's rules, so a booking cannot point at a service that does not exist.
- Sample data is marked. Use Clear sample data to remove it in one go once you have your own; records that your real data depends on are adopted rather than deleted.
- Advanced mode reveals table creation and field types. Most owners never need it.
- Export your data as a file on Starter plans and up.
Every app has its own isolated database. Nothing is shared with other apps or other customers, and the app's database credentials are never shown in the dashboard.
An app can be pointed at a PostgreSQL database you host, for example to keep data in a specific region or alongside existing systems. See the Bring your own database card on the Database tab.
Users and sign-up policy#
Apps are invite-only by default. Strangers cannot create accounts in your business system; you are provisioned as the owner automatically, and staff join by invitation.
| Role | How they get in | What they see |
|---|---|---|
| Owner | You, automatically | Everything, including the app's admin dashboard |
| Staff | An invite link from the Users tab, with a role such as waiter, kitchen, stylist, mechanic, clinician | The operator pages for their role, never the admin settings |
| Customer | Sign-up where the business type allows it, or a customer account created at checkout | Their own orders, bookings, pets or visits under /account |
Some verticals allow public customer sign-up because it makes sense there (loyalty schemes, community apps); others keep it closed. The Users tab shows the current policy, and you can change it. A public sign-up is always a customer account: a visitor can never become an admin.
Invite links are signed and expire. Pin an invite to an email address to make sure only that person can use it.
Sign in with Google, for app users#
Your app's sign-in page can offer Continue with Google. Autoflowly brokers the sign-in, so you do not need your own Google project. The result is role-aware: your own Google account becomes the owner, customers become customers, and anyone else sees the invite-only page. Turn it off per app from the Users tab if you prefer email and password only.
Integrations#
The Integrations tab lists connectors by category. Connecting one asks for the credentials that provider issues, applies them to the running app, and shows Applying until the app has picked them up (about a minute).
| Category | Connectors |
|---|---|
| Payments | Stripe, PayPal, Flutterwave, CinetPay, MTN Mobile Money, Orange Money. Cash is always available |
| Resend, to send customer emails from your own domain. Without it, emails go through Autoflowly's relay in your business name | |
| Messaging | WhatsApp and SMS via Twilio for the AI Receptionist and missed-call text-back |
| Analytics | Google Analytics 4 and similar, loaded only after the visitor consents |
| Auth | Google sign-in for app users |
| Legal | Business details that the privacy policy, terms and Impressum are generated from |
Credentials are stored encrypted with the app, persist across restarts and redeploys, and are never shown again after you save them. Removing a connector removes its keys.
Payments in practice#
The app offers a payment method only when its provider is connected. Each checkout starts the payment with the provider before the order is confirmed; a declined or misconfigured provider shows the real error on the page, it never silently falls back to cash. Mobile money prompts the customer on their phone and the app polls until it is confirmed. See Quotes, invoices and payments for the owner's side.
Email in practice#
With no email connector, confirmations and reminders are relayed by Autoflowly in your business name, with a monthly allowance on the Free plan. Connect Resend with your own domain for unlimited sending and your own sender address. See Customer emails and messages.
Environment#
The Environment tab exposes configuration values for the rare case a connector does not cover: a third-party API key the app reads, a feature switch. Values marked secret are write-only. Changing a value restarts the app within a minute.