App overview
The app overview is the operating home for one SaaS app. Open it before changing service settings so you know whether the app is still in setup, ready for first users, live, or needs attention.
What the overview shows
The overview helps you answer practical operating questions:
- what is the app called and which slug is selected?
- is there a setup blocker?
- does the app have at least one organization?
- is Auth configured enough for end users?
- are account emails and backend API keys ready?
- are webhooks configured if this app needs event delivery?
- what happened recently?
- what should the Builder do next?
Readiness states
| State | Meaning | Typical next step |
|---|---|---|
| Needs setup | A required setup area is missing. | Follow the primary action on the page. |
| Waiting on first member | Invitations exist, but nobody has accepted yet. | Review invitations and email setup. |
| Ready for first end users | The baseline is configured, but real users are not active yet. | Bring in first users or import a starter list. |
| Live | Real organization or end-user activity exists. | Monitor operations and improve the next service. |
| Needs attention | A blocker or degraded state needs review. | Open the linked service and resolve the issue. |
Use the primary action
When the overview shows a large action card, treat that as the next recommended task. Common examples:
- Create your first organization when the app has no customer container yet
- Finish sign-in setup when Auth is missing a usable method
- Review organizations when one or more organizations need attention
- Open webhooks when external notifications are the next integration step
After completing the task, return to the overview and confirm the readiness card changed.
Launch checklist
The overview includes a compact launch checklist for the required first-app baseline:
| Checklist item | Required? | What ready means |
|---|---|---|
| Create first organization | Yes | At least one customer organization exists. |
| Configure sign-in | Yes | Auth has a saved baseline for hosted sign-in and user management. |
| Prepare account email | Yes | Sender settings are available and runtime alerts are clear. |
| Create backend API key | Yes | At least one secret key exists for trusted backend calls. |
| Bring in first users | Yes | The app has real end users, or it is ready for the first invite/import. |
| Connect event receiver | No | Webhooks are configured only when the app backend needs events. |
The checklist separates required launch work from optional integrations. A missing webhook endpoint should not block a simple pilot unless the product depends on event delivery.
App navigation
Inside an app, the sidebar groups product areas:
| Sidebar area | Use it for |
|---|---|
| Overview | Readiness, current operating state, next action, and recent activity. |
| Organizations | Customer accounts, members, invitations, domains, groups, and organization state. |
| Services > Authentication | Sign-in, social providers, enterprise SSO, MFA, branding, legal, hooks, and directory sync. |
| Services > Webhooks | Endpoint setup, event catalog, deliveries, attempts, replay, and test sends. |
| Services > Email | Sender identity, templates, workflows, built-in emails, and delivery runtime. |
| Admin > API Keys | Publishable and secret keys for test and live environments. |
| Admin > Audit Logs | Traceability, filtering, and export of configuration activity. |
Recommended app setup flow
- Open the app overview.
- Follow the primary next action.
- Create the first organization.
- Configure the first Auth method.
- Configure email sender identity and invitation or managed messages.
- Create or review the backend API key from a trusted setup machine.
- Add webhook endpoints only if your backend needs events.
- Check audit logs after important changes.
- Return to the overview and confirm the launch checklist has no blockers.
Avoid common mistakes
- Do not configure production credentials before confirming you are in the correct app.
- Do not invite real users before email and Auth are reviewed.
- Do not subscribe webhook endpoints to every event by default.
- Do not rotate live API keys until the backend has the replacement.
- Do not treat a setup app as live just because it was created.