Differences

This shows you the differences between two versions of the page.

--- hortus:support:documentation [2026/04/07 14:57] – savino.frisardi
+++ hortus:support:documentation [2026/04/08 12:30] (current) – savino.frisardi
@@ Line 1: / Line 1: @@
 ===== Get help =====
-Use this section when you need to:
+**Use this section when you need to:**
   * find user manuals, quick answers, or issue-reporting routes
@@ Line 8: / Line 8: @@
   * recover from common blockers such as missing permissions or pending moderation states
-Main roles:
+**Main roles:**
   * All users
-Related sections:
+**Related sections:**
-  * [[hortus:navigation|Navigation]]
+  * [[hortus:navigation|Start here]]
-  * [[hortus:workspace|My Workspace]]
+  * [[hortus:workspace|Work in My Workspace]]
-  * [[hortus:publish|Publishing workflows]]
 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
@@ Line 69: / Line 69: @@
 {{: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. |