Integrations & settings
Project settings hold the connections a project uses: its database, and the mail, storage and Redis services that features build on. All of it is owner-only — no role or API key can read or change credentials — and every secret is encrypted at rest with the platform's key ring. Saved passwords and secret keys are write-only: the settings page shows masked values, and no API returns them.
One rule applies to every integration: the host is egress-validated at the moment of use, not just when saved. Private and internal network addresses are refused, so a stored configuration cannot later be re-pointed at infrastructure it should never reach.
The database
The project's MongoDB — see Getting started for attaching one. Also here:
- Export / import — a JSON dump of the project's collections, for backups or moving between environments. (Your true export path is always the database itself — it's yours.)
- Detaching is an administrative action that stops the project without touching your data; reattaching the same database restores everything.
Mail (SMTP)
Powers invitation emails, event send-email steps, auth schema verification and reset emails, and manual sends.
| Field | Notes |
|---|---|
| Host, port, secure | Your SMTP server; TLS as your provider requires |
| Username, password | Optional — some relays authenticate by network |
| From email, from name | The identity every send uses |
Every send — success or failure — is logged under Email templates → Logs with recipient, subject and source, so delivery problems are diagnosable without asking us. Email templates themselves are simple {{variable}} HTML documents, reusable across events and manual sends.
Storage (S3-compatible)
Backs the media library: endpoint, bucket, access key, secret key, optional region and public base URL (serve files via CDN/public host instead of signed URLs). Any S3-compatible provider works.
Redis
An optional connection (host, port, password, TLS) reserved for state-and-cache features. Note that endpoint response caching does not require it — that works out of the box.
Project settings
- Rename the project; its ID and APIs are unaffected.
- The settings page shows which database is attached with credentials stripped, plus the project's ID for API use.
Sending email by hand
Email templates → Send delivers a one-off templated email through your SMTP — gated on emails.send, which is deliberately a separate permission from reading logs: your From address is a trusted identity, and the ability to send as you is the dangerous half.