---
title: "Reasons"
slug: "reasons"
updated: 2026-01-29T11:30:20Z
published: 2026-01-29T11:30:20Z
canonical: "documentation.encodify.com/reasons"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.encodify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reasons

## What are Reasons

---

For each [status transition](/v1/docs/change-status), it is possible to configure predefined **Reasons**, which serve as supplementary metadata. These reasons help support business processes by providing clarity and justification for actions such as rejection, ensuring transparency and consistency in decision-making.

## How to configure Reasons

---

Follow these steps to configure **Reasons**:

1. Navigate to **Site Configuration → Site Configuration → Modules**.
2. Click **Create Module**
3. Set the **Type** to **Module**.
4. Specify a **Name** for the module (e.g., *Reasons*).
5. Select a **Template** (e.g. Without Media Settings and Audit Fields)
6. Click **OK**to confirm the creation of the module

![](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/create-reasons-module.png)

An image highlighting the creation of reasons module

1. Navigate to **Site Configuration → {Module} → Field Definition**
2. Click **New Field**
3. Create a Text Field with a given **Field Name**(e.g. Reasons)
4. Click **OK** to create the field

![](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/create-reasons-field-definition.png)

An image highlighting the creation of Reason field

Once you have created the field, navigate to the source module and define a list of specific reasons relevant to the transition. Once completed, you can assign a reason to a specific transition by following the steps below:

1. Navigate to **Site Configuration → {Module} → Workflow**.
2. Create a new workflow transition or edit an existing one.
3. Locate the **Enable Reasons** option and specify whether selecting a reason should be optional or mandatory during the status transition.
4. In the **Reasons Module** field, select the module that contains the list of available reasons.
5. In the **Available Reasons** field, choose the specific reasons applicable to this status transition.
6. Select the **User Module Field**.
7. Click **OK** to finalise the configuration.

![](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/configure-reasons-against-transition.png)

An image highlighting an example of reasons configuration against a specific transition