> 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/using-templates/creating-and-managing-templates/configure-a-flexi-form-template/setting-workflow-permissions.md).

# Setting workflow permissions

### Setting Workflow Permissions

Workflow permissions allow the template creator to control what each signatory can access and perform during the signing journey. These permissions are configured at the signatory level and help enforce document confidentiality and controlled collaboration.

***

#### Where to Configure

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

Workflow permissions are configured directly within the **Add Participants** step:

1. Click on the relevant signatory from the left panel to open their **Configure settings** panel.
2. Expand the **Signatory Settings** section.
3. Configure the required permissions under **Configure Attachment Profile**.
4. Click **Save Details** to apply.

***

#### Available Permission Controls

**1. Configure Attachment Profile**

Select a **Profile Name** from the dropdown to define the type of attachments the signatory is required to submit as part of the signing process.

**2. Restrict Document Download**

* **Don't Allow to download documents** — When enabled, the selected signatory cannot download the document during or after the signing process. Useful for restricting document access for specific participants.

**3. Dynamic Participant Access**

* **Allow to add exceptional users and define access controls** — When enabled, the selected signatory can add new participants during an active signing workflow. Refer to the **Adding Dynamic Users** section for full details.

**4. Control Attachment and Comment Visibility**

The **Configure Attachment Profile** table lists all other signatories in the workflow. For each co-signatory listed, the following visibility controls are available:

| Setting              | Description                                                                                   |
| -------------------- | --------------------------------------------------------------------------------------------- |
| **Hide Attachments** | Prevents the selected signatory from viewing attachments uploaded by the listed co-signatory. |
| **Hide Comments**    | Prevents the selected signatory from viewing comments added by the listed co-signatory.       |

> **Note:** The visibility table reflects all signatories added to the workflow. If only one signatory has been configured, the table will display *No signatories available* until additional participants are added.

***

#### Key Notes

* Permissions are configured independently for each signatory. Repeat the process for every participant whose access needs to be controlled.
* All permission settings are locked into the template and apply each time the template is used to initiate a signing transaction.


---

# 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/using-templates/creating-and-managing-templates/configure-a-flexi-form-template/setting-workflow-permissions.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.