===== Get help =====

**Use this section when you need to:**

  * find user manuals, quick answers, or issue-reporting routes
  * understand when to use Documentation, FAQ, Issues, or the service desk
  * build a useful support request that can be acted on quickly
  * recover from common blockers such as missing permissions or pending moderation states

**Main roles:**
  * All users

**Related sections:**
  * [[hortus:navigation|Start here]]
  * [[hortus:workspace|Work in My Workspace]]
 

Support in HORTUS is designed as a layered recovery system rather than as a single contact point. Documentation gives you structured explanations, FAQ gives you short validated answers, Issues gives you a problem-reporting route, and the service desk handles permission and operational escalation logic such as role activation

----

===== Documentation, FAQ, and Issues =====

Before requesting support, check available resources.

==== Documentation ====

  * User manuals
  * Guides and tutorials
  * Contextual help inside the platform

Use documentation to:

  * understand features
  * learn workflows
  * resolve common doubts


{{:hortus:support:support1.jpg?600|}}

----

==== FAQ (Frequently Asked Questions) ====

FAQ sections provide:

  * quick answers
  * solutions to recurring issues
  * clarifications on common workflows

Use FAQ when:

  * you need a fast solution
  * the problem is likely common

{{:hortus:support:support2.jpg?600|}}
----

==== Issues / tickets ====

If documentation is not enough:

  * create a support request (issue/ticket)
  * describe your problem clearly
  * track resolution progress

Some support processes may involve external systems.

{{:hortus:support:support3.jpg?600|}}
----

^ Use this when… ^ Best route ^ Why ^
| **You need the full explanation of a feature or workflow.** | Documentation | Long-form guidance is easier to follow when the task has several steps or roles. |
| **You need a quick answer to a recurring question.** | FAQ | A shorter answer is faster when the problem is already common and well understood. |
| **You need to report a bug, incident, or improvement idea.** | Issues | The request enters the issue-handling path instead of getting lost in email threads. |
| **You need role activation or an operational permission change.** | service-desk@ampersand.it | The service desk is the right route for account activation and operational escalation. |