SignNow
Connect SignNow to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect SignNow to collect digital signature evidence with automated compliance tests, switched on per workspace.
| Category | Digital Signature |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| SignNow's guide | docs.signnow.com |
Connect with an API token
-
In SignNow:
- Sign in to SignNow as an organization admin (the member list is only available to admins).
- Go to the API dashboard (
https://app.signnow.com/webapp/api-dashboard) › Apps and Keys and select your application (an API key is generated automatically when you create an application). - On the API Keys tab, copy the API key and paste it into Safeguard's Access token field (it is sent as
Authorization: Bearer).
Where to find the other values:
- Organization ID: Not shown in a documented UI location. SignNow's API returns it from
GET /v2/organizations(Get admin's organizations) when called with the same key.
SignNow's public documentation does not cover every step.
SignNow describes API keys as "less secure" and non-expiring compared with OAuth access tokens (POST /oauth2/token, which expire and need refreshing); there is no read-only key. That the API key is accepted in place of a bearer token on the organization members endpoint was not verified. Not sourced: where the Organization ID appears in the SignNow web app.
Source: docs.signnow.com, docs.signnow.com, checked 2026-10-07.
The permissions Safeguard needs:
organization admin. SignNow shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. -
On Compliance › Connectors, open SignNow, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Organization ID Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read SignNow 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 | 2 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 2 |
| PCI DSS | Automated tests | 7.2.4, 8.2.5 | 2 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- Digital Signature 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