> 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-internal-user/other-actions-you-can-perform.md).
# Other actions you can perform
While reviewing a document, internal users have access to several supporting actions from the document viewer. These options help users collaborate, review details, or manage the signing workflow without interrupting the signing process.
***
#### View / Add Attachments
If the initiator has added supporting documents, or if attachments are enabled for the workflow, the signer can access them using **View/Add Attachments**.
From here, the signer can:
* View all supporting or reference documents attached to the envelope
* Download attached files for offline review
* Add additional supporting documents (if permitted)
This is useful when the main document refers to external files such as annexures, reference agreements, or supporting evidence.
***
#### Doc Log (Document Activity Log)
The **Doc Log** provides a detailed audit trail of the document lifecycle.
It displays:
* Document number and envelope reference
* Workflow initiator details
* Total number of internal and ad hoc users
* Workflow status (for example: Pending, Completed)
* A chronological log of activities such as:
* Document upload
* Save as draft
* Sent for signing
* User actions with timestamp, IP address, and browser details
This helps signers understand the background of the document and track actions already performed.
***
#### Save (Progress Preservation)
At any point during document review or field filling, the signer can use **Save**.
* All entered information (fields, initials, signatures, selections) is securely saved
* The document remains in a pending state
* The signer can return later and continue from where they left off
This is useful when the signer needs more time or additional clarification before completing the signing process.
***
#### Decline to Sign
If the signer decides not to proceed, they can choose **Decline**.
When declining:
* The signer must provide remarks (mandatory)
* The decline action is recorded in the workflow
* The initiator and relevant participants are notified
This ensures transparency and provides clear reasoning for not signing the document.
***
#### Delegate to Someone Else
If delegation is enabled, the signer can delegate the signing responsibility to another user.
The signer needs to provide:
* Delegate’s email address
* Delegate’s name
* Reason for delegation
Once delegated:
* The signing responsibility moves to the new participant
* The workflow reflects the delegation in the signing order
This is helpful when the original signer is unavailable or not the appropriate authority.
***
#### Share Document
Using the **Share** option, the signer can share the document for review purposes.
Key points:
* Multiple email addresses can be added (semicolon-separated)
* An optional message can be included
* Attachments can also be shared, if enabled
This action is typically used for internal consultation or legal review before signing.
***
#### View Document (Read-Only Mode)
The **View Document** option opens the document in a read-only viewer.
In this mode, the user can:
* Scroll through the entire document
* Zoom in/out for better readability
* Navigate pages using thumbnails
No fields or placeholders can be edited in this view, making it ideal for focused reading or validation.
***
#### Summary
These actions allow internal users to:
* Review supporting materials
* Track document history and participant actions
* Collaborate with others
* Pause, delegate, or decline when needed
All of this can be done **without disrupting the signing flow**, ensuring flexibility and control throughout the document signing journey.
---
# 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-internal-user/other-actions-you-can-perform.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.