Report Templates
Upload and manage DOCX report templates that control the structure and formatting of your exported pentest reports.
Report templates are DOCX files that define the structure and visual formatting of your exported reports. When you export a report, Vulnsy merges your engagement data into the template to produce the final document.
Template Types
| Type | Description |
|---|---|
| Organization templates | Templates uploaded by your team. Only visible to your organization. |
| Global templates | Templates provided by Vulnsy, available to all organizations. Can be toggled on or off. |
Uploading a Template
- Go to Admin > Templates (
/admin/templates) - Click Upload Template
- Select a
.docxfile from your computer - Give the template a name
- Save
The template is now available for selection when exporting reports.
Setting a Default Template
You can designate one template as the default for new reports:
- Go to Admin > Templates
- Find the template you want to set as default
- Click Set as Default
New reports will automatically use this template unless a different one is selected.
Template Syntax
Templates use Docxtemplater syntax for dynamic content. Tags in your template are replaced with data from Vulnsy during export.
{report_title}
{client_name}
{#findings}
{title} - {severity}
{/findings}
{%image}For the full list of available template tags and syntax reference, see the Report Export documentation.
Global Template Visibility
By default, Vulnsy's global templates are visible to your organization. To hide them:
- Go to Admin > Templates
- Toggle off Show Global Templates
This is useful if your organization has its own templates and you want to avoid confusion.
Report Styles
Report styles control the visual formatting applied to your exports -- fonts, colors, heading styles, and table formatting. Styles are configured alongside templates and applied during the export process.
When editing templates in Word, type tags in one continuous motion. Do not copy/paste or edit tags after typing, as Word may split the tag across multiple XML runs and break the replacement. See Export Issues for more details.