Esper

Connect Esper to collect mdm evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Esper:

   1. In the Esper Console, open the API Key Management section.
   2. Select Create Key, enter a unique API key name and an optional description, and click Create Key.
   3. Copy the key and close the window.

   Esper's public documentation does not cover every step.

   The fetched page mentions no role or permission choice during key creation, so the Viewer grant could not be confirmed. You can view and copy the key again later from API Key Management (ellipsis › View). The Enterprise ID, needed for API calls and specific to a tenant, is copied from the icon next to Enterprise ID at the top right of the API Key Management section; the page does not say where the tenant name is shown.

   Source: help.esper.io, checked 2026-10-07.

   The permissions Safeguard needs: Viewer.

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

   Field	What to enter
   Tenant	Required. The part before .esper.cloud in your address.
   API key	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Esper 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

• MDM 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