> 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/connect-v3.1-en/firma/administracionconnectfirma/grupoficheros/alta/grupos_firmantes.md). # Signer groups ## Signer groups On this screen, both the signer groupings and the totals for the *file group*. ![Signer group](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-6e3d1e34ce9a03b72bd51a205d877645b91b20be%2F03_grupo_de_firmantes.png?alt=media) * **Enable order in signer group**: parameter indicating that the signer groups to be registered below must act in a specific order. The first group defined will be the first to sign and so on until the last. When this parameter is enabled, the maximum number of signer groups that can be configured is five. In addition, in this case all signer groups will be mandatory, that is, the file must receive the sum of the values of the parameter **Number of mandatory signatures** of all of them. * **Signer group name**: unique identifier of the signer group in the *file group*. * **Number of mandatory signatures**: number of signatures required to consider the signer group fulfilled. It is a mandatory parameter and its minimum value is 1. It is recommended to include in the signer group a number of participants greater than the number of mandatory signatures indicated here. In this way, the number of signatures needed for the group is guaranteed in situations where some of the signers are absent due to illness, vacations, etc. The inclusion of signers in the group is done in **Users - Groups** and is described in the following section. * **Mandatory group**: indicates whether the group must be fulfilled necessarily, that is, that as many members of the group must act as mandatory signatures of the group have been configured in order to consider the file sufficiently signed. This parameter is shown selected and becomes non-editable when **Enable order in signer group**. When a signer group is not marked as mandatory, it is considered optional. In this case, the need for action by the signers that make it up depends on whether or not it is required for the file to reach the figures indicated in the two totals of the *file group* to be described below. If an optional signer group acts, it must do so until the end so that its number of mandatory signatures is reached. ## File group totals * **Total mandatory signatures**: number of signatures required to consider the file sufficiently signed. The signatures may come from signers who participate as part of or not part of a signer group. The minimum value of this parameter is 1. If there are mandatory signer groups, the figure entered here will include at least the sum of the numbers of signatures required in each of them. * **Groups that must be fulfilled**: number of signer groups that must act to consider the file sufficiently signed. The indicated value must include the number of signer groups that have been configured as mandatory, if any, and as many optional ones as required. The minimum value of this parameter is 0. The combined use of the two totals makes it possible to carry out signing strategies in which the required number of signatures can be reached with different combinations of signers. ### ๐Ÿงพ Use cases #### **Case 1** An entity has the following signer groups by category: > * **Level 1 authorized representatives group**: 2 signers > * **Level 2 authorized representatives group**: 3 signers > * **Level 3 authorized representatives group:** 3 signers 1.1 In the entity, the files of a certain amount range must be signed by **two people from the level 2 and 3 authorized representatives groups**, interchangeably. **Configuration in Connect:** * **Single signer group**: * **Components**: the three members of *Level 2 authorized representatives group* and the three members of *Level 3 authorized representatives group* * **Number of mandatory signatures**: 2 * **Mandatory group**: yes * **File group totals**: * **Total mandatory signatures:** 2 * **Groups that must be fulfilled:** 1 *** 1.2 In the entity, the files of another certain amount range must be signed by **two people from the level 2 authorized representatives group** or by **one from the level 2 authorized representatives group and another from the level 3 authorized representatives group**. **Configuration in Connect** * **Level 3 authorized representatives group** * **Components**: the three members of *Level 3 authorized representatives group* * **Number of mandatory signatures**: 1 * **Mandatory group**: no * **Additionally:** * The three members of *Level 2 authorized representatives group* are added to the *file group* **without belonging to a group**. * **File group totals**: * **Total mandatory signatures**: 2 * **Groups that must be fulfilled**: 0 *** 1.3 In the entity, the files of a third amount range must be signed by **two people from the level 1 authorized representatives group**\*. **Configuration in Connect** * **Level 1 authorized representatives group** * **Components**: the two members of *Level 1 authorized representatives group* * **No. of mandatory signatures**: 2 * **Mandatory group**: Yes * **File group totals**: * **Total mandatory signatures**: 2 * **Groups that must be fulfilled**: 1 *** ๐Ÿ“Œ **Things to keep in mind** > The signer groups in Connect do not always match the signer groups of the entity (company or organization). > The *file groups*, or signing rules, are independent of each other, so the inclusion of signers in each one must be planned in a way that makes it possible to achieve the desired signing objective. As seen in the examples, the same signer who participates as a group member in one of the signing rules may need to do so in a different group, or even individually, in other signing rules that apply to the same set of files. #### **Case 2** > In a public administration, there are the following three signer groups: > > * ***Treasury group***: two members > * ***Controllers group***: two members > * ***Mayor's Office group***: two members 2.1 The organization requires that all files be signed by **one member of each group**. **Configuration in Connect:** * **Treasurers group** * **Components**: the two members of *Treasury group* * **Number of mandatory signatures**: 1 * **Mandatory group**: yes * **Controllers group** * **Components**: the two members of *Controllers group* * **Number of mandatory signatures:** 1 * **Mandatory group**: yes * **Mayor's Office group**: * **Components**: the two members of *Mayor's Office group* * **Number of mandatory signatures**: 1 * **Mandatory group**: yes * **File group totals:** * **Total mandatory signatures**: 3 * **Groups that must be fulfilled**: 3 If necessary, it could be configured **Enable signer group order** so that the signing of the file is carried out in a specific sequence. Once the signer groups and the number of signatures and signer groups required have been configured, proceed to the next screen to associate users with the *file group*. --- # 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://docs.editran.onesait.com/documentacion-editran/connect-v3.1-en/firma/administracionconnectfirma/grupoficheros/alta/grupos_firmantes.md?ask=&goal= ``` `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.