> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/user/envelope-processing-flow-template-configuration/processing-flow-role-types.md).

# Processing Flow Role Types

This document explains the available role types in an envelope processing flow and their constraints.

{% hint style="info" %}

* **Processing flow** — The rule set that determines recipient order and document processing behavior.
* **Role** — A participant type in a template or envelope flow, such as sender, signer, approver, or copy.

See the [Glossary](https://support.docstudio.com/glossary/glossary.md) for DocStudio term definitions.
{% endhint %}

### Assignee role

* An **Assignee** fills in fields in the envelope and can sign a document when required.
* The **Assignee** role must have at least one field in a template document.
* The **Assignee** role must appear earlier in the flow than the **Signer** role.

### Signer role

* A **Signer** signs a document with an electronic signature.
* The **Signer** role must have at least one signature field in a template document.
* A **Signer** cannot have two signature fields in the same document.
* The **Signer** role must appear later in the flow than the **Assignee** role.

### Approver role

* An **Approver** can approve or reject moving the envelope to the next roles.
* The **Approver** role can be placed at any point in the processing flow, but not earlier than the **Sender**.

### CC role

* A **CC** role receives a copy of the envelope and cannot edit document fields.
* The **CC** role can be placed at any point in the processing flow, but not earlier than the **Sender**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.docstudio.com/user/envelope-processing-flow-template-configuration/processing-flow-role-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
