Dashboard documentation

When it appears

• Shown in the Account rail while steps remain or until you dismiss the guide.
• Hidden automatically when the checklist is complete and dismissed.

Recommended flow

1. Open Account and select the setup guide if it is pinned in the rail.
2. Add priority vendors to your watchlist and confirm notification channels.
3. Visit the dashboard to confirm incidents and activity match expectations.
4. Optional: enable monitoring or enroll a probe on Pro+ if you need LAN vantage.

What you see

• Rollups scoped to vendors on your watchlist, not the full Huntertech catalog.
• Signals when vendors you follow have open incidents, maintenance, or notable changes.
• Paths into vendor overview, incidents, analytics, and compliance where your plan allows.

Daily workflow

1. Start at /dashboard after sign-in to scan open work.
2. Open a vendor card to drill into incidents or maintenance detail.
3. Use notifications inbox for items you may have missed since last visit.

Adding and removing vendors

1. Open Account → Watchlist.
2. Search or browse vendors and add the ones you operate or advise on.
3. Remove vendors you no longer need to reduce noise in dashboard and alerts.

Downstream effects

• Notification rules and digests respect watchlist membership.
• Community hub highlights ongoing incidents for watchlist vendors.
• Enterprise contracts and quarterly reports align to watchlist vendors.

Domain stack

• Track domains with RDAP, DNS, TLS expiry, and related health signals.
• Useful for renewal planning alongside vendor status monitoring.

API checks

• Configure HTTP methods and URLs; review rollup charts in the workspace.
• Assign checks to probe agents when you need office or customer LAN vantage.

Probe agents (Pro+)

• Enroll Windows agents, assign monitors, and review health in Account → Monitoring.
• Install, permissions, telemetry, and troubleshooting live in Probe agent documentation.

Reading and clearing alerts

1. Open Account → Notifications.
2. Select an item to jump to the vendor page, monitor, or community context when linked.
3. Mark items read as you triage; delivery settings control what arrives here versus email or Slack.

Tuning volume

• Adjust channels and rules under Account → Notification settings.
• Use per-vendor mutes during planned maintenance windows.

Plan requirement

• Enterprise plan required.
• Pair with quarterly reports for executive QBR prep.

Typical fields

• Vendor linkage, contract value or spend notes, renewal dates, and product SKUs or tiers.
• Internal notes for account teams and procurement stakeholders.

When to use reports

• Executive or customer QBR readouts.
• Archival snapshots alongside live vendor pages.

Plan requirement

• Enterprise required for PDF quarterly exports.
• Other plans still use vendor pages, analytics, and dashboard rollups in product.