Safeguard Docs
Compliance ConnectorsSetup by categoryTicketing

Productboard

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

Connect Productboard to collect ticketing evidence with automated compliance tests, switched on per workspace.

CategoryTicketing
Connect withAPI token
What a connection producesAutomated compliance tests
Productboard's guidedeveloper.productboard.com

Connect with an API token

  1. In Productboard:

    1. In Productboard, go to Settings › Integrations › Public APIs › Access Token.
    2. Click the plus (+) icon to generate a new token.
    3. Copy and store the token; this is the only time you'll be able to see it.

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

    API tokens need the Pro plan or higher (not Essentials). The docs don't mention scopes for access tokens; members:read and members:pii:read appear to apply to OAuth only, so the token can't be narrowed to them. The required role is not stated.

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

    The permissions Safeguard needs: members:read, members:pii:read.

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

    FieldWhat to enter
    Access tokenRequired. Stored encrypted and never shown again.
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Productboard 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.33
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.6.5, A.8.23
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4)3
PCI DSSAutomated tests7.2.2, 7.2.4, 8.2.53
NIST CSF 2.0Automated testsPR.AA-01, PR.AA-053

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

On this page