Integrations are the platform's connections to external services your tenant uses. Each integration is its own page under Integrations in the sidebar.
What ships today
Section titled “What ships today”- Email SMTP — for transactional emails (verification, recovery, OTP). The most-used integration. See Email SMTP.
What's coming
Section titled “What's coming”The platform is gradually wiring in integrations for:
- SMS providers — Twilio, Vonage, AWS SNS, etc. for SMS-based MFA.
- Slack — for ops-channel notifications (admin sign-ins, security events).
- PagerDuty — for high-severity incident escalation.
- Custom domain —
auth.cymmetri.cominstead of the platform default.
When these ship, they'll appear in Integrations. Each integration is opt-in; no integration is required for the tenant to function (the platform provides defaults where it can).
Per-integration shape
Section titled “Per-integration shape”Each integration page generally has:
- State — enabled / disabled.
- Credentials — typically an API key or username / password the integration needs. Stored encrypted on the platform; never displayed in plain text after entry.
- Configuration — integration-specific (sender email, sender name, regional endpoint, etc.).
- Test button — sends a synthetic operation to verify the integration works.
- Audit summary — recent events from / to the integration.
When the platform ships a default
Section titled “When the platform ships a default”For email specifically, the platform ships a default SMTP that works out of the box (low rate; for prototyping). For production, switch to your own SMTP / transactional email provider.
For SMS, the platform doesn't ship a default — SMS is a paid service with real per-send cost; tenants configure their own.
Each integration's lifecycle (added / configured / disabled / removed) records in audit under admin.integration_* events.