> 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/learning-paths/access-the-learning-paths-settings/general-settings-of-a-learning-path.md).

# General settings of a Learning Path

From the `General settings` page of your Learning Path, you can edit the following:

* The title and description
* The privacy settings:
  * **Public**: Visitors and members of the Spot can view the Learning Path. Only members can participate.
  * **Private**: Members of the Spot can view and participate to the Learning Path.
  * **Secret**: Only invited participants can view and participate to the Learning Path.
* The order of progression:
  * **Flexible**: Members can access the contents in any order.
  * **Sequential**: Members must complete the contents in the defined order.

Once you’ve made your changes, don’t forget to click `Save` to apply changes!

You can also delete the Learning Path from this page. To do so, click the `Delete` button at the bottom of the page. Please note that deletion is permanent and cannot be undone.


---

# 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/learning-paths/access-the-learning-paths-settings/general-settings-of-a-learning-path.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.