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

# Support and recovery

> Choose the right help route, report faults and resolve unavailable actions.

<h2 id="problem-reports">
  1\. Problem reports
</h2>

<span id="problem-reports-overview" />

Start with the [Community forum](/help/get-help#community-forum) for general how-to, usage and workflow questions. Use Report a problem when a fault needs the team to inspect the task and its diagnostics.

Report a problem opens a dialog with a description, diagnostic bundle, technical context and a screenshot. The visible controls allow individual context items to be reviewed, copied or removed before sending.

Explain what you expected, what happened and how to reproduce it. Review the attached context and the dialog’s privacy information before submitting.

<span id="problem-reports-in-ideatura" />

1. Open the report from the affected screen.
2. Describe expected and actual behavior.
3. Review the included screenshot and technical context.
4. Submit only the material intended for support.

<span id="problem-reports-check-the-result" />

The report is reproducible and its included material has been reviewed.

<h2 id="workspace-support">
  2\. Workspace Support
</h2>

<span id="workspace-support-overview" />

For general questions about using Ideatura, start with the [Community forum](/help/get-help#community-forum), where other architects and the Ideatura team can read and contribute.

Use workspace Support to follow up on a relevant report or existing discussion. It has its own conversation, report entries, attachments and message box. Check the audience shown in its header before posting; a workspace discussion is not automatically private.

Review a problem report’s attached diagnostics and privacy information separately from the Support conversation’s audience. Share only the project material needed to explain the issue.

<span id="workspace-support-in-ideatura" />

1. Open Support.
2. Read the audience in the header.
3. Locate the relevant report or conversation.
4. Send a concise follow-up with the needed context.

<span id="workspace-support-check-the-result" />

The follow-up reaches the intended discussion with the relevant report context.

<h2 id="unavailable-actions">
  3\. Unavailable actions
</h2>

<span id="unavailable-actions-overview" />

Read the label or error beside an unavailable control. Check whether work is still loading, a required input is missing, access is unavailable or an application is disconnected.

Resolve the indicated condition before retrying. If work stopped partway, inspect what changed and save useful output so the next attempt does not repeat completed changes.

If you need help understanding the control or workflow, search the [Community forum](/help/get-help#community-forum) first. For a reproducible fault, use [Report a problem](/studio-reference/ui-support#problem-reports) with the error and relevant diagnostics.

<span id="unavailable-actions-in-ideatura" />

1. Identify the affected screen and operation.
2. Read its state or error.
3. Check the corresponding prerequisites.
4. Recover and inspect the actual result before retrying broadly.

<span id="unavailable-actions-check-the-result" />

The blocking condition is resolved, or you have the context needed for a forum question or problem report.


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