The platform stores SMTP credentials per organization. Project backends and other services can use them to send transactional or notification email (password resets, orders, internal alerts).
What you configure here
- One credential per SMTP relay (for example Mailtrap, another provider, or your own outbound mail server).
- Fields such as host, port, username, password/API key, sender address, and sender name match what your framework or mail library expects for SMTP.
Typical flow
- Create an account or API access with your email provider (see SMTP setup with Mailtrap as a step-by-step example).
- In the Application Platform, under Email delivery, create an SMTP entry with the same values.
- Your generated project or backend reads the credentials from platform configuration and sends outbound mail through that relay.
Terminology
If you are unsure how SMTP relates to IMAP or POP3, read the short guide: SMTP, IMAP, and related protocols.
Security
- Prefer API keys or app passwords, not personal logins, whenever the provider supports it.
- Restrict provider permissions to sending only (no unnecessary mailbox access).