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

# Support & feedback

> How to reach mory support, what a good bug report contains and how to submit feature requests, test protocols and training requests.

This page explains how to get help when this help center does not answer your question, and how to submit improvement requests.

## Reaching support

* **Support link**: In the navigation at the top right of this help center you find the **Support** link. It takes you directly to the contact options.
* **Email**: Write to [support@mory.app](mailto:support@mory.app).
* **Your mory contact person**: For organizational questions and training, contact the person who supports your organization.
* **Internally**: Many questions about roles, **Mandanten** (clients) or missing properties can be solved directly by your administrator in **Einstellungen** (Settings).

<Tip>
  Before reporting, take a quick look at the [FAQ](/en/help/faq) and [Troubleshooting](/en/help/troubleshooting). Many topics can be resolved in a few minutes.
</Tip>

## What a good bug report contains

The more precise your report, the faster the solution. Please include:

| Information                                                        | Why it helps                                                                                                               |
| ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
| **Task number** (format T-YYMMDD-NNN) or link to the affected page | We find the case immediately without searching by name.                                                                    |
| **Screenshot** of the message or state                             | Shows error messages and context that are hard to describe. Please do not include sensitive data unrelated to the problem. |
| **Time** (date and time of day)                                    | Allows support to trace what happened.                                                                                     |
| **Expected and actual behavior**                                   | One sentence for each avoids follow-up questions.                                                                          |
| **Steps to reproduce**                                             | What did you click, in which order?                                                                                        |

<Warning>
  Never send passwords or credentials. mory uses sign-in via Google or Microsoft only; support never needs your password.
</Warning>

## Improvement requests

Ideas for new features or improvements are welcome. Describe the goal ("I want to ...") and the situation in which you miss the feature, rather than only the solution. Your mory contact person records the request and gets back to you.

## Training and onboarding

* **Onboarding**: New organizations are supported in setting up organizations, clients, users, roles and **Workflows**.
* **Training**: For teams we offer introductions to the core processes, especially working with mory and the workflow checklists. Arrange dates via your mory contact person.
* **Self-study**: Start with [What is mory](/en/welcome/introduction) and the [Workflows overview](/en/workflows/overview).

## Related pages

* [FAQ](/en/help/faq)
* [Troubleshooting](/en/help/troubleshooting)
* [What's new](/en/help/whats-new)