TimeSheets sends email through Amazon SES. This is the only thing the app sends outside Atlassian.
1. Built-in sender or your own
| Option | What it means |
|---|---|
| Built-in | Mail goes through our SES account. Nothing to configure. We are a processor and AWS a sub-processor for the message in transit |
| Your own SES | You supply AWS credentials and mail goes through your account. No third party in the path |
Your own credentials always win over the built-in sender. They are stored write-only — no screen and no API returns them once saved.
Leave notification emails include the leave type name. If you have Sick Leave enabled, those words travel with a person's name through whichever email path you choose. Using your own SES account keeps that inside your infrastructure.
2. Editing templates
Every notification has an editable template — subject and body. Edit them under Admin Settings → Email to match your own tone or language.
3. Smart values
Templates support placeholders that are substituted when the mail is sent — the person's name, the dates, the project, a link back into the app. The editor lists the values available for the template you are editing.
4. Bounces and suppression
SES reports bounces and complaints back to the app. An address that hard-bounces or reports a message as spam is added to a suppression list and is not emailed again.
This protects delivery for everyone on your site: a sender that keeps mailing dead addresses gets throttled. Suppressions are kept indefinitely by default — see Privacy & Data Handling for the retention control.
5. Test sends
Send a test to yourself after changing credentials or a template. It is the quickest way to find a misconfigured sender before a real notification depends on it.