> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acusight.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get help

> Where to go when you're stuck — support channels, what to include in a report, and how to follow known issues.

Start with [Troubleshooting](/reference/troubleshooting) — most issues have a quick fix from the dashboard. If yours doesn't, here's how to reach us and how to make your report easy to act on.

## Channels

* **Bugs & feature requests** — [open an issue on GitHub](https://github.com/ArcturusNetworks/acusight/issues). This is also where fixes and known issues are tracked, so search existing issues first — yours may already have a workaround.
* **Docs feedback** — every docs page has a thumbs rating; use it to flag anything unclear, wrong, or missing. It goes straight to the team.
* **Self-managed & on-prem** — deployments you run yourself are supported directly. [Contact your AcuSight representative](/hardware/air-gapped) for operational issues with platform services, storage, identity, or networking.
* **Security vulnerabilities** — don't open a public issue; contact us directly through [acusight.io](https://acusight.io) or your AcuSight representative so a fix can ship before details are public.

## What to include

A report we can reproduce is a report we can fix. Include:

* **What you did, what you expected, what happened** — the three sentences that matter most.
* **Where** — your organization name, and the device name for device issues (from **Devices**).
* **When** — timestamps and your timezone, so we can line your report up with what the platform saw.
* **What it looked like** — screenshots of the dashboard, error messages verbatim, and for training issues the job's status and logs (both visible on the training job page).

## Known issues

Known issues and their status live in the [GitHub issue tracker](https://github.com/ArcturusNetworks/acusight/issues). If you hit something already reported, add a comment with your details rather than opening a duplicate — it bumps the signal and you'll be notified on the fix.

## Next steps

<CardGroup cols={2}>
  <Card title="Troubleshooting" icon="wrench" href="/reference/troubleshooting">
    Common issues and their quick fixes.
  </Card>

  <Card title="Changelog" icon="clock-rotate-left" href="/reference/changelog">
    What's shipped recently.
  </Card>
</CardGroup>