> 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/learning-paths-list.md).

# Learning paths list

Learning Paths are grouped in a list accessible from the top navigation bar of your Spot.\
This interface allows you to easily browse, search, and resume your ongoing training programs.

When you click on the Learning Paths button in the top bar, a modal window opens.\
It displays all the Learning Paths available to you, depending on your role and access level within the Spot.

Learning Paths are organized into different tabs:

* `Continue what you’ve started`: shows all the Learning Paths you have already started.
* `More paths`: includes the Learning Paths you haven’t joined yet.
* `Completed!`: lists the Learning Paths you’ve already finished.

{% hint style="info" %}

### Access rights

* Admins can see all Learning Paths in the Spot.
* Members can only see public, private, or invited Learning Paths.
* Visitors don’t have sorting tabs : they only see public Learning Paths.
  {% endhint %}

Each Learning Path is displayed as a card, which includes:

* The title of the Learning Path
* Its description
* The list of contents, displayed as small badges (completed contents appear in green)
* A highlighted section showing the next content to complete


---

# 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/learning-paths-list.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.