# Collect signatures

> Request signatures on a published version, follow each signer and verify the certificate.

Kind: guide · ~3 min · Verified v0.237.0 · Next: [Use stored secrets](https://pr-2197-stg.superartifacts.app/docs/secrets.md)

## Goal

Collect signatures on the exact agreement you approved.

## What you'll have

A request tied to one artifact version, each person's signing status, and a certificate when everyone signs.

## Needs

An Owner or Editor of the artifact, a connected agent with permission to request signatures, and each signer's name and distinct email address. Use one file up to 2 MiB, or a document published from an official document template with its declared source filled by the platform.

## Prompt

**Prepare a signature request.** Your agent checks the version and recipients with you before sending invitations.

```prompt
Help me collect signatures on a Super Artifacts agreement. Read https://superartifacts.app/docs/signatures.md first. Ask which artifact and version, and for each signer’s name, email and optional party label. Check that version is eligible; show me the version and recipients and wait for my confirmation before super_signatures request. Keep the existing audience. Return the request id and status, never signer credentials. Explain how people sign and how I follow, remind or withdraw the request.
```

```mermaid
flowchart TB
  V["Review version"] --> R["Request and pin"]
  R --> S["Code and consent"]
  S --> C["Everyone signs"]
  C --> P["Certificate; keep pin"]
  R --> E["Closed unsigned"]
  E --> U["Release if unheld"]
```

## Steps

1. Open the artifact and review the version. In **Signatures**, create a request, or ask your agent to use `super_signatures` with action `request`. Without a version number, it uses the published version.
2. Confirm up to 10 signers and an optional message of up to 500 characters. Sending emails each person their own link, valid for 14 days.
3. Each signer reads the document without a platform account, requests a six-digit email code, verifies it, accepts electronic signing, types their name and presses **Sign**. They can decline instead.
4. Follow progress in **Signatures**, or with action `status`. Use `remind` for pending signers, at most three reminders per signer, a day apart. Use `withdraw` to close an open request.

## Check it worked

Look for `completed` and the certificate. Every party receives the certificate and exact document by email. Its verification link checks the document fingerprint and sealed event chain. Treat signer links as private credentials.

An open or completed request pins its version against deletion. Editing the artifact creates another version; it does not change what was signed.

## If not

`unsupported_multifile` means republish as one file or an official document-template fill. `source_not_filled` means the declared source was not filled by that template. `document_changed` requires a new publication and request. `signing_unconfigured` needs the deployment operator; agents cannot supply the sealing key.

## Variations

Use the [REST operations](https://pr-2197-stg.superartifacts.app/docs/reference/api-endpoints.md) or [SDKs](https://pr-2197-stg.superartifacts.app/docs/sdks.md) for an integration. They expose requesting, status, reminding and withdrawal. No agent API signs for a person.

## Next

Read [signature evidence, limits and retention](https://pr-2197-stg.superartifacts.app/docs/concepts/signing.md), [MCP tools](https://pr-2197-stg.superartifacts.app/docs/reference/mcp.md) and [plan limits](https://pr-2197-stg.superartifacts.app/docs/reference/limits.md).
