Export Tag Prefixes

How export tag prefixes scope template data to specific tabs in multi-tab Vulnsy reports, enabling structured DOCX exports across multiple testing areas.

When a report has multiple tabs — for example, "Web Application" and "Infrastructure" — each tab's data needs to be distinguishable in the exported document. Export tag prefixes solve this by scoping each tab's findings and narrative content under a unique identifier.

What Is an Export Tag Prefix?

Every report tab has an exportTagPrefix — a short label like web, infra, or mobile that identifies that tab's data during export. The prefix appears as a badge or chip next to the tab name in the export UI, making it easy to see which prefix maps to which tab.

Tab Name	Export Tag Prefix	What It Scopes
Web Application	`web`	All findings and narrative content from this tab
Infrastructure	`infra`	All findings and narrative content from this tab
Mobile App	`mobile`	All findings and narrative content from this tab

You set the export tag prefix when creating or editing a tab. It can be any short string that makes sense for your engagement.

How Prefixes Work in Templates

When you export a multi-tab report, the {#tabs} loop in your template iterates through each included tab. Each tab carries its own findings, narrative sections, and the prefix identifier.

{#tabs}
Testing Area: {name}
Prefix: {exportTagPrefix}

Findings for this tab:
{#findings}
{order}. {title} — {severity}
{description}
{/findings}
{/tabs}

In this example, the template loops through each tab and renders that tab's findings within its section. The {exportTagPrefix} tag outputs the prefix value itself, which you can use as a label or reference ID in the document.

Finding IDs and Tab Scoping

Each tab also has a findingIdPrefix that controls how finding reference IDs are generated. By default, the prefix is REF, producing IDs like REF-001, REF-002, etc.

When you customize the finding ID prefix per tab, findings are scoped accordingly:

Tab	Finding ID Prefix	Example Finding IDs
Web Application	`WEB`	`WEB-001`, `WEB-002`, `WEB-003`
Infrastructure	`INFRA`	`INFRA-001`, `INFRA-002`
Mobile App	`MOB`	`MOB-001`, `MOB-002`

This makes it clear in the final report which testing area each finding belongs to, even when all findings are listed together.

Export Options with Multiple Tabs

When exporting a multi-tab report, you choose which tabs to include:

Export Option	Behavior
All tabs	Every tab is included. The `{#tabs}` loop iterates through all of them, and all findings from all tabs appear in the document.
Single tab	Only the selected tab's findings and narrative content appear. Report-level fields (title, client, project) are still included.
Custom selection	You pick specific tabs to include. Only selected tabs appear in the `{#tabs}` loop and only their findings are exported.

When exporting a single tab, report-level fields like {report.title}, {client.name}, and {project.name} are always available — they are not scoped to a specific tab. Only findings and narrative sections are tab-specific.

Setting Up Prefixes

Open your report and navigate to the tab you want to configure
Click the tab settings or edit the tab
Set the Export Tag Prefix to a short, descriptive label (e.g., web, infra, api)
Optionally set a custom Finding ID Prefix (e.g., WEB, INFRA, API)
Save the tab

Repeat for each tab in your report. Each tab should have a unique prefix to avoid confusion in the exported document.

Use unique prefixes for each tab within the same report. Duplicate prefixes will make it difficult to distinguish between tabs in the exported document.

Example: Multi-Tab Report

Consider a report with two tabs:

Tab 1: Web Application

Export Tag Prefix: web
Finding ID Prefix: WEB
Findings: SQL Injection (WEB-001), XSS (WEB-002), CSRF (WEB-003)

Tab 2: Infrastructure

Export Tag Prefix: infra
Finding ID Prefix: INFRA
Findings: Open Ports (INFRA-001), Weak SSH Config (INFRA-002)

When exported with the template shown above, the document would contain two sections — one for Web Application with three findings, and one for Infrastructure with two findings — each clearly labeled with its prefix.

Next Steps

Template Tags — full reference of all available template tags
Search & Replace — replace variables across report content before export
Creating Templates — build Word templates that use tab loops and prefixes