Author a reusable report template with ordered sections, conditional render rules, per-section finding filters, column selection, and a watermark.
This guide shows you how to turn a protected PMAP system template into an editable, user-owned template you can shape to your reporting needs. You will clone a base template, author an ordered sections list, and inject free-text custom blocks anchored after named sections. The template then feeds the report pipeline, so the structure you define here drives every report generated from it.
It is written for report authors and compliance owners who need consistent, repeatable output across audiences. By the end you will be able to attach per-section finding filters, set render conditions that drop empty or low-risk sections, configure per-section columns, add a watermark, and confirm the whole template in the live preview before you share or lock it.
Inside this guide
- Find a base template, read its config, and clone a protected system template into an editable copy.
- Set template identity, scope, and output formats.
- Author the ordered sections list and inject custom free-text blocks after named sections.
- Attach per-section finding filters for severities, statuses, limit, and sort order.
- Set render conditions of always, has_findings, or has_severity so weak sections drop out.
- Configure per-section columns and add a watermark with severity mapping.
- Preview, share, and lock the finished template.
Before you start
- A PMAP account with report template create and edit permissions in the scope you will author for.
- Familiarity with the section keys your target report_type renders, for example executive_summary and findings.
- An understanding of your organization’s severity and status vocabulary, since section filters reference those values.
- A system template close to what you want, so you can clone rather than build from an empty config.
- If you intend to share the finished template, the user ids of colleagues who will receive view or edit grants.
