Safeguard Docs
Compliance ConnectorsSetup by categoryCRM

Copper

Connect Copper to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Copper to collect crm evidence with automated compliance tests.

CategoryCRM
Connect withAPI token
What a connection producesAutomated compliance tests
Copper's guidedeveloper.copper.com

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:

    FieldWhat to enter
    API keyOptional. Stored encrypted and never shown again.
    EmailOptional.

    No field is required on its own: the form accepts more than one set of credentials. Fill in one complete set.

    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.

FrameworkEvidenceControlsTests
SOC2Automated testsCC6.2, CC6.32
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.6.52
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4)2
PCI DSSAutomated tests7.2.4, 8.2.52
NIST CSF 2.0Automated testsPR.AA-01, PR.AA-052

On this page