GRC Oversight

Dropbox Sign

Collect Dropbox Sign (HelloSign) account, team, and signature-request evidence through the read-only API to support e-signature and document-control audits.

Generic connector
Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

  • Team member inventory
  • Signature request activity and status
  • Account security settings
Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

  • Auth header value(secret credential)

Optional

  • API base URL
  • Auth header name
  • Evidence endpoints (JSON)
Where this evidence goes

Which frameworks this evidence supports

Dropbox Sign evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in Dropbox Sign evidence

Get a guided demo, or start by scanning any domain for free.