> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/fr/knowledge-base/troubleshooting-articles/entry-locked-on-edit.md).

# Entrée verrouillée lors de la modification

Résolvez un statut Verrouillée pour modification sur une entrée Devolutions Cloud en retirant le verrou depuis le panneau de survol de l'entrée dans le coffre.

Les utilisateurs peuvent occasionnellement rencontrer un problème dans Devolutions Cloud où une entrée affiche le statut **Verrouillée (Modification)**. Ce verrou empêche toute modification supplémentaire jusqu'à ce qu'il soit révoqué.

{% hint style="info" %}
Seul l'utilisateur qui a verrouillé l'entrée ou un administrateur peut la déverrouiller.
{% endhint %}

### Solution

1. Connectez-vous à votre compte Devolutions Cloud.
2. Naviguez jusqu'au coffre et repérez l'entrée verrouillée.
3. Dans le survol de l'entrée, trouvez l'invite verte indiquant ***Verrouillée pour modification par moi***.
4. Cliquez sur le ***x*** à côté de l'invite de verrouillage pour retirer le statut verrouillé.


---

# 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.devolutions.net/cloud/fr/knowledge-base/troubleshooting-articles/entry-locked-on-edit.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.