> 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/concepts/intermediate-concepts/custom-fields.md).

# Custom fields

Devolutions Cloud custom fields add sensitive entry properties like asset tags or ticket IDs, referenced via variables in scripts and reports.

Custom fields are extra entry properties that you define to capture organization-specific data that standard fields do not cover. They can hold technical details, business identifiers, or notes, and are often configured as sensitive to protect confidential values.

In Devolutions Cloud, entries expose several custom fields that can be marked as sensitive and referenced through variables, for example when launching sessions from Remote Desktop Manager using a Devolutions Cloud workspace. This allows scenarios such as storing asset tags or internal ticket IDs and injecting them into scripts, templates, or reports without exposing the underlying values.

#### Related topics

* [List of supported variables in Devolutions Cloud](/cloud/knowledge-base/knowledge-base-articles/list-of-supported-variables-in-devolutions-cloud.md)

#### See also

* [Custom fields](https://docs.devolutions.net/rdm/concepts/intermediate-concepts/custom-fields)


---

# 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/concepts/intermediate-concepts/custom-fields.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.