> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/spot-content/discussions.md).

# Discussions

Take a group of individuals, and foster interaction among them to create a vibrant adademy.

In your discussion channels, both admins and members have the opportunity to express themselves, help each other out, and engage in meaningful conversations.

## Navigation&#x20;

On this page, on the right, you'll find a list of the different discussion channels to which you're a member, ready to immerse yourself in captivating and rewarding exchanges.&#x20;

## Channel or Topic?

### A discussion channel&#x20;

The channel is an interactive space where you can talk to other members. Send messages, embed links and documents, react to messages and reply to a particular message in a thread. Below the channel list, a `More channels` button lets you discover the different channels available to you on the Spot.&#x20;

### A Topic

A forum is an interactive space that lets you group exchanges into Topics. Create Topics, add links and documents, react to messages and vote for certain Topics!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.meltingspot.io/english/spot-content/discussions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
