# After signing: check, download, cancel

[Video: What a signed page shows when it is edited, in 22 seconds, no sound](/images/videos/signplus/changes-light.b0f2519e.mp4)

What the video shows:

1. A signed page shows Page signed and valid in the byline. Its tooltip says the page has not been modified since.
2. Someone changes a term on the page. The byline changes to Page signed but modified.
3. The panel says the page has been modified after signing, with a link to compare.
4. Compare opens Confluence’s comparison of the two versions, with the change marked.
5. The signed document still holds the version that was signed.

Once a page has a signing, anyone who can view the page sees its state, without opening
anything: the SignPlus item under the title changes its icon and its words.

## What the byline says

| Byline | Meaning |
|---|---|
| **Sign this page** | No signing on this page, or the last one was declined or cancelled |
| **Signing in progress** | Out for signature, and the page has not changed since it was sent |
| **Page modified during signing** | Out for signature, and someone has edited the page since it was sent |
| **Page signed and valid** | Everyone has signed, and the page is exactly what they signed |
| **Page signed but modified** | Everyone has signed, and the page has been edited since |

Hover over it for a sentence that says the same at more length. Select it to open the panel.

## What the panel says

**Latest signing** shows the newest signing on the page:

| Heading | Under it |
|---|---|
| **Signature pending** | *Signing in progress*, and how many of the signers have signed, for example *0 / 1 signers have signed* |
| **Signature valid** | *Page has not been modified after signing* |
| **Signature not valid** | *Page has been modified after signing*, with a **compare** link |

**compare** opens Confluence's own comparison between the version that was signed and the
current one, so you see what changed and who changed it.

<Aside type="note" title="How the check works, and what it covers">
When a signing starts, SignPlus stores a SHA-256 of the page's space id, page id and version
number. Confluence moves the version on every edit, so the panel recomputes the hash and compares.

**It detects that the page changed, not what changed.** Confluence's comparison answers that.

**It hashes the page's identity, not the rendered document.** Changing the export styling does
not make a signed page read as modified. The signed document's own SHA-256 is computed separately
and sent to Dokobit as the document's digest.

**It does not need anyone to open the page.** The same check runs when a signed page is saved,
and can notify another system: see the [signed-page webhook](../automation/#when-a-signed-page-is-edited).
</Aside>

## Where the signed file is

When the last signer has signed, the signed file is attached to the page, named after the
document: `Service agreement.asice`, or `.pdf` for the PDF format. Get it from:

- **Download signed document** on the **Latest signing** tab;
- the page's own attachments;
- **Actions**, then **Download**, on **SignPlus: your signings**;
- the **download** link in the signing's details.

## Signing details

**View signing details** opens a dialog with the document's name, the page version that was sent,
the status, when it was created and last updated, and who started it.

Under **Signers** it says how many have signed, and lists everyone with their role, status and
the time they signed. **Show** narrows the list to **Not signed yet**, **Signed** or **Declined**,
which is how to find who to chase on a signing sent to hundreds of people. A signing sent to a
group lists its members, a hundred at a time, with **Load more** for the rest.

**All signings** on the panel lists every signing on the page, newest first, and opens the same
details.

## Cancelling or deleting a signing

The details dialog offers one of two actions, and only to someone allowed to use it.

| | Cancel signing | Delete |
|---|---|---|
| **Offered** | While the signing is still out | Once it has finished: signed or declined |
| **What it does** | Removes the document from Dokobit for every signer, so nobody can sign it, and lifts the page restrictions it set | Removes SignPlus's record of the signing and lifts the edit lock it left on the page. **The signed file stays attached to the page** |
| **Who can** | The person who started it, or anyone who can edit the page | **A Confluence administrator.** The site can add space administrators, page editors or the person who started it: see [deleting signings](../configure/#deleting-signings) |

Both ask once more before they act. After a delete, the byline shows the page's previous signing,
or **Sign this page** if there was none, because the record it compared against is gone.

<Aside type="caution" title="Delete is about the record, not the document">
Deleting a finished signing does not delete the signed file. Remove the attachment as you would
any other, if that is what you want. Without the record, nothing on the page says any more that
it was signed, or whether it has changed since.
</Aside>

## What happens to the page

| When | Edit lock | Viewing restriction |
|---|---|---|
| The signing starts | Applied, if chosen | Applied, if chosen |
| **It completes** | **Stays on** | Lifted |
| It is declined | Lifted | Lifted |
| It is cancelled, or its record deleted | Lifted | Lifted |

The edit lock stays after a completed signing because it exists so that what people signed cannot
change. It is a Confluence page restriction held by SignPlus alone. A space administrator can
always remove it, and on Premium and Enterprise an organisation administrator can bypass it with
an audit-logged admin key: Confluence guarantees that recovery path, so the lock raises the bar
and the hash is what detects an edit.

## Related

- [Sign a page](../sign-a-page/)
- [What a signer sees](../for-signers/)
- [Automation and webhooks](../automation/)

---

A problem or a question? Write to [support@oktul.com](mailto:support@oktul.com) or open a request in the [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals). Both reach the same service desk, so either way the request gets a reference and an SLA measuring the response.