Scan Template Group Form
The Scan Template Group form creates a new group or edits an existing one. Template groups let a single Schedule reference multiple scan templates at once — the dispatcher fans the group into individual scan jobs at run time.
Inputs
| Name | Description | Allowed values | Default |
|---|---|---|---|
Name | Human-readable label for this group | Non-empty string, must be unique across scan template groups (e.g., "production-monitoring") | — |
Description | Optional free-text note | Any text, max 10,000 characters | Empty |
Scan Templates | Selection of templates to include. The picker shows each template name, description, and how many configured tests it has. | At least one selection (empty groups are rejected) | None |
Gotchas
- **When creating:** Group templates by operational rhythm ("hourly-checks") or scope ("perimeter-only"), not by who owns them — the schedule that uses the group already encodes ownership.
- **When editing:** Adding a template to a group means the next scheduled run includes it; removing one means future runs drop it. Past scan results remain.
- Template groups referenced by a Schedule cannot be deleted from the parent list page until the schedule drops the reference.
- Built-in templates can be added to groups, but they cannot themselves be modified. Groups composed entirely of built-in templates are useful for "out-of-the-box" recurring runs.
API calls (4)
| Method | Path | Description |
|---|---|---|
| GET | /api/config/scan-template-groups/:id | Load an existing template group (Edit mode) |
| GET | /api/config/scan-templates | List available scan templates |
| POST | /api/config/scan-template-groups | Create a new template group (Create mode) |
| PUT | /api/config/scan-template-groups/:id | Update an existing template group (Edit mode) |
Related
- Scan Template Groups — Parent list page
- Scan Templates — Members of template groups
- Schedules — A schedule can reference a template group to fan out to all member templates