Hunter reports in Backoffice

Hunter Reports is the Backoffice page where page audits that your team sent from the Hunter browser extension land. A workspace administrator creates upload tokens and can delete reports. Analysts and administrators can read them.

Nothing is uploaded automatically. A report arrives only when someone pastes an upload token into the extension and presses Send on that report.

What it is

Availability: depends on your organisation and the modules enabled for it; ask your account team.

The page lives under Backoffice → Session Insights → Hunter Reports. It does not appear in the sidebar, and its address answers “not found”, until Hunter report upload is switched on for your environment. When it is not switched on, Backoffice shows “Hunter report upload is not switched on yet”.

Who can do what

What a report contains

A report lists which scripts used which browser features during one page load in one browser. The page states that a report never contains page content, the values those features returned, or anything that identifies a visitor. It names the reporter: the administrator who created the token that was used to upload it.

A high rating describes what that page did at that time. It is not a verdict about the site, and a page that behaves differently on other visits can look quieter.

Retention

Uploaded reports expire 30 days after upload. The list shows each report’s expiry in its “Deleted after” column, and the detail page counts the days left. Administrators can delete a report earlier. This retention applies to Hunter reports only; identity-verification data follows a different rule, described in Verification data: storage, access and deletion.

What the audit log records

Backoffice writes an audit row for each of these, without copying report content or the token:

The token itself is never stored, logged or audited. If the audit row for a new token cannot be written, no token is handed out.

What the list and the detail show

Prerequisites

• Hunter report upload switched on for your environment, and a Hunter build that includes sending. Ask your account team.
• Analyst role to read reports; administrator role to create tokens and delete.
• A device that can complete step-up MFA, for tokens and deletions.

Steps

1. Create an upload token

1. Backoffice → Session Insights → Hunter Reports → Create upload token.
2. Pick a Lifetime: 5 minutes, 15 minutes, 1 hour, 4 hours or 12 hours. The default is 12 hours.
3. Press Create token and confirm the fresh verification code prompt.
4. Press Copy upload token.

The token is shown once. Close the window and you need to create another. The token lets one browser upload reports to this workspace until it expires. It cannot read, list or delete anything.

2. Give the token to the person who will send reports

In the Hunter extension: Options → Send reports to your organisation (optional) → paste it under Report token. See Hunter browser extension. Every report sent with the token is stored under your workspace and linked to the administrator who created it, so create tokens for people you trust and with a short lifetime.

3. Find a report

The list shows newest first, with Page, Risk score, Feature rating, Uploaded, Deleted after, Size and Actions. Open Filter reports to narrow it:

• Page contains, for example example.com/checkout.
• Risk score and Feature rating: Low, Medium, High (risk also has Critical).
• Uploaded from and Uploaded until.

Press Show more reports to load another page. A page holds 50 reports by default and at most 100.

4. Read a report

Open a row. The detail page has these sections: Risk score, Feature rating, Capture health, Scripts observed, Vendors recognised, Network and script findings, Activity by feature area and Data versions. Capture health tells you whether the extension could observe every feature area; a failed area can make a page look quieter than it is. If a report uses a format the page cannot display, the summary stays correct and you can download the JSON.

5. Download the JSON

Press Download JSON. The file is named hunter-report-<id>.json. The response carries the header X-Hunter-Payload-Sha256, the digest stored with the report, so you can check that the file you hold is the file Noxtica stored.

6. Delete reports

• On a report, press Delete, then Delete report. The report is permanently removed from the workspace.
• On a report, press Delete all reports from this reporter to remove every report uploaded with a token created by that administrator.

A report uploaded in the last few minutes can take a few minutes to disappear completely; if it reappears, delete it again. Each deletion is recorded in the audit log. See Audit log and data export.

Verify it works

• A new token appears with “Expires ” and a copy button.
• After a send from the extension, the report is listed with its page, risk score, rating, upload time and expiry. The extension shows “Sent. Your organisation’s Noxtica workspace stored report until ”.
• The downloaded file opens as JSON and its report schema is noxtica.hunter.report/v1.
• After a delete, the page shows “Report deleted.” or “Deleted N reports from this reporter.”

Troubleshooting

Related

• Hunter browser extension for audits, the preview and sending.
• Spot captures for operator-started recordings.
• Roles and permissions for analyst and administrator capabilities.
• Audit log and data export for the records of reads, tokens and deletions.
• Privacy and Security for data handling.