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

# Custom workflow settings

> How to register a custom workflow in Atoti Sign-Off by updating backend configuration properties with the workflow name, process ID, and participant roles.

When adding a custom workflow, the user needs to update the project settings to pick up the workflow.

## Backend settings

The workflow needs to be included in the [SignOff workflow properties](../../../user-ref/properties/property-files/application-yml#Section-sign-off).
To add the new workflow, add a new entry to `sign-off.workflow.configuration` with the following format:

```yaml theme={"languages":{"custom":["/engine/python-sdk/0.9/languages/pycon.tmLanguage.json"]}}
    <WORKFLOW_NAME>:
      key: <WORKFLOW_PROCESS_ID>
      participants: <WORKFLOW_PARTICIPANTS>
```

* `<WORKFLOW_NAME>` is a name given to the workflow by the user.
* `<WORKFLOW_PROCESS_ID>` is the value of the `<process id=` tag defined at the beginning of the bpmn file.
* `<WORKFLOW_PARTICIPANTS>` is a comma-separated list of actors in the workflow, these define fields in the UI filled with one of the roles defined under `sign-off.workflow.roles`. This may not be required.

Below is an example from the Atoti Sign-Off `application.yml` with a custom workflow:

```yaml theme={"languages":{"custom":["/engine/python-sdk/0.9/languages/pycon.tmLanguage.json"]}}
sign-off:
  workflow:
    configuration:
      4-eyes:
        key: sign-off-process-instance.four-eyes
        participants: Examiners,Approvers
      simple:
        key: sign-off-process-instance.simple
        participants: Approvers
      4-eyes-kpi:
        key: sign-off-process-instance.four-eyes-kpi
        participants: Examiners,Approvers
    roles: USERS,MANAGERS
```

## Frontend settings

No frontend settings are required.