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

# Feedback & Support

> Where to ask for access, report issues, and bring docs gaps back into the repo.

Use the Fleet Manager team as the first routing point for both access requests and runtime issues.

## Access Requests

Raise access requests in the `#fleet-manager-chat` Slack channel. See
[Getting Access](./getting-access) for what operators and users typically need, or the
[Developer Guide](../developer-guide/overview) for local development setup.

## Documentation and Code Feedback

If you find drift, gaps, or stale instructions in the docs, let the team know in
`#fleet-manager-chat`. If you want to contribute a fix directly, the docs are sourced
from this repository — see [Contributing to the Docs](../developer-guide/overview#contributing-to-the-docs).

## Runtime and Deployment Support

When reporting an issue, include the smallest useful set of facts:

* Site and environment
* [Device](./glossary#node) names or workflow/job identifiers
* Which subsystem appears involved: Fleet Manager API, [NetBox](./glossary#netbox), [Temporal](./glossary#temporal), [DHCP](./glossary#dhcp), OpenStack, or [SLURM](./glossary#slurm)
* Any relevant Grafana Loki queries, Temporal history, or NetBox state

## First Places To Look

The current runbooks consistently rely on these systems for investigation:

* **Temporal UI** for workflow execution history
* **Grafana** for logs, metrics, and dashboards
* **NetBox** for source-of-truth inventory and device-state checks

If the issue is deployment-specific, the [Site Validation](../deployment-guide/new-site-deployment/site-validation)
page is the best starting point for the expected checks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.