> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/personal-settings-and-support/support-and-deployment-diagnostics.md).

# Support and deployment diagnostics

Use Support settings to find the support contact for your organization. Deployment details help the support team identify the version of StackAI you use.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FzmEpH6UI8XHb0RDGAHKT%2FG106.mp4?alt=media&token=0807852e-9034-4ec0-8f77-925859a6571e>" %}

## Before you start

Collect the project, expected result, error, and time before opening the support form. If the problem is account access and you cannot reach Settings, ask an organization administrator to use the established support contact on your behalf. IT should own identity-provider issues identified in [Password recovery and MFA](https://docs.stackai.com/guides-and-quickstarts/personal-settings-and-support/password-recovery-and-mfa.md).

## Find your support contact

Open **Settings → Support**. Your available support options appear under **Your point of contact**.

![Settings Support contact options](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/RETv5V16Q6YOIVTvf6Wu/assets/g106-g106-01-support.png)

Select **Ask for help**, or use **Copy Support Email** to copy the address into your email application.

![Ask for help and Copy Support Email](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/FAnY6OXnHB7iJcux4j6C/assets/g106-g106-02-copy.png)

## Include deployment information

Open **Deployment Info**. This page shows the environment and available application and database version details.

![Deployment Info version details](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/OQYM82yLKj78GwicfNFV/assets/g106-g106-03-deployment.png)

Use the copy controls to copy the requested identifiers into your support request.

![Deployment identifier copy controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/NUWeh5rtaxEE7kZkvJJa/assets/g106-g106-04-versions.png)

## Describe the issue

Explain what you were trying to do, the steps you followed, and what happened. Include the expected result, the time and time zone, and the affected project where relevant.

![Support issue description](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/OI457cDKwemEV9ZPwfI8/assets/g106-g106-05-draft.png)

Add a screenshot or error message when it helps explain the issue.

## Important behavior

Remove passwords, API keys, and unrelated personal information before sending a support request.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/personal-settings-and-support/support-and-deployment-diagnostics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
