Overview
Email default settings are the company-wide gateway configuration that every Application inherits when it sends email. Things like your gateway provider, sending limits, link tracking, and the credentials the platform uses to actually deliver mail all live here.
Setting these centrally means you don't need to configure an email gateway for every new Application from scratch. New Applications pick up the defaults automatically, and you only step in to override them when an Application has different needs — its own gateway, a stricter send cap, or different tracking rules.
The settings on this page also act as the source of truth for any Application that hasn't ticked Override company defaults. So a change here ripples out across every Application that's still following the default configuration.
You'll need System Administration access to view or change the email gateway settings. If you can't see the option in your settings, have a quick chat with whoever manages user permissions in your team — they can either lift your access or make the change for you.
What each setting does
Here's a quick rundown of the email gateway settings and what each one controls. The same fields appear at the Application level if you ever need to override these defaults for a specific use case.
| Setting |
What it does |
| Test mode |
When enabled, the platform will generate and validate every message but won't actually send anything. Handy for testing a new template or running a campaign end-to-end before real emails go out the door. Just remember to switch it off again before you go live. |
| Max send per hour |
Caps how many emails the platform will send in a rolling hour. Useful for throttling large sends to protect deliverability or to stay within your gateway provider's rate limits. Set this to 0 for unlimited (no cap). |
| Enable link tracking |
Wraps the links in your emails so the platform can record clicks and report on engagement. Turn this on if you want to see which links are pulling their weight in the Send Activity dashboard. |
| Require secure links |
Adds an extra layer of security to all tracked links. We recommend leaving this enabled by default. Only turn it off in rare cases — for example, when SMS character counts are tight and a longer secure URL would push the message over the limit. |
| Gateway |
The outbound gateway or server your messages are sent through. |
| Server / endpoint |
The URL the platform uses to connect to your chosen gateway. This is usually pre-filled based on the gateway you select, but you can customise it if your provider has given you a specific endpoint to use. |
| Account Id |
The account identifier from your gateway provider. Some providers use this to route messages to the right account or to apply the correct billing. |
| Username / Api key |
The credential the platform uses to authenticate with your gateway. You'll get this from your gateway provider's dashboard or admin area. |
| Password / Api secret |
The matching secret that pairs with your username or API key. Treat this like any other password — keep it confidential, and rotate it if you suspect it's been exposed. |
Tip
If you're setting up a new gateway for the first time, flick on Test mode and run a few sends through a test template before going live. It's the easiest way to confirm your credentials and endpoint are right without risking a real send going to a real recipient.
