Dashboard menu guide
The purpose of each Dashboard menu and the next action it supports.
The Hunt Web Dashboard organizes assessment setup, scan execution, findings, conversations, and administration into separate menus. This guide explains the purpose of each menu, the information available, and the next action it supports. Menu access and available controls follow the signed-in account's permissions. Results and Report belong to individual Runs and open from the Run workspace.
1. Dashboard: Review Current Assessment Activity
Dashboard is the starting point for reviewing work across accessible Targets and Runs. It displays Active Targets, Active scans, Paused scans, Verified findings, the five most recent Runs, findings grouped by severity, and a Health summary.
Use Refresh overview and the last-checked timestamp to review the current readout. Open a recent Run to inspect its progress, or select a severity group to examine the corresponding findings. Add Target starts application setup; Prepare a scan opens Run preparation.
The overview summarizes saved work. Restricted or unavailable data is shown separately from a confirmed zero count. Detailed request history and execution events are available inside the relevant Run.
2. Targets: Prepare Applications and Account Access
Targets manages applications before scanning. Search by name or URL, open an existing Target, or select Add Target to choose Blackbox, Greybox Environment, or Greybox Browser.
Target setup contains the saved Scope and its revisions, application URLs, and account configuration. Greybox Environment uses uploaded account access and authentication checks. Greybox Browser uses the account's interactive Chromium session on Desktop. One-account and two-account configurations support assessments involving different identities or roles.
Review Application URLs to test and detected application hosts before preparing a Run. Login/support URLs serve authentication setup; they do not automatically expand testing boundaries. A Run retains its saved Scope snapshot. A Run with the automatic host policy can admit related application hosts that meet that policy (see Application hosts and account access); other additions require a new Scope revision and a subsequent Run.
Use Archive Target to move an eligible Target out of the active list. Open Trash displays archived Targets. Eligible entries offer Restore Target and Delete permanently, with confirmation for permanent removal. Use Prepare Run from a prepared Target to continue into scanning.
3. Runs: Control Scans and Inspect Saved Work
Runs lists saved scans with their Target, Scope, profile, and status. Search and filter the list to find a specific assessment. New Run opens preparation, including Quick, Standard, or Deep profile selection and the time limit.
Opening a Run reveals four main tabs:
| Tab | Information and actions |
|---|---|
| Overview | Scan context, status, lifecycle controls, detected application hosts, and links to results. |
| Investigation | Saved Surface, Traffic, Experiments, Evidence, and Activity views. |
| Results | Recorded assessment results for this Run. |
| Report | The saved report snapshot and PDF download. |
Within Investigation, Surface lists recorded pages and endpoints; Traffic contains request and response references; Experiments shows investigation checks; Evidence provides saved evidence references; and Activity records execution and lifecycle events.
Use Pause scan to suspend work, wait for the saved Paused state, and select Resume scan to continue. Finalize Run closes the Run for further scanning while retaining its findings and reports. Available controls depend on the Run's state and account permissions.
Archived Runs provides restoration and permanent-deletion controls for eligible entries. For a connection interruption during a control request, use Check previous request when offered to recover its recorded outcome.
4. Findings: Examine Verified Issues and Evidence
Findings brings together verified findings from accessible Runs. Search by finding text, target, or endpoint, then filter by severity, Target, or Run. This is useful for prioritizing review across several assessments.
Open a finding to inspect its description, affected endpoint, recommended remediation, and available evidence. Detail sections can include verifier observations, reproduction steps, saved requests and responses, and proof-of-concept code. Links return to the originating Run and its results.
A finding's verified status describes the automated verification workflow. Evidence still requires human review. Inconclusive investigation checks can remain in the Run without becoming verified findings.
5. Hermes Chat: Continue an Existing Assessment
Hermes Chat connects instructions to a selected Run. Open it through Open in Hermes Chat from a Run, or use Continue a scan to select previous work. Recent conversations provide access to saved exchanges.
The conversation can read earlier scan results and request history, summarize unfinished checks, and accept instructions for additional investigation. The selected Run supplies its saved Scope, testing mode, and configured accounts. A question about previous work can be answered from saved context; an instruction to continue testing can activate further scanner work.
Use the linked Open Run, Results, and Report controls to compare replies with recorded outcomes. After a connection interruption, refresh or reconnect to read the saved instruction state before retrying. Deleting a conversation through its menu retains the Run and its saved scan results.
6. Assistant: Ask General Cybersecurity Questions
Assistant provides general cybersecurity conversation with a configured model. Select Ask a general question, choose an available model, and submit a question. Recent conversations can be reopened, renamed, or deleted. The composer also supports TXT/JSON attachments within its displayed limits.
Scan data is not included automatically. Assistant is suitable for explaining security concepts, discussing testing approaches, or interpreting text explicitly supplied in the conversation. Hermes Chat is the Run-connected interface for reading saved assessment context and continuing scanner work.
Assistant requires its own configured provider/model and an explicit access permission, including for Admin accounts. Its configuration is managed separately from Hermes Chat.
After a message is sent, Assistant shows Assistant is thinking with an animated icon, moving dots, and the elapsed waiting time until the reply finishes. See What's new.
7. Chat Templates: Prepare Focused Instructions
Chat Templates contains editable instructions for Hermes investigations. Search by focus, mode, phase, or purpose; filter by Continue, Audit, Focus, or Results; then choose English or Indonesia.
Select a template, review its content, and adjust the wording where needed. Copy complete template copies the displayed text, including edits. Paste the instruction into the intended Run's Hermes conversation and send it there. Copying a template does not start a scan.
Editor changes are temporary and tracked separately for each language until the page is refreshed. Refresh restores the default templates in English.
8. Health: Check Component Readiness
Health reports the state of the Hunt Web CLI, Dashboard database, saved reports, Hermes connection, subdomain discovery command, and Greybox Browser command. Use Refresh status after configuration changes or when a component appears unavailable.
Each card explains its check and the next step. For example, Needs setup indicates missing configuration, Check failed indicates an unsuccessful check, and No saved reports means that no report is recorded yet.
Readiness checks have specific limits: a connected Hermes Gateway does not confirm a successful model response, and a Browser command being available does not confirm that an account is logged in. Check account access from the Target.
On Server installations, interactive Greybox Browser displays Unavailable in Server mode. Headless Chromium remains available to supported scanner tools; Blackbox and Greybox Environment do not require the interactive Desktop login window.
9. Settings: Configure the Workspace and Model Services
Settings provides administrative configuration in five categories:
| Category | Purpose |
|---|---|
| Instance | Workspace defaults, including the activity-period preference. Changing that preference does not delete stored events. |
| Assistant | Assistant providers, models, prompts, and availability settings. |
| Hermes Chat | Hermes provider access and the default model selection for new conversations. |
| Storage & Retention | Recorded storage usage, retention rules, eligible cleanup, and security-history archive management. |
| Security Audit | Protected records of workspace access and changes, with person and event-type filters. |
Saving a Hermes default does not replace the model in existing conversations. Review the selected model in the conversation itself when continuing work. Refreshing the Hermes connection and model list does not send a test prompt.
Storage cleanup follows its displayed eligibility and confirmation steps. Saving retention rules alone does not immediately clean up records. Security Audit is a protected history; individual events cannot be deleted from that view, and retention is handled separately.
10. Users & Roles: Manage Team Access
Users & Roles allows an active Admin to create accounts, search people, filter by role or status, enable or disable accounts, and manage feature permissions.
Admin
Manages accounts and settings, with built-in access to registered Hunt Web features. Assistant still requires a separate permission.
Operator
Uses the features explicitly granted to the account. The role alone does not authorize scanning.
Viewer
Reads permitted features. Cannot start scans, send Hermes instructions, use Assistant, or manage accounts.
The feature-permission panel distinguishes access Included with role from additional grants. Reading Runs, starting profile scans, controlling scans, and continuing through Hermes are separate capabilities. Resource access and scan readiness are also checked when those actions are requested.
Review permissions after a role change. A disabled account cannot sign in; reenabling it does not automatically restore permissions previously removed. For account creation, permissions, and role changes in detail, see Dashboard Accounts and Roles.
Account Menu — Profile, Security, and Sign Out
The account control at the bottom of the navigation opens Profile & preferences, Security / Sessions, and Sign out. Profile settings cover personal account details; Security / Sessions manages passwords, authenticator protection, recovery codes, and signed-in sessions.
Admin accounts accessing the Dashboard through a domain must complete the required authenticator onboarding before opening scan pages. That onboarding is separate from role assignment and feature permissions.
Choose the Menu That Matches the Task
| Task | Navigation |
|---|---|
| Prepare a new application | Targets → Add Target → Scope and account setup |
| Start an assessment | Prepared Target → Prepare Run, or Runs → New Run |
| Inspect recorded requests | Runs → selected Run → Investigation → Traffic |
| Review verified issues | Findings → selected finding → evidence and Run links |
| Continue an investigation | Selected Run → Open in Hermes Chat |
| Download an assessment PDF | Runs → selected Run → Report |
| Diagnose component availability | Health → Refresh status |
| Configure models or team access | Settings or Users & Roles |
For the complete assessment sequence, continue with the scanning workflow guide. Installation requirements and initial account setup are covered in the Linux Desktop guide and Linux Server/VPS guide.