Evisort
Connect Evisort to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Evisort connection as digital signature evidence. Automated collection is not available for this provider yet.
| Category | Digital Signature |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Evisort:
- Sign in to Contract Management and Document Intelligence (formerly Evisort) as an administrator.
- Click Admin, then click Integrations.
- On the API Management tab, click Generate new API key and copy the key.
- Existing keys are listed in the same section; active keys show Enabled in the Status column, and the trash icon next to a key deletes it.
Where to find the other values:
- Base URL (optional): Workday's Salesforce connector setup gives the API endpoint base URL as https://api.evisort.com/.
Evisort was acquired by Workday; the product is now Workday Contract Management and Document Intelligence (Contract Intelligence / CLM, powered by Evisort AI), documented on doc.workday.com. Generating a key requires a subscription to the Contract Management and Document Intelligence API integration and an administrator. Workday documents no read-only or scoped key option. In its Salesforce connector guide, Workday says the API key determines the user associated with all API actions and has a dedicated administrator account set up the key. Keys don't expire; Workday recommends rotating them periodically. Whether the key is shown only once is not stated. The old developer portal (developers.evisort.com) no longer serves content ('Project not found for custom domain').
Source: doc.workday.com, doc.workday.com, checked 2026-10-07.
-
On Compliance › Connectors, open Evisort, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
Evisort publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
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