Restrict signing contexts per Signer

By default, once a Signer is added to a Signature Request, they can sign it from any Yousign surface: the Inbox (if they have a Yousign account) or the Signature Portal.

This isn't always what you want. For example, if you deliver the Signature Request through your own product (delivery_mode: none), the signing experience already lives inside your journey. You may not want the same Signature Request to also become signable from Yousign's Inbox or Signature Portal, since that context doesn't belong to your integration.

disabled_signing_contexts lets you disable one or more of these contexts on a per-Signer basis, without changing how the Signature Request behaves anywhere else.

How it works

disabled_signing_contexts is an array field on the Signer resource. It lists the contexts where the Signature Request should be unavailable for that Signer. Any context not listed remains fully enabled.

Default behavior: when disabled_signing_contexts is omitted or set to [], all contexts are enabled and the Signer can access the Signature Request normally.

When a context is disabled, the Signature Request is still listed in the Inbox (the Inbox always shows all Signature Requests a Signer is involved in), but the document is not consultable and the signing flow is not accessible. A guidance message is displayed instead, inviting the Signer to contact the sender.

Set disabled contexts when creating a Signer

Pass disabled_signing_contexts in the Signer creation payload:

{
  "info": {
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "[email protected]",
    "locale": "en"
  },
  "signature_level": "electronic_signature",
  "disabled_signing_contexts": ["inbox", "signature_portal"]
}

This creates a Signer for whom the Signature Request is not accessible from either the Inbox or the Signature Portal.

What Signers see when a context is disabled

The Inbox keeps its "list everything" principle: a Signature Request is never hidden from a Signer just because a context is disabled.

In the Inbox, a Signature Request with inbox disabled is still listed, the same way Advanced or Qualified Electronic Signatures are shown before identity verification. The Signer can't open it: the access button is hidden and a message invites them to contact the sender.

In the Signature Portal, if signature_portal is disabled, the Signer reaches the portal but the content is not accessible and the same guidance message is shown instead of the signing flow.

*disabled_signing_contexts can only be managed through the public API, there is no equivalent setting in the App. A Signature Request created via the API with this parameter keeps the same restrictions if it's later handled from the App.*