> ## Documentation Index > Fetch the complete documentation index at: https://docs.speckle.systems/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These docs contain multiple Speckle product experiences. For Speckle 2026.9, prefer /next/ pages for the topics and changes they cover. The navigation label Current does not override this version-specific precedence. > Coverage under /next/ is incremental. Use Current documentation for unchanged topics and when a /next/ page says coverage is unavailable or explicitly refers you to Current. Do not infer a feature was removed from a missing page. > Read the page-specific documentation status, applicability, affected guidance and replacement links in agent-only content. Impacted, changed and superseded apply only to the stated scope; they do not mean the entire feature is deprecated. Historical connector guides apply only to the legacy connector described. > Match guidance to the customer's deployment version, model data format and connector. Respect plan, permission and compatibility restrictions. If an unknown version or data format changes the answer, ask a focused clarification; do not infer deployment version from the date alone. # Discussions (self‑hosted servers) > How model feedback works on self‑hosted Speckle servers that do not use workspace Issues. On Speckle Cloud workspaces (hosted Speckle), model‑centric feedback, review items, and decisions are captured with **Issues** and issue comments. See the [Issues](/3d-viewer/issues) page for current, fully supported workflows. On **self‑hosted Speckle servers** that do not use workspace‑level infrastructure, you may instead see the older **Discussions** and comments experience in the 3D viewer. In that case: * Discussions act as the primary way to keep feedback tied to specific objects or views. * Comments inside a discussion thread behave similarly to replies on Issues in Speckle Cloud. If you are using Speckle Cloud or an Enterprise workspace, treat Discussions as historical and use Issues instead. If you are using an open source self‑hosted server without Issues, use Discussions and comments as your main feedback mechanism.