---
title: "How to set up the contract workflow?"
slug: "1723138892"
tags: ["Settings"]
updated: 2026-11-02T12:26:51Z
published: 2026-11-02T12:26:51Z
canonical: "help.ila.cegid.com/1723138892"
---

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

# How to set up the contract workflow?

- [x] PT
- [x] ES

---

In contracts, you can change the state flow so that it matches the organization's way of working.

---

## View the default workflow

By default, the contract workflow has the following states:

| State | Notes |
| --- | --- |
| New | Initial state |
| Approved |  |
| Canceled | Final state |
| Closed | Final state |

---

## Change the workflow

To create a state or change the settings of an existing state, follow these steps:

1. Go to **Settings | Contracts | Workflow**;
2. In the list of states, click on **Create** to create a state, or select the desired state to change its settings;
3. In the **General** tab, fill in the state details:
  - **State**;
  - **Description** (required);
  - **Localized Description**;
  - **Color**: select the state color. The initial value is **Gray**;
  - **Entity** (required): select **CONTRACTSTATES.CONTRACTSCORE**;
  - **Is Initial State**: by default, entities are created in the state defined as initial;
  - **Is Final State**: defines the end of the entity's state flow, so it cannot have transitions to other states;
  - **Is Locked For Changes**;
  - **Transitions** section: in each row, fill in the **Target Entity State** and **Need Justification** columns;
4. In the **Contract** tab, in the **Configuration** section, configure the **Canceled** option: if active, items in the configured state are considered “trash”;
5. Click on:
  - **Save and New**, to save the state and start a new record;
  - **Save**, in the arrow next to the **Save and New** button, to save only the state.

When creating and editing states, the following rules apply:

- There must be one **initial** state and one **final** state for each **entity**;
- To fill in the remaining description languages, edit the state with a **user** who has the **language configured** in their **profile**.