Trello
Connect Trello to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Trello 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 |
| Trello's guide | developer.atlassian.com |
Connect with an API token
-
In Trello:
- Sign in to Trello as an Enterprise admin and open the Power-Up admin portal at https://trello.com/apps/admin. Open your Power-Up (create one if you have none).
- Go to the Trello Auth tab and select Generate a new API Key. Copy the API key.
- Generate the token with read-only scope by opening https://trello.com/1/authorize?expiration=never&scope=read&response_type=token&key=<your API key> (scope can be read, write, account; expiration can be 1hour, 1day, 30days or never). You can also click the Token link to the right of the API key on the admin page.
- Click Allow. Trello shows the full user token in the browser window; copy it.
Where to find the other values:
- Enterprise ID: Not documented in the pages fetched. It is the {id} used in the Enterprise API routes (/enterprises/{id}/...).
Trello's public documentation does not cover every step.
Needs Trello Enterprise. The Enterprise members route requires the read:enterprise:trello scope; the Enterprise audit log route requires an Enterprise admin token, so create the token as an Enterprise admin. Trello's docs treat the API key as not secret; the token is the secret. Where the Trello UI shows the Enterprise ID was not found in official docs during this pass.
Source: developer.atlassian.com, developer.atlassian.com, developer.atlassian.com, checked 2026-10-07.
The permissions Safeguard needs:
read:enterprise:trello. Needs Trello's Enterprise plan. Trello 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 Trello need the credential on the API token tab: an OAuth connection cannot read everything they check. -
On Compliance › Connectors, open Trello, click Connect, choose API token and fill in:
Field What to enter Enterprise ID Required. API key Required. Stored encrypted and never shown again. API token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Trello 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