> For the complete documentation index, see [llms.txt](https://docs.hashsphere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashsphere.com/support/support-overview.md).

# Support Overview

Support is included with [HashSphere Managed Service](/managed-service/architecture-overview.md).

### Access to the Support Portal

Portal access is granted to designated customer personnel during onboarding.

Support Portal URL: <https://support.hashgraph.com/>

<a href="https://support.hashgraph.com/" class="button primary" data-icon="headset">Open Support Portal</a>

If you need access, contact your HashSphere representative.

### What the portal is for

The portal provides two core services:

* **Knowledge base**: searchable access to Hedera and HashSphere resources
* **Support tickets**: raise, update, and track support requests

The knowledge base aggregates Hedera, Hiero, Hashgraph, and HashSphere resources.

{% hint style="warning" %}
Do not share private keys, seed phrases, or un-redacted secrets in support tickets.
{% endhint %}

### Support landing page

The landing page is the quickest way to search the knowledge base and create tickets.

{% embed url="<https://www.canva.com/design/DAHCiFApBsE/sZlWQG6t1-yiNKsjN-0mmg/view>" %}

Ticketing lets you report issues, communicate with support, and track progress.

### User menu

Clicking on the user icon in the top right gives access to the following options:

<div data-with-frame="true"><figure><img src="/files/DzyD8SAT4jTJXC6Dmi3U" alt="" width="362"><figcaption></figcaption></figure></div>

* **Profile**: customize profile and set up two-factor authentication
* **Requests**: view and manage support requests
* **Contact details**: add a photo and a short bio
* **Change password**: update your portal password
* **Sign out**: sign out of the portal

### Next steps

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><a href="/pages/VPI3ZXdEHcCUC285TpeH"><mark style="color:$primary;"><strong>Raising Support Tickets</strong></mark></a></td><td><a href="/pages/VPI3ZXdEHcCUC285TpeH">/pages/VPI3ZXdEHcCUC285TpeH</a></td></tr><tr><td align="center"><a href="/pages/VPI3ZXdEHcCUC285TpeH"><mark style="color:$primary;"><strong>Managing Support Tickets</strong></mark></a></td><td><a href="/pages/oflax6xdMks2tdadvibB">/pages/oflax6xdMks2tdadvibB</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hashsphere.com/support/support-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
