> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/initiate-and-sign-envelopes/signing-a-document/as-an-external-recipient-ad-hoc-user/reading-through-documents.md).
# Reading through documents
External users (Ad Hoc recipients) are participants who are not part of the emSigner internal user directory. When an external user’s signature or review is required, emSigner enables a secure, guided signing experience without requiring a full platform login.
***
#### 1. Email Notification
When the workflow reaches an external user, emSigner sends an email notification to the recipient.
The email includes:
* **Document name**
* **Sender name**
* **Sent date and time**
* A **Preview and Sign** action button
* Optional message from the initiator (if provided)
Clicking **Preview and Sign** initiates the signing process.
***
#### 2. Accessing the Document
After clicking **Preview and Sign**, the external user is redirected securely to emSigner.
* **No emSigner account or manual login is required** for external users.
* Access behavior depends on the authentication settings configured by the initiator.
***
#### 3. Additional Authentication (If Configured)
Based on workflow configuration, one or more verification steps may be required before the document is opened:
**OTP Verification (Optional)**
* A one-time password (OTP) is sent to the user’s registered email or mobile number.
* The user must enter the OTP to proceed.
**Liveness / Video Verification (Optional)**
* The user is prompted to complete a short liveness check using the device camera.
* On-screen instructions guide the user to ensure proper lighting, face visibility, and clarity.
* This step helps validate the signer’s presence and identity.
> **Note:**\
> If OTP or liveness verification is **not enabled**, the external user is taken **directly to the document** after clicking the email link.
***
#### 4. Document Viewer Experience
Once authentication (if any) is completed, the external user is taken directly to the assigned document.
Within the document viewer, the user can:
* Read the complete document content
* Navigate between pages using page controls
* View document details such as document name and reference number
No additional navigation is required to locate the document.
***
#### 5. Available Actions While Reviewing
While reading the document, external users can access the following actions (based on permissions):
* **Next**\
Guides the user to the next required action such as initials or signature fields.
* **View/Add Attachments**\
View supporting documents or upload attachments (if enabled).
* **Signing Order Indicator**\
See participant details and the current signing sequence.
* **Save**\
Save progress and continue signing later.
* **Decline**\
Decline the document with a mandatory reason.
* **Download document(s)**
* **Add comments**
* **View document details**
***
#### 6. Guided Navigation to Signing Fields
The **Next** button ensures a guided signing experience by automatically navigating the user to:
* Initial placeholders
* Signature placeholders
* Mandatory fields
This prevents missed actions and helps external users complete signing efficiently.
***
#### 7. Sign & Finish
Once all required actions are completed:
* The **Sign & Finish** button becomes available.
* Clicking **Sign & Finish** completes the external user’s signing process.
* The workflow automatically moves to the next participant, if any.
---
# 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://support.emsigner.com/initiate-and-sign-envelopes/signing-a-document/as-an-external-recipient-ad-hoc-user/reading-through-documents.md?ask=&goal=
```
`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.