Day-two operations
Day-two operations are the recurring checks your team performs after the first app is live. Use this page as a practical operating rhythm for keeping Switera healthy.
Daily checks
Check:
- new or failed sign-ins
- pending organization invitations
- user import failures
- webhook delivery failures
- email delivery problems reported by users
- unexpected audit events
Use the dashboard and app overview first, then open the specific service that needs attention.
Weekly checks
Review:
- organizations that still need setup
- users without expected organization access
- pending invitations that should be resent or revoked
- inactive or unused sign-in methods
- webhook endpoints with repeated failures
- API keys that have not been used recently
- support issues caused by unclear hosted Auth or email copy
Monthly checks
For production-facing apps:
- rotate or review sensitive credentials according to your policy
- check provider callback URLs
- review enabled social and SSO providers
- export or review audit logs if your compliance process requires it
- test password recovery and verification
- send a webhook test event
- review email templates and legal links
New customer onboarding runbook
When onboarding a new customer organization:
- Create the organization.
- Confirm the slug and display name.
- Invite the first operating member.
- Confirm the invitation email was sent.
- Confirm the member accepted access.
- Add or import end users if needed.
- Confirm Auth policy for the organization.
- Confirm webhooks are subscribed if downstream systems need events.
- Review the organization overview readiness cards.
Incident triage
When something breaks, identify the affected layer first:
| Problem | Start here |
|---|---|
| User cannot sign in | Auth settings, hosted Auth page, user status, email verification. |
| Invitation not received | Organization invitation state, email sender, template, delivery route. |
| Imported users missing | Import result, selected app, duplicate or failed rows. |
| Backend missed an event | Webhook deliveries, receiver logs, endpoint subscriptions. |
| Integration stopped working | API key state, recent rotations, backend secret storage. |
| Unexpected configuration change | Audit logs filtered by actor, app, and action. |
Change management
Before changing a production-facing app:
- identify the affected service
- decide whether users are impacted immediately
- take screenshots or notes of the current setting
- make the smallest change possible
- run the related smoke test
- check audit logs
- document the change in your internal runbook
Handoff checklist
When one team hands Switera operations to another:
- confirm app ownership
- list active sign-in methods
- list sender domains and support mailboxes
- list active webhook receivers
- confirm where backend secret keys are stored
- share the audit review process
- share the support path for failed login, invite, email, and webhook issues
Related pages: