> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/reporting/template-options.md).

# Template - Options

## Overview

Template options change how ReportGen builds a report from your template. You turn an option on by adding its tag to your template, usually at the very start.

Help, examples and tips for building templates are on the [ReportGen GitHub support site](https://github.com/AttackForge/ReportGen).

## Available options

| Option                      | What it does                                                                                  | Tag                                    |
| --------------------------- | --------------------------------------------------------------------------------------------- | -------------------------------------- |
| **RemoveDuplicateEvidence** | Removes evidence that's already shown inline in an affected asset's Proof of Concept or Notes | `{#$optionRemoveDuplicateEvidence}{/}` |

## Why it matters

* **Shorter reports.** Removing repeated evidence makes reports smaller.
* **Easier to read.** Readers don't see the same screenshot twice.

## Who uses it

| Who                         | To                                                                              |
| --------------------------- | ------------------------------------------------------------------------------- |
| **Report template authors** | Turn options on in their templates                                              |
| **Testers**                 | Add evidence inline in Proof of Concept and Notes, knowing it won't be repeated |
| **Report readers**          | Get shorter, clearer reports                                                    |

### RemoveDuplicateEvidence

Put this option at the start of your template to remove duplicate evidence. For each vulnerability, any evidence that's already shown in an affected asset's Proof of Concept or Notes, such as an image shown inline, is left out of the evidence section. This reduces repeated evidence, makes the report smaller, and makes it more useful to readers.

Without the option, images shown inline in Notes or Proof of Concept appear again in the evidence section. With RemoveDuplicateEvidence turned on, each image appears once.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fd1bcTwZGFiP2oJuwWu5t%2Ftemplate-options-at-a-glance.svg?alt=media&amp;token=58bf3c11-0c6e-4053-a172-7726db6ac01c" alt=""><figcaption></figcaption></figure>

```
{#$optionRemoveDuplicateEvidence}{/}
```

#### How it works

1. ReportGen loops over `{#affected_assets}`.
2. If an asset's Proof of Concept or Notes contains an inline image, that image is removed from the `{#evidence}` section.
3. The same file isn't displayed twice.

{% hint style="info" %}
**Important:** the `{#$optionRemoveDuplicateEvidence}{/}` tag must be at the beginning of your template file.
{% endhint %}

#### Example

```
{#$optionRemoveDuplicateEvidence}{/}
{#vulnerabilities}
VULNERABILITY: {title}
{#affected_assets}
ASSET: {asset}
NOTES:
{#notes_html}
{@note_styled(“image_description”:“caption”) | resize:[“400”]}
{/notes_html}
PROOF OF CONCEPT:
{@proof_of_concept_styled(“image_description”:“caption”) | resize:[“400”]}
{/affected_assets}
{#evidence}
{%fileBase64 | resize:[“400”]}
{fileName}
{/evidence}
{/vulnerabilities}
```

In this example, an image shown inline in an asset's Notes or Proof of Concept isn't repeated in the vulnerability's evidence.

## Tips

* **Put option tags on the first line of your template**, before any other content.
* **Add evidence inline where it helps the reader**, such as in Proof of Concept, and let RemoveDuplicateEvidence keep it out of the evidence section.
* **Test with real data.** Generate a report from a project with inline images to check the option is working.
* **Use the `$help` function** to see the data available at any point in your template. See [ReportGen issue #18](https://github.com/AttackForge/ReportGen/issues/18).

## FAQ

**Where do I put an option tag?** At the beginning of your template file.

**What does RemoveDuplicateEvidence remove?** Evidence files that are already shown inline in an affected asset's Proof of Concept or Notes. They're left out of the `{#evidence}` section.

**Does it delete evidence from AttackForge?** No. It only changes what appears in the generated report.

**Why isn't it working?** Check that `{#$optionRemoveDuplicateEvidence}{/}` is at the very start of your template, and that the images really are inline in Proof of Concept or Notes.

## Related pages

* [Reporting overview](https://support.attackforge.com/app/modules/reporting/overview)
* [Reporting (getting started)](https://support.attackforge.com/app/getting-started/reporting)
* [ReportGen on GitHub](https://github.com/AttackForge/ReportGen)


---

# 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://support.attackforge.com/app/modules/reporting/template-options.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.
