> 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/user-dashboard-and-docstore/dashboard/originating-a-document.md).

# Originating a document

When you land on the **Dashboard**, the left-hand panel is the primary place from which you can **initiate documents or envelopes for signing**. This section provides multiple initiation options; each designed for a specific type of signing workflow.

<figure><img src="/files/lXnXIBLOQPPbBfA1szev" alt=""><figcaption></figcaption></figure>

***

#### Create an Envelope

The **Create an Envelope** option allows you to initiate a signing workflow **from scratch**, without relying on predefined templates.

Using this option, you can:

* Upload one or more documents
* Add internal and/or external recipients
* Define signing order and roles
* Place signature and form fields dynamically
* Configure authentication, notifications, and optional compliance steps

This option is best suited for **custom, ad-hoc, or one-time signing workflows**.

<figure><img src="/files/N1xfCAgSC8LjYeST9niX" alt=""><figcaption></figcaption></figure>

*For detailed steps, refer to the* **Creation of an Envelope** *section.*<br>


---

# 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/user-dashboard-and-docstore/dashboard/originating-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.