Smartsheet
Connect Smartsheet to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Smartsheet 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 |
| Smartsheet's guide | developers.smartsheet.com |
Connect with an API token
-
In Smartsheet:
- Sign in to Smartsheet (API access tokens need a Business or Enterprise plan). System admins see additional user attributes when the API lists users.
- Click your account (profile image) and open Personal Settings, then select the API Access tab.
- Click Generate new access token, name the token and select OK.
- Copy the token value now; this is the only time it is visible.
Smartsheet shows the secret only once, so copy it before you leave the page.
Smartsheet's public documentation does not cover every step.
API access tokens are available on Business and Enterprise plans. Tokens are revoked from Manage API Access Tokens, and admins can set an access token expiration time in Admin Center. The help page links to Smartsheet Regions but gives no region-specific steps, so the Region field's location is not sourced.
Source: help.smartsheet.com, developers.smartsheet.com, checked 2026-10-07.
The permissions Safeguard needs:
READ_USERS,System Admin. Smartsheet shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. -
On Compliance › Connectors, open Smartsheet, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Region (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Smartsheet 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