> This page is for RakeSign.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# Standing delegation

Standing delegation lets an organization apply a signer's approved signature to documents from one approved template revision.
An administrator or integration can request consent.
Only the signer can grant it.

Delegation must be enabled for the organization.
Eligible signers must be organization members or use a verified organization domain.
Contact CloudRaker support if your organization needs delegation enabled.

## Consent and document signing

These are separate steps:

1. RakeSign sends the signer a consent request for a named template revision.
2. The signer verifies their email and accepts or declines.
3. After acceptance, RakeSign can apply that consent to eligible documents.
4. Each delegated signature records its grant and consent evidence in the audit trail.

An administrator cannot activate a grant by changing its status.
The API never returns the signer's consent link or signature image.

## Request consent

Use `delegations:write` and a saved template you can manage.
Send its current version:

```bash
curl --fail-with-body -sS \
  https://api.cloudraker.com/v1/signing/delegations \
  -H "Authorization: Bearer $RAKESIGN_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "templateId": "YOUR_TEMPLATE_ID",
    "templateVersion": 3,
    "name": "Jordan Lee",
    "email": "jordan@example.com",
    "language": "en"
  }'
```

A new grant starts as `pending`.
Its `id` identifies the consent record, not a signing document.
Requesting the same scope can return its existing grant.
It cannot override a decline or revocation.

## Read status and evidence

`GET /delegations` returns `items` and `nextCursor`.
Use `limit` and `cursor` for pagination.
You can filter by `templateId` and `status`.

`GET /delegations/:id` includes consent evidence and recent delegated signatures available to the caller.
It also includes links between previous and renewed grants.

| Status     | Meaning                                     |
| ---------- | ------------------------------------------- |
| `pending`  | The signer has not accepted the request.    |
| `active`   | The signer accepted consent for this scope. |
| `declined` | The signer refused consent.                 |
| `revoked`  | Future use of this grant has stopped.       |

Use `allowedActions` to show the actions available for the current grant.
The API checks the grant again when you request an action.

## Send under a grant

First create a document with `POST /templates/:id/instantiate`.
Use the template's current `version` in that request.
The server binds the new draft to its template revision and prepared PDF.

Saved rich-text and Word templates can render new values and recipient details while preserving that binding.
Their source content and supporting files must stay unchanged.

Then update the draft with its current version:

```json
{
  "version": 4,
  "signingMode": "delegated",
  "delegation": {
    "templateId": "YOUR_TEMPLATE_ID",
    "templateVersion": 3
  },
  "allowReassignment": false
}
```

Send it with `POST /documents/:id/send`.
The key needs `documents:send` and `delegations:use`.
Draft creation and editing also need their normal document and template scopes.

If consent is missing, the recipient enters `awaiting_consent` and receives a consent request.
An active grant permits the delegated signature.
A declined or revoked grant does not silently become active when another document arrives.

## Current limits

* Every recipient must use delegation. Mixed manual and delegated signing is unavailable.
* Use one stage with `mode: "all"` and signer roles.
* Approval stages, delays, conditions, and recipient reassignment are unavailable.
* Use `placement: "page"` or `placement: "tags"`. Visual field placement is unavailable.
* The document must come from the saved template's current revision.
* Replacing its PDF, changing source content, or adding or replacing supporting files removes delegation eligibility.
* Rendering again from a Compose template or external style removes eligibility because those sources can change outside the saved revision.

The server enforces these limits for both the app and API.
Changing template content does not extend an older grant to the new revision.
Prepared PDF copies remain eligible when their content stays unchanged.
After an incompatible edit, instantiate the original template again or save a new revision and request consent for it.

## Resend, revoke, and renew

All paths below use `/v1/signing`:

| Route                          | Behavior                                           |
| ------------------------------ | -------------------------------------------------- |
| `POST /delegations/:id/resend` | Send a new consent link for a pending grant.       |
| `POST /delegations/:id/revoke` | Stop future use of a pending or active grant.      |
| `POST /delegations/:id/renew`  | Request new consent after a decline or revocation. |

Consent email requests have a 24-hour cooldown.
A `429` response includes `Retry-After`.
Wait before requesting another email.

Renewal requires a reason of 5 to 1000 characters:

```json
{ "reason": "The signer asked to resume signing after returning to work." }
```

Renewal creates a pending grant linked to the previous decision.
It preserves the previous evidence and requires a new signer acceptance.
If the template revision changed, request consent for the new revision instead.

Revocation preserves completed signatures and their audit records.
The signer can also revoke consent and contest a delegated signature through their recipient controls.
Contestation is recorded; it does not rewrite the completed PDF.

## Legacy grants

Legacy consent can have `templateVersion: null`.
These grants remain separate from RakeSign grants bound to a saved template revision.
They do not authorize signatures on a new RakeSign revision.
Use a new consent request when adopting the RakeSign template workflow.