Copper

Connect Copper to collect crm evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Copper:

   1. Sign in to the Copper web app.
   2. Go to System settings › API Keys and click GENERATE API KEY.
   3. Copy the key and paste it into API key.

   Where to find the other values:

   • Email: The email address of the Copper user who generated the API key; Copper requires it with the token on every request.
   • Access token (optional): Only for OAuth integrations; leave empty when using an API key.

   Copper documents no read-only key; the key carries its user's access. Users can hold multiple tokens; admins can see all user-generated tokens and generate new ones. The docs do not say whether the key is shown only once.

   Source: developer.copper.com, checked 2026-10-07.

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

   Field	What to enter
   API key	Optional. Stored encrypted and never shown again.
   Email	Optional.

   Or, instead: Access token (optional).

3. Click Connect with token.

Frameworks

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

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