Safeguard Docs
Compliance ConnectorsSetup by categoryDigital Signature

RightSignature

Connect RightSignature to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Record your RightSignature connection as digital signature evidence. Automated collection is not available for this provider yet.

CategoryDigital Signature
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In RightSignature:

    1. Make sure the account is on a ShareFile Premium or ShareFile Industry Advantage plan (or a trial with API access granted by an API specialist); trial accounts have no API access by default.
    2. Log into your RightSignature account and request an API key.
    3. Once RightSignature approves the key, copy the Private API Token (plus the Client ID and Client Secret) from your API credentials and paste the Private API Token into Safeguard.

    Where to find the other values:

    • Base URL (optional): Leave blank; the public API is documented at https://api.rightsignature.com.

    RightSignature's public documentation does not cover every step.

    Source: api.rightsignature.com, api.rightsignature.com, checked 2026-10-07.

  2. On Compliance › Connectors, open RightSignature, click Connect, choose API token and fill in:

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. Click Connect with token.

Frameworks

RightSignature 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.

FrameworkEvidenceControlsTests
SOC2AttestationCC6.2, CC6.31
ISO/IEC 27001AttestationA.5.181
HIPAA Security RuleAttestation164.308(a)(3)1
PCI DSSAttestation7.2.41
NIST CSF 2.0AttestationPR.AA-051

These tests are switched on per workspace by the Safeguard team.

On this page