> 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/rdm/es/getting-started/workspaces/lock-a-workspace.md).

# Bloquear un espacio de trabajo

Bloquee una configuración de espacio de trabajo de Remote Desktop Manager con una contraseña para proteger las URL de servidor y las credenciales sensibles antes de la implementación.

Para proteger los datos sensibles de la configuración de su espacio de trabajo (p. ej., la URL del servidor o las credenciales), quizá desee bloquear la configuración del espacio de trabajo antes de implementarla para sus usuarios. Puede hacerlo mediante el botón ***Bloquear/Desbloquear*** de la barra de herramientas.

El espacio de trabajo bloqueado requerirá una contraseña. La contraseña debe especificarse cuando se aplica el bloqueo. Utilice la misma contraseña para desbloquearlo o para modificar la configuración del espacio de trabajo.

{% hint style="danger" %}
No hay forma de desbloquear el espacio de trabajo si la contraseña se pierde o se olvida. En tal caso, deberá configurar un nuevo espacio de trabajo. Sin embargo, el contenido de la base de datos no se perderá.
{% endhint %}


---

# 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/rdm/es/getting-started/workspaces/lock-a-workspace.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.