> For the complete documentation index, see [llms.txt](https://docs.spydra.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spydra.app/how-to/public-chain/additional-configurations/create-a-document-workflow.md).

# Create a Document Workflow

As part of regulatory compliance, issuers can configure document workflows that require investors to sign specific documents during the token purchase process. This feature helps ensure compliance with legal requirements in the issuer's jurisdiction.

Once configured, the platform will automatically prompt investors to complete the document workflow based on your settings, either during or after the token purchase process.

#### Document Configuration Steps

1. **Document Details**

   1. **Document Name:** Enter a clear, investor-friendly document name
   2. **Document Description:** Provide a description explaining the purpose of the document to your investors
   3. **Upload Document:** Upload the document in PDF format

2.  **Define Signing Requirements**

   1. Specify when investors need to sign: before or after token purchase.
   2. Indicate if the document is required for all transactions (if the sign is required post purchase).
   3. Set up document renewal requirements if applicable, including renewal timeline

3. **Variable Properties**
   1. Add dynamic information of investors, investment details, and token details such as investor name, investment value, and token name etc.
   2. Include ***mandatory signature blocks*** for document validation

<div align="left"><figure><img src="/files/76zmIiAtD6AcLg67SyAu" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Issuers have an option to add a document for signing or remove an existing document workflow even after the asset is listed.
{% endhint %}


---

# 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://docs.spydra.app/how-to/public-chain/additional-configurations/create-a-document-workflow.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.