Sign in
Reeve.Sign · Documenso

Sign

Reeve.Sign is consumed as a Documenso package/embed — there is no HTTP substrate route, so a fresh tenant cannot originate a signing token in-app. This seed ships the embed and documents the origination paths a provisioned tenant would wire in.

Signing not provisioned

embed-only template

This tenant ships only the client-side Documenso embed widget (@documenso/embed-react).

The embed can display a signing flow but cannot originate one — mounting it needs a recipient signing token, and minting that token requires a Documenso document-creation call the template deliberately does not carry. No Documenso API key or first-party signing secret ships in a tenant template, so a fresh tenant has no in-app way to create a document to sign.

To enable origination
  • Substrate seam (preferred). A host-key-guarded Reeve.Sign endpoint in reeve-services that wraps create_envelope_from_template and returns the recipient token, proxied like every other substrate module. Not yet exposed — reeve_sign is a package-only client with no HTTP route.
  • Provisioned Documenso org. A Documenso organization (API token + base URL) issued to this tenant out of band, with document creation and token minting handled by that operator — never by pasting a raw secret into this UI.

Preview an existing token

advanced

Only if you already hold a token issued externally (e.g. by your provisioned Documenso org). The template cannot originate one — the embed talks to Documenso directly.

No document loaded

With an externally-issued signing token, the Documenso embed mounts here. Without a provisioned origination path (above), a fresh tenant has no token to paste.