> 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/server/es/concepts/basic-concepts/information.md).

# Información

Las entradas de información en Devolutions Server almacenan datos de referencia como procedimientos, contactos o detalles de activos junto con credenciales y documentos.

Las entradas de información en Devolutions Server son registros flexibles para almacenar datos de referencia que no son una sesión remota ni una credencial independiente, como procedimientos, contactos o detalles de activos. Coexisten con otras entradas en bóvedas orientadas al negocio, comparten el mismo modelo de permisos y pueden combinarse con documentos, adjuntos y campos personalizados para crear artículos de conocimiento ligeros. Utilizar entradas de información en lugar de wikis separadas mantiene el contexto operativo cerca de las contraseñas y las conexiones que sus equipos utilizan realmente.

Un caso de uso típico es una entrada de información que documenta un servidor, con enlaces a sus entradas RDP y SSH además de notas sobre las ventanas de mantenimiento.

#### Temas relacionados

* [Entradas](/server/es/web-interface/vaults/entries.md)
* [Tipos de contenido de bóveda](/server/es/web-interface/customization/vault-content-types.md)


---

# 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/server/es/concepts/basic-concepts/information.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.