> 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-3.2-en/firma/administracionconnectfirma/notificaciones_correo_a_firmantes.md). # Email notifications to signers Connect notifies users with the signer role about the availability of new files to sign. This notification is sent once every hour from Monday to Friday between 8:00 a.m. and 8:00 p.m. Although the notification does not specify which particular files are awaiting signature, the system does keep track of which files it has already notified about so as not to send another notification for them. In this way, by notifying only the existence of new files, the aim has been to make the product intrude as little as possible into mailboxes. When the members of a signer group can sign a file, all of them receive the notification, even though only one of them needs to act (depending on the number of required signatures in the group). Not receiving a notification that a file is available does not mean that it is not available. For example, if a file is placed in the input directory on a Friday at 8:30 p.m., the signers who can act on it will not receive a notification about it until Monday at 8:00 a.m., but if they access Connect and the menu **Files**, they will find it available and will be able to sign it. Connect also notifies users with the signer role about the upcoming expiration of the certificates associated with them in their configuration. This notification is sent when there are three months, one month, or fifteen days left until the expiration date. It is also sent on the first day the certificate has expired. These notifications about the upcoming expiration of signers' certificates are also received by users with the signature administrator role. --- # 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-3.2-en/firma/administracionconnectfirma/notificaciones_correo_a_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.