> 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-v2.1-en/firma/administracionconnectfirma/grupoficheros/alta/grupos_firmantes.md). # Signer groups ## Signer groups This screen defines both the signer groups and the file-level totalizers of the *file group*. ![Signer group](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-6e3d1e34ce9a03b72bd51a205d877645b91b20be%2F03_grupo_de_firmantes.png?alt=media) * **Activate signer group order**: parameter to indicate 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 activated, 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 required signatures** from all of them. * **Signer group name**: unique identifier of the signer group in the *file group*. * **Number of required signatures**: number of signatures required to consider the signer group fulfilled. This is a mandatory parameter and its minimum value is 1. It is advisable to include in the signer group a number of participants greater than the number of required signatures indicated here. In this way, the number of required signatures for the group is guaranteed in situations where some signers are absent due to illness, vacation, etc. Signers are added to the group in **Users - Groups** and this is described in the following section. * **Mandatory group**: indicates whether the group must necessarily be fulfilled, that is, that as many members of the group must act as the number of required signatures configured for it in order to consider the file sufficiently signed. This parameter is shown selected and becomes non-editable when **Activate signer group order**. When a signer group is not marked as mandatory, it is considered optional. In this case, the need for the actions of the signers who make it up depends on whether it is required or not for the file to reach the figures indicated in the two totalizers of the *file group* which will be described below. If an optional signer group acts, it must do so until the end so that its number of required signatures is reached. ## File group totalizers * **Total required signatures**: number of signatures required to consider the file sufficiently signed. Signatures can come from signers who participate either 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 required signatures 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 totalizers allows 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 categories: > * **Power of attorney group level 1**: 2 signers > * **Power of attorney group level 2**: 3 signers > * **Power of attorney group level 3:** 3 signers 1.1 In the entity, files within a certain amount range must be signed by **two people from the power of attorney groups of levels 2 and 3**, interchangeably. **Configuration in Connect:** * **Single signer group**: * **Members**: the three members of *Power of attorney group level 2* and the three members of *Power of attorney group level 3* * **Number of required signatures**: 2 * **Mandatory group**: yes * **File group totalizers**: * **Total required signatures:** 2 * **Groups that must be fulfilled:** 1 *** 1.2 In the entity, files within another certain amount range must be signed by **two people from the power of attorney group of level 2** or by **one from the power of attorney group of level 2 and another from the power of attorney group of level 3**. **Configuration in Connect** * **Power of attorney group level 3** * **Members**: the three members of *Power of attorney group level 3* * **Number of required signatures**: 1 * **Mandatory group**: no * **Additionally:** * The three members of *Power of attorney group level 2* are added to the *file group* **without belonging to a group**. * **File group totalizers**: * **Total required signatures**: 2 * **Groups that must be fulfilled**: 0 *** 1.3 In the entity, files in a third amount range must be signed by **two people from the power of attorney group of level 1**\*. **Configuration in Connect** * **Power of attorney group level 1** * **Members**: the two members of *Power of attorney group level 1* * **No. of required signatures**: 2 * **Mandatory group**: Yes * **File group totalizers**: * **Total required signatures**: 2 * **Groups that must be fulfilled**: 1 *** ๐Ÿ“Œ **To keep in mind** > Connect signer groups do not always match the entity's (company or organization) signer groups. > The *file groups*, or signing rules, are independent from each other, so the inclusion of signers in each one must be planned in a way that allows achieving the desired signing goal. As seen in the examples, the same signer who participates in a group 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 > * ***Auditors 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** * **Members**: the two members of *Treasury group* * **Number of required signatures**: 1 * **Mandatory group**: yes * **Auditors group** * **Members**: the two members of *Auditors group* * **Number of required signatures:** 1 * **Mandatory group**: yes * **Mayor's office group**: * **Members**: the two members of *Mayor's office group* * **Number of required signatures**: 1 * **Mandatory group**: yes * **File group totalizers:** * **Total required signatures**: 3 * **Groups that must be fulfilled**: 3 If necessary, it could be configured **Activate signer group order** so that the file signing is carried out in a determined sequence. Once the signer groups and the number of required signatures and signer groups have been configured, you should proceed to the next screen to associate users to 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-v2.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.