> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/administrador-de-onesait-ecosystems-editran-ff/alta-de-perfiles/alta-condiciones-mancomunadas.md).

# Create joint conditions

To create new joint-signature conditions in an Editran/FF application, you must select the application branch in the tree and then access the “*Operations -> New group/Conditions for* *joint signature*” menu will be accessed (also from the right-click context menu) or the button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/4oJbIEMffCRlxDSNnTpo/image1.png) from the toolbar.

**The application must necessarily have “Joint rules” set in the “*****Signature validation*** ***required” section.***

A dialog will be displayed with the following elements:

* **Application – Purpose**: information relating to the application to which the rule is going to be added; these fields are not editable.
* **Conditions**: list containing all the conditions established for the application.
* **New condition**: button to add a new joint rule.
* **Modify condition**: button to make changes to an existing condition.
* **Exit**: button to close the dialog.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/sYh6Gm6ZYM7zKXpJ1V34/image2.png)

When clicking the “*New condition*”, the lower area of the dialog is enabled, where the parameters needed to configure a new rule or condition are displayed. They are:

* **Local/remote users of the application**: list with all the users of the application. The users shown are of local type in applications to sign or of remote type in those whose purpose is verification.
* **Users of the condition:** list of the users that will take part in the condition to be created. To add users to this list, select as many as necessary in the “*Local/remote users of the*

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/kRWpUw63xB8yV9VorHaq/image3.png)

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/DywVhrHk8U1pTEXyzQqQ/image4.png)

*application*” list and use the button . To remove users from this list, select them and press .

* **No. of required signatures**: number of signers from the “*Users of the condition*” list who must sign each file for the condition to be considered fulfilled. Having more users participating in the condition than the number of required signatures guarantees the continuity of the signing flow when one of the signers is absent.
* **Maximum amount**: maximum amount that files signed with this rule may have. Enter ‘0’ when there is no limit.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/CHNn4mKDYeEyNqvZF5s6/image5.png)

Once all fields have been completed, click “*Save*” to create the new condition. The new condition will be added to the upper list, “*Conditions*” and the lower section will be disabled.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/ojSOkAazoewbWU4Aayit/image6.png)

Carry out this operation to create as many joint-signature conditions as necessary. **Entering redundant or unnecessary conditions could slow down the validation process, since they are checked one by one, and in the order in which they are created, until the first one that is met is found.**


---

# 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://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/administrador-de-onesait-ecosystems-editran-ff/alta-de-perfiles/alta-condiciones-mancomunadas.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.