Email (Amazon SES)
Communication · platform_managed · Always-on
ThirdSentry-managed transactional email delivery via Amazon SES. Reviewer notifications, audit-trail digests, vendor questionnaire invitations, and remediation reminders ship through a verified SES identity with the bounce + complaint pipeline configured for deliverability.
- Authentication
- platform_managed
- Sync cadence
- —
- Stale threshold
- —
- Category
- Communication
Evidence this connector produces
Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.
How to connect
No customer setup needed. ThirdSentry manages the SES identity, deliverability monitoring, and bounce/complaint handling. Replies to platform emails reach the ThirdSentry support team.
- 1Sender and reply-to
Platform emails send from [email protected]. Replies go to [email protected], so nothing lands in a dead inbox.
- 2Custom sending domain (Enterprise tier)
Enterprise customers can request a custom-domain SES configuration (DKIM + SPF setup) so platform emails appear to send from notifications@<their-domain>. Contact support to provision.
Security model
Every connector ships behind the same auditor-grade primitives: not just RBAC config, but architectural enforcement.
Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.
Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.
Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.
Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.
If this connector hasn't synced in —, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence. Neither do we.
We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.
Ready to connect Email (Amazon SES)?
Connect from Settings → Integrations , typically under 5 minutes. Or talk to us first.