> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/using-hippoly/e-signing/sign-a-document.md).

# Sign a document

When someone sends you a document for e-signing, you'll receive a notification asking you to review and sign. This article describes the signing experience from the signer's perspective.

## How you get notified

How you receive the signing request depends on whether you are a workspace member or an external signer:

* **Workspace members** receive an in-app notification in Hippoly and can open the signing request directly from there.
* **External signers** (people who are not part of the workspace) receive an email from Scrive with a link to sign the document.

## Review and sign

{% stepper %}
{% step %}
**As a workspace member**, click the notification in Hippoly and then click the `Sign` button in the signing details. A new tab opens with the Scrive signing page.

**As an external signer**, click the link in the email you received. You are taken directly to the Scrive signing page.
{% endstep %}

{% step %}
On the Scrive signing page, you can read through the full document before signing. Take the time to review the content carefully.
{% endstep %}

{% step %}
Depending on the [signing method](/using-hippoly/e-signing/signing-methods.md) chosen by the sender, you may need to verify your identity, for example using BankID, MitID, SMS PIN, or another method. Follow the instructions on the Scrive signing page.
{% endstep %}

{% step %}
Once your identity is verified, confirm your signature. You'll see a confirmation that the signing is complete.
{% endstep %}
{% endstepper %}

## Decline to sign

If you don't agree with the document or are unable to sign, you can **reject** the signing request on the Scrive signing page. The sender will be notified that you have declined. You can optionally provide a reason for the rejection.

{% hint style="info" %}
Rejecting a signing request cancels the entire signing process. The sender can make changes and start a new signing if needed.
{% endhint %}

## Sequential signing

If the sender has set a signing order, you may see a status of **Waiting for prior signatures**. This means another signer needs to complete their signature before it's your turn. You'll be notified when it's time for you to sign.

## After signing

Once all signers have completed their signatures, the signed document is finalised and stored in Hippoly. All parties, both workspace members and external signers, are notified when the signing is complete.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.hippoly.com/using-hippoly/e-signing/sign-a-document.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.