> 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/create-a-channel.md).
# Creating a channel
Give your members a voice in the discussion channels!
## Creating a new channel
You can create a channel directly from the `Add` button on the right-hand side of the `Channels` menu or from the `Manage My Spot` shortcut.
A drawer will appear allowing you to set up this channel:
1. Choose an **icon** (optional), a **name** (mandatory), and a **description** (optional).
2. Define its **accessibility**, i.e. the Spot members are able to see the items in this channel.
* Select `Public` if you want all members of your Spot to be able to see this channel.
* Select `Private` if you want to select which Spot members can access this channel.
3. Decide if you want to add all Spot members to the default channel
4. Decide if you want to display the list of channel members
5. Decide whether you want to allow or restrict members from sending messages.
6. Click `Create` – that's it, your channel is created! :clap:
Find out how to [add members to a private or public channel](/english/spot-content/discussions/add-or-delete-channel-members.md).
---
# 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/create-a-channel.md?ask=&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.
