# Signatures: agents ask, people sign

> Ask named people to sign one published version, follow the request, and get a sealed certificate. Your agent can send it; only a signer can sign.

Kind: concept · ~3 min · Verified v0.185.0 · Next: [MCP tools](https://superartifacts.app/docs/reference/mcp.md)

```mermaid
%% hand-drawn: public/docs/diagrams/signing.svg is an animated SVG; this is its text twin.
flowchart LR
  A["Agent: super_publish, one file"] --> V["Version, pinned"]
  A -->|super_signatures request| R["Request open"]
  R -->|emailed link| S["Each signer"]
  S -->|six-digit code, typed name, Sign| R
  R -->|all signed| C["Sealed: certificate to every party"]
  A -.-x|cannot sign| S
```

A **signature request** asks named people to sign **one published version** of one artifact. Each signer opens their own link, proves they hold the inbox, types their name and signs. When everyone has signed, the platform seals the record and every party gets a certificate.

## What your agent can do

With `super_signatures` it can **request** signatures on a version, read a request's **status**, **withdraw** an open request, and **remind** a signer who has not signed. It cannot **sign**. No tool, key or workspace role reaches the step that signs: only the signer's own link, plus the code sent to their inbox, does.

## What can be signed

One version holding **one file of up to 2 MiB**. Publish the agreement as a single file; a version with several files is refused. A request names at most 10 people, and each link lasts 14 days.

A version that is part of an open or completed request is **pinned**: nobody can delete it, from the dashboard or through the agent, while that request holds it. See [Versions](https://superartifacts.app/docs/concepts/versions.md).

## What the signer sees

An email with a link. The link opens the document; no account is needed. To sign, they ask for a **six-digit code**, sent to the same address and good for ten minutes, then tick a consent box, type their name and press **Sign**. Five wrong codes lock that signer out. They can decline instead.

## The evidence kept

- the document's fingerprint (a SHA-256 hash), taken again at the moment of signing, so a changed document cannot be signed;
- the code check, the consent wording, the typed name and the time of every step;
- each signer's IP address and browser, encrypted, shown only in the certificate the parties download;
- a chain of every event, sealed so that any later change shows.

Every party gets the certificate and the exact document by email. Anyone holding the certificate's link can check it on a public page that says whether it is valid.

## What it is, and is not

This is a **simple electronic signature** of the kind the US ESIGN Act and UETA recognise: intent, consent, attribution and a kept record. It is not a qualified or advanced signature, and it checks no identity document and sends no code by text message.

## Where it is on

The Signatures tab on an artifact appears only where signing is switched on, and a deployment without its sealing key refuses a request with `signing_unconfigured`.

Next: [Secrets](https://superartifacts.app/docs/concepts/secrets.md)