> 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/firmadeficheros/detallefichero/firmar/firma_cert_nube.md).

# Signing with a private-key certificate stored in the cloud

When it has been indicated in the configuration that one of the certificate locations to be used is the cloud of one of the providers included in Connect:

* If the request is made from a Windows device and it has been indicated in the configuration that one of the certificate locations is the operating system’s own store, signing is only performed in the cloud if there has been a previous attempt that failed with the desktop application.
* If the request is made from a Windows device and the only location indicated in the configuration is the cloud, or if the request is made from any device with an operating system other than Windows, signing is performed in the cloud.

## Signing process

Once the signer accesses the file details and, if applicable according to format and permissions, has viewed it, they will click the button **Sign** to begin the process.

![Sign button](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-e564010f8a1f21d7e201f1aaef8f8ad12a37614b%2F06_boton_firmar.png?alt=media)

When **Sign**is pressed, a new window specific to the cloud provider that holds the certificate will be displayed, where the certificate password must be entered.

![Signing with cloud certificate](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-3a9f79442b3d258ab441b74daa1f382e1bae8e95%2F14_pantalla_firma_certificado_nube.png?alt=media)

Pressing **Sign**again, a new window will report whether the operation was successful or not, and after a few seconds control will return to the screen with the user's file list filtered by status `Pending to be signed by me`, so the file that has just been signed will no longer be shown. However, if the user unchecks that filter, they can view the newly signed file and its overall and individual statuses with respect to each signer, if they wish.

From the file list, the signer can repeat the described process with the rest of the files that are still pending their action in Connect.

📌 **Remember**

> The maximum number of signatures with certificates stored in the cloud that can be made for each local channel-code is limited by license (feature `signatures_[provider_name]` with respect to local code). The number of signatures made this way can be consulted from: **Local configuration -> Electronic signature -> Cloud signing** and selecting the corresponding cloud signing provider in the dropdown.

![number of signatures made in the cloud](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-52f14c8d5bf3fe749f3443ed222a74c97c2c2d3c%2F15_num_firmas_nube.png?alt=media)

> When 75% or more of the contracted cloud signing package for a given local code has been used, the signing administrators receive a daily notification email reminding them of the need to renew the license to avoid service interruption once the limit is reached. This notice is also reflected in the Activity Log and in the aforementioned counter through the color of the data in the Number of signatures made column: orange when the figure is between 75% and 100% and red once the limit has been reached.


---

# 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/firmadeficheros/detallefichero/firmar/firma_cert_nube.md?ask=<question>&goal=<endgoal>
```

`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.