Basecamp
Connect Basecamp to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Basecamp to collect ticketing evidence with automated compliance tests, switched on per workspace.
| Category | Ticketing |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Basecamp's guide | github.com |
Connect with an API token
-
In Basecamp:
- Register an app at launchpad.37signals.com/integrations; Basecamp assigns a client_id and client_secret.
- Run the OAuth 2 flow as an account administrator or owner: send the user to the authorization endpoint, receive the verification code, and trade it for an access token with a backchannel request.
- Use the access token as a Bearer token.
Where to find the other values:
- Account ID: Call GET https://launchpad.37signals.com/authorization.json with the token; the id of the Basecamp account in the response is the Account ID. API URLs take the form https://3.basecampapi.com/<ACCOUNT_ID>/.
Basecamp issues this credential through its API or its support team, not through its admin screens.
Basecamp has no personal token screen; tokens come from the OAuth 2 flow and currently last two weeks, with refresh tokens issued. GET /people.json returns everyone visible to the token's user, and full email addresses only for account administrators and owners (and the person themselves), so authorize as an admin or owner. The fetched docs do not mention a read-only scope.
Source: github.com, github.com, checked 2026-10-07.
The permissions Safeguard needs. Basecamp shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it.
-
On Compliance › Connectors, open Basecamp, click Connect, choose API token and fill in:
Field What to enter Account ID Required. Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Basecamp 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC6.2, CC6.3 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Ticketing 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