Teamwork
Connect Teamwork to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Teamwork 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 |
| Teamwork's guide | apidocs.teamwork.com |
Connect with an API token
-
In Teamwork:
- Sign in to your Teamwork.com site as the user whose API key Safeguard will use.
- Click your profile icon in the top right corner and select Edit My Details.
- Go to the API & Mobile tab and click Show your Token.
- Copy your API key.
Where to find the other values:
- Site: Your site address, https://<site>.teamwork.com; enter the part before .teamwork.com.
The API key is the user's own key and carries that user's rights; Teamwork documents no read-only key. The Access token alternative needs an app registered in Teamwork's Developer Portal and an OAuth 2.0 flow; the portal's click path was not documented on the pages fetched. one_time_display is false because the key can be shown again with Show your Token.
Source: support.teamwork.com, apidocs.teamwork.com, checked 2026-10-07.
The permissions Safeguard needs:
site administrator. Teamwork shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. Safeguard's compliance tests for Teamwork need the credential on the API token tab: an OAuth connection cannot read everything they check. -
On Compliance › Connectors, open Teamwork, click Connect, choose API token and fill in:
Field What to enter Site Optional. The part before .teamwork.com in your address. API key Optional. Stored encrypted and never shown again. Or, instead: Access token (optional).
-
Click Connect with token.
Frameworks
Safeguard's automated tests read Teamwork 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