Skip to main content

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.

Switera app overview with readiness state and setup cards
The app overview combines readiness, focus areas, service status, and recent activity for the selected app.

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 webhooks configured?
  • what happened recently?
  • what should the Builder do next?

Readiness states

StateMeaningTypical next step
Needs setupA required setup area is missing.Follow the primary action on the page.
Waiting on first memberInvitations exist, but nobody has accepted yet.Review invitations and email setup.
Ready for first end usersThe baseline is configured, but real users are not active yet.Bring in first users or import a starter list.
LiveReal organization or end-user activity exists.Monitor operations and improve the next service.
Needs attentionA 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.

App navigation

Inside an app, the sidebar groups product areas:

Sidebar areaUse it for
OverviewReadiness, current operating state, next action, and recent activity.
OrganizationsCustomer accounts, members, invitations, domains, groups, and organization state.
Services > AuthenticationSign-in, social providers, enterprise SSO, MFA, branding, legal, hooks, and directory sync.
Services > WebhooksEndpoint setup, event catalog, deliveries, attempts, replay, and test sends.
Services > EmailSender identity, templates, workflows, built-in emails, and delivery runtime.
Admin > API KeysPublishable and secret keys for test and live environments.
Admin > Audit LogsTraceability, filtering, and export of configuration activity.
  1. Open the app overview.
  2. Follow the primary next action.
  3. Create the first organization.
  4. Configure the first Auth method.
  5. Configure email sender identity and invitation or managed messages.
  6. Add webhook endpoints only if your backend needs events.
  7. Copy API keys only from a trusted backend setup machine.
  8. Check audit logs after important changes.
  9. Return to the overview and confirm blockers are gone.

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.