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

# Support

> Get help and find resources for Hexel Studio.

## Get help

<CardGroup cols={2}>
  <Card title="Console" icon="gauge" href="https://console.hexelstudio.com">
    Manage your account, view usage, and access support from the dashboard.
  </Card>

  <Card title="Contact Sales" icon="envelope" href="mailto:enterprise@hexelstudio.com">
    Enterprise plans and custom needs.
  </Card>
</CardGroup>

## Before you reach out

To get help faster, include these specific fields in your ticket:

| Field               | Where to find it                                                       | Why it matters                                           |
| ------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------- |
| `error_code`        | Error response body (e.g., `quota_exceeded`, `AUTH.PERMISSION_DENIED`) | Immediately narrows the problem category.                |
| `request_id`        | Data Platform error response body                                      | Lets support trace the exact operation in internal logs. |
| `environment_id`    | Console → IAM → Environments                                           | Identifies which isolated context the issue occurred in. |
| `workspace_id`      | Console → Workspace settings                                           | Narrows the scope to the correct project.                |
| **Timestamp** (UTC) | Your application logs or the Console log viewer                        | Required to correlate with platform-side telemetry.      |
| **Resource ID**     | The agent, instance, task, sandbox, or store identifier                | Pinpoints the affected resource.                         |

<Warning>
  Tickets without `error_code` and timestamp take significantly longer to resolve — support must search across all your resources to find the relevant event.
</Warning>

Many issues have quick fixes in [Troubleshooting](/docs/troubleshooting).

## Resources

<CardGroup cols={3}>
  <Card title="Quickstart" icon="rocket" href="/docs/getting-started/quickstart">
    Get up and running.
  </Card>

  <Card title="API Reference" icon="book" href="/docs/api-reference/introduction">
    Full REST API.
  </Card>

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

## Status and security

* For account or billing questions, use the Console.
* If you believe you have found a security issue or exposed credential, rotate the affected credential immediately and contact the team.