> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/search-and-workspace/using-workspace/getting-a-personalized-learning-path.md).

# Getting a personalized learning path

Enable [Experimental mode](/user-guide/search-and-workspace/using-workspace.md#enabling-experimental-mode) to let Workspace build personalized learning paths and enroll you in courses.

In Workspace, describe what you want to learn and it builds a personalized course path aligned to your role and goals, so you get exactly the training you need.

Instead of browsing 100+ courses across 11 learning paths in [Nexthink Learn](https://learn.nexthink.com), you describe a topic or problem you want to solve, and Workspace returns a sequenced path with direct course links. It shows which courses you've already completed or started, and can enroll you in the remaining courses without leaving Workspace.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FzeWuRz6baJeeoZbDQSol%2Fimage.png?alt=media&amp;token=b913cf6e-d1ea-482b-94e7-950dc059d54c" alt=""><figcaption></figcaption></figure>

## What you'll get

* A learning path tailored to what you asked about, sequenced from foundational to advanced
* Course URLs linked directly to Learn
* Your enrollment status for each course: **(already completed)**, **(already started)**, or **(currently enrolled)**
* One-step enrollment in courses you haven't taken yet

## How to use it

### Step 1: Describe what you want to learn

In Workspace, ask Workspace about a topic. For example:

* "I want to learn more about Nexthink"
* "Show me courses about campaigns"
* "Teach me NQL"
* "How do I troubleshoot devices?"

### Step 2: Provide more detail if asked

If your question is generic (like: I want to learn about Nexthink), Workspace asks you to be more specific: Is there a specific problem you're trying to solve, or would you like to start with the Nexthink foundations?

Answer with a concrete topic or problem. For example:

* I want to learn how to configure campaigns.
* I need to troubleshoot devices faster.
* I want to set up Remote Actions.

### Step 3: Review the learning path

Workspace returns a path with:

* Course titles (linked to Learn)
* A one-sentence reason why each course is included
* Your status for each course: **(already completed)**, **(already started)**, or **(currently enrolled)**
* A summary line if you're already in some of the courses

Workspace also asks: Does this work for you, or would you like it adjusted?

Your options:

* Accept the path as-is and enroll
* Ask for a more focused version (drop advanced/supplementary courses)
* Ask to extend to the broader topic (see more courses)

### Step 4: Enroll

If you want to be enrolled in the courses you haven't completed yet, click **Enroll me**.

Workspace confirms the exact courses first: I'll enroll you in Course 1, Course 2, Course 3 — OK?

After you confirm, you're enrolled. The courses appear on your Learn **My Progress** page.

## Prerequisites

* Access to Workspace
* An active Learn account (same login as your Nexthink account)
* Enable Experimental mode to let Workspace build personalized learning paths and enroll you in courses.


---

# 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://docs.nexthink.com/user-guide/search-and-workspace/using-workspace/getting-a-personalized-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.
