Mailgun

Connect Mailgun to collect communications platforms evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Mailgun:

   1. In the Mailgun dashboard, go to Account Settings and open the API keys page.
   2. Click Create key and fill in the form fields in the modal; where role selection is offered, choose the Admin role (the only role that can read the users on an account). Click the modal's Create Key button.
   3. Record the generated key secret right away; Mailgun shows it only once.

   Mailgun shows the secret only once, so copy it before you leave the page.

   Mailgun's public documentation does not cover every step.

   Role-based API keys (Admin, Analyst, Developer, Support) are available only on Enterprise and certain Business plans; in Mailgun's permissions table only Admin has Read on 'Users on an account', so no narrower role lists users. Missing: where the account's US or EU region is shown (for the Region field) was not confirmed from a fetched page. Click path labels come from a summarized extraction.

   Source: documentation.mailgun.com, checked 2026-10-07.

   The permissions Safeguard needs: list users.

2. On Compliance › Connectors, open Mailgun, click Connect, choose API token and fill in:

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.
   Region (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Mailgun and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Communications Platforms connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks