Settings Global defaults used across all clients. Expand a section to edit it. See Help for first-time setup order.

Editing settings for Default user (default). ConnectSecure and Liongard credentials are stored per user; ConnectWise Manage PSA API credentials are shared by all users. Mappings, rules, templates, and review sessions are also shared.

Expand a section to edit it. Save Settings at the bottom applies to the whole page.

1. External integrations

Connect third-party APIs first - most workflows depend on ConnectSecure; Liongard and Manage are optional for mapping, email DNS, and PSA tickets.

ConnectSecure APICredentials to authenticate with ConnectSecure - required to download vulnerability reports, run patching, and check remediation status.

Copy all four values from the same screen: Global → Settings → Users → API Key. The Client Secret is usually a long base64 string (Z0FB…) - paste it exactly as shown.

Base URL

Tenant

Must match the tenant name you use to log in (case-sensitive).

Client ID

Client Secret

Liongard APICredentials for Liongard ROAR - used to sync environment maps on Client mappings and optionally enrich email DNS domain lists.

Create an API access key in Liongard: Settings → API Access Keys. Instance is the subdomain in your ROAR URL (e.g. us2 from https://us2.app.liongard.com).

Instance

Access key ID

Access key secret

API key (optional)

Base64 of key_id:secret if set instead of the fields above.

ConnectWise Manage (PSA)API credentials and defaults for creating service tickets from review findings in ConnectWise Manage.

API keys from Manage: System → Members → API Members → API Keys. API URL is your site base (e.g. https://na.myconnectwise.net/v2025_1) - VScanMagic adds /apis/3.0 automatically. The Client ID header is not the public key; register a Client ID (UUID) at developer.connectwise.com (NA region for na.myconnectwise.net). Internal/private integrations do not need a marketplace listing. The API member's security role must allow: Service Boards (Inquire) for the connection test; Companies / Company Maintenance (Inquire) for Configuration → Sync from Manage; Contacts / Contact Maintenance (Inquire) for deliverable email greeting and client address; Service Tickets (Add) for creating tickets from Deliverables; Ticket Notes (Add/Edit) so notes land under your Manage member; Service Tickets (Edit), Schedule (Add/Edit), and Time (Add) for closing review tickets from Deliverables.

API URL

Company ID (auth)

Public key

Private key

Client ID header

UUID from ConnectWise Developer Portal - required on every Manage API call since 2019.

Default service board

Default new-ticket status

Review ticket status name

Applied after time is logged when closing a review ticket (Scan Ticket Notes).

Meeting review status name

Applied after the client meeting (Meeting Ticket Notes).

Review time-entry status name

Set before logging time - Manage requires a status that allows time entry.

Manage member identifier (shared default)

Used for tickets, notes, and review time when a signed-in user has not set their own identifier below.

Your Manage member identifier

Per-user override - tickets, notes, and review time land under your Manage member instead of the API member.

Review time work type ID

Manage setup → Time → Work Types. Required to log review time.

After Hours RMIT+ work type ID

Used instead of the work type above when the After Hours RMIT+ checkbox is selected while closing a review ticket.

Review board name

Review ticket summary

Review time billable option

Review ticket type

Review ticket subtype

Review ticket item

Review ticket owner identifier

Optional. Or set owner member ID below.

Review ticket owner member ID

Follow-up business days

Follow-up time (hour)

Local time, 24h (10 = 10:00 AM).

Follow-up duration (hours)

Follow-up schedule type ID

Manage setup → Schedule → Types. Required for follow-up entry.

No-answer close status name

Referenced in the follow-up internal note on Templates.

Hatz AIPer-user key. Deliverables and Review show Hatz only after you save a key and a model here.

API key

Stored on your user only. Improve ticket bodies and AI review stay hidden until a key and a model are saved.

Model

Load models after you paste a key, then Save Settings.

2. Review session defaults

Defaults applied when you start or open a review - filters, host selection, CVE context, and optional email DNS findings.

Vulnerability scan filtersDefault EPSS and severity filters when loading ConnectSecure data into a review session. Export Top N is set per client on Start client review.

Min EPSS

Applies to application and registry findings. Network, external, and email DNS often have no EPSS - they still appear when they match the severity checkboxes. External starts in the export set; network stays on Add to export.

Critical

High

Medium

Low

Shift-click to toggle a range of severity levels.

OS host selection thresholdsFor Windows OS findings from the Application scan, hosts below these vulnerability counts start unchecked in review. Registry, network, and third-party app findings are never auto-filtered.

Windows 11 - minimum host vuln count

Default 350 (matches legacy VScanMagic). Hosts below this are unselected for Windows 11 tabs.

Other Windows - minimum host vuln count

Windows 10, Windows Server, etc. 0 = include all hosts.

Other operating systems - minimum host vuln count

Linux, macOS, ESXi, etc. 0 = include all hosts.

CVE enrichment (NVD + CISA KEV)Fetch CVE descriptions, vendor links, and known-exploited context for review findings that lack ConnectSecure fix text.

Data comes from the NVD API and CISA KEV catalog. Results are cached under your config folder (KEV auto-refreshes after 24 hours).

Auto-fetch remaining NVD details when opening Review

New sessions auto-fetch NVD for up to 15 export findings at creation; larger export sets need Load NVD details per finding.

NVD API key (optional)

Without a key, lookups are limited to about 5 requests per 30 seconds.

CISA KEV catalog

Version 2026.10.30 · 1,766 CVE(s) · last fetched 10/30/2026 4:32 PM.

Email DNS (SPF / DMARC / DKIM)Optional mail-authentication checks on Company Review and Review sessions. Domains come from Client mappings; assessments use live public DNS.

Domains are managed under Client mappings → Liongard map (manual entries and Sync from Liongard). Liongard API credentials are in External integrations above.

Show email DNS findings in review workflows

Use Liongard domain cache when configured (requires API credentials and environment map)

Turn off to skip Liongard map validation; still uses domains listed under Client mappings → Liongard map.

3. Reports & deliverables

Where exports are saved on disk and how your name, company, and client email defaults appear on reports and deliverables.

Report output foldersWhere quarterly Word, PDF, and Excel exports are saved under each client's documentation folder.

Reports Base Path

Locked for all users by server configuration (VSCANMAGIC_REPORTS_BASE_PATH).

Last Output Directory

Used when the base path is empty or a client folder cannot be matched automatically.

Report author identityDefault presenter name, company, and email signature used on new review sessions and deliverable emails.

Prepared By

Company Name

Leave my name off the deliverable email and use my Outlook signature

The email keeps its closing (Sincerely,) and stops there, so Open in Outlook drops your signature right below it. Reports and tickets still use Prepared By.

Deliverable email defaultsDefault scheduling link inserted into quarterly client deliverable emails. OneDrive links are pasted per session on Deliverables.

TimeZest username

When set, Export looks up the open Manage review ticket and fills in the scheduling link below with the ticket number. Leave blank to always use the manual link.

Scheduling link (TimeZest)

Inserted as {SchedulingLink} in the email template.