Under Connections (/connections) you manage organization-wide credentials that projects can use:
| Group | Purpose |
|---|---|
| Mailtrap | Outbound mail via Mailtrap – status, plan, and sending domains right in the platform |
| Email (SMTP) | Outbound mail from backends via a generic SMTP account |
| Google / Firebase | Push notifications for apps |
| Sentry | Error tracking for apps, websites, and backends |
Mailtrap and SMTP credentials appear together in projects under the Mail account picker. For details on the Mailtrap tile (API token, status, DNS checks for sending domains), see Setting up email delivery with Mailtrap.
Google / Firebase
You can connect Firebase in two ways:
- Service account JSON (recommended) – paste a JSON key from Google Cloud / Firebase
- Connect with Firebase (OAuth) – authorize a Google account; shown with a Beta badge while the platform app is not yet approved in Google Cloud
Step-by-step: Firebase: Credentials.
When editing an app, enable Firebase under Features and pick the connection. Where possible, the platform copies existing Firebase app configs (web/iOS/Android) into generated project files.
Sentry
You can connect Sentry in two ways:
- OAuth (“Connect with Sentry”) via a Sentry Public Integration for sentry.io – cloud only
- API token with host (cloud or custom instance URL), organization slug, and token
Step-by-step including required token scopes: Sentry: Credentials.
When you enable Sentry under Features for an app, homepage, or backend, the platform creates the matching project in your Sentry organization and writes the DSN into the generated configuration.
See also
- Firebase: Credentials – service account JSON and OAuth (Beta)
- Sentry: Credentials – create a token and fill in the fields
- Email delivery – SMTP details and Mailtrap
- Error tracking – how errors land in projects
- Working with Sentry – reading issues and mapping releases