> 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/knowledge-base/knowledge-base-articles/entry-settings/common-settings/logs.md).

# Logs

Prompt users for a comment or a ticket number when they open, close or view the credentials of an entry in Remote Desktop Manager.

The ***Logs*** section defines what users must enter in the activity logs when they open or close an entry, or view its credentials: a comment, a ticket number, or both. The logged activities are shown in the [Logs](https://docs.devolutions.net/rdm/user-interface/content-area/dashboard/dashboard-tabs/logs.md) dashboard tab.

Available for session, credential, information and document entries, for folders and for the vault, with workspaces that support logs: Devolutions Server, Devolutions Cloud, Microsoft SQL Server and SQLite. In the entry properties, go to ***View*** – ***Logs***. For the vault, go to ***Administration*** – ***Vault settings*** – ***View*** – ***Logs***.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Warn if already open</strong></em></td><td>Warns the user, before opening the session, when the logs show that the session is already open. Not applied in offline mode. Shown for session entries, folders and the vault. Disabled, with the message <em><strong>Not supported by this type or when used in external mode</strong></em>, when the entry type or its external display mode does not log the closing of the session.</td></tr><tr><td><em><strong>Open logs</strong></em></td><td>Prompt shown when the entry is opened: <em><strong>Inherited</strong></em> or <em><strong>Custom</strong></em>. Not shown for credential entries.</td></tr><tr><td><em><strong>Close logs</strong></em></td><td>Prompt shown when the session is closed: <em><strong>Inherited</strong></em> or <em><strong>Custom</strong></em>. Shown for session entries, folders and the vault.</td></tr><tr><td><em><strong>View credential logs</strong></em></td><td>Prompt shown when the credentials of the entry are viewed: <em><strong>Inherited</strong></em> or <em><strong>Custom</strong></em>.</td></tr></tbody></table>

With ***Inherited***, the entry uses the setting of the closest parent folder, or of the vault, that is set to ***Custom***. On Windows, the value that applies is shown next to the setting.

With ***Custom***, these options appear under the setting:

<table><thead><tr><th width="220">OPTION</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Prompt for comment on open</strong></em>, <em><strong>Prompt for comment on close</strong></em>, <em><strong>Prompt for comment on credentials viewed</strong></em></td><td>Asks the user for a comment, which is saved in the logs.</td></tr><tr><td><em><strong>Open comment is required</strong></em>, <em><strong>Close comment is required</strong></em>, <em><strong>Credentials viewed comment is required</strong></em></td><td>Prevents the action until a comment is entered. Available when the matching <em><strong>Prompt for comment</strong></em> option is selected.</td></tr><tr><td><em><strong>Ticket number is required</strong></em></td><td>Requires a ticket number with the comment. Available when the matching <em><strong>Prompt for comment</strong></em> option is selected.</td></tr></tbody></table>

In the user vault, the section is shown only when the activities of the user vault are logged (***Log user vault activities***). By default, the section is shown only after selecting ***Show all properties*** in the entry properties. In a PAM vault that is not merged with a standard vault, the section is not shown for folders and the vault.

See [Logs, reports, and audits](https://docs.devolutions.net/rdm/concepts/advanced-concepts/logs-reports-and-audits.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/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/logs.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.
