> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/review-tool-concepts/brands-and-attributes/setting-up-attributes/add-variables-to-steps.md).

# Add Variables to Steps

When using linked files (like your Attributes or regulatory databases), Protege Review automatically creates variables you can insert into policy steps for dynamic, context-aware reviews.

These variables can be used in multiple fields within a step, including:

* Explanation
* Prompt
* Keywords

#### To Add a Variable:

1. In the step editor, place your cursor in the field where you’d like to insert the variable (e.g., Explanation).

<figure><img src="https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-d44c30db7cc362dfdc585f5289b93e0c8fd789d3%2Fpolicy-step-variables.jpg?alt=media" alt=""><figcaption></figcaption></figure>

1. Press the $ key to open the list of available variables.
2. Select the appropriate variable from the dropdown list — this variable pulls matching data from the linked file.
3. Once inserted correctly, the variable name will turn green, indicating it’s properly connected.

<figure><img src="https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-d2bf37a4c1b567932c896addbbe5d2abb5002236%2Fprompt-attribute-variable.jpg?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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.tryprotege.com/review/review-tool-concepts/brands-and-attributes/setting-up-attributes/add-variables-to-steps.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.
