> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/wiki/infrastructure/moodle/moodle-user-tours.md).
# Moodle: User tours
A user tour is a short step-by-step guide that appears directly on a Moodle page. Each step highlights one element of the interface and explains it in a pop-up. User tours are useful for onboarding new course participants. The tour usually starts automatically on the first visit. Here is an example:
{% hint style="info" %}
**Requirement:** Only site administrators can create user tours (= you need admin rights).
{% endhint %}
## Finding the tours
Path: *Site administration > Appearance > User tours*
The "Tours" page lists all existing user tours and their status (enabled or not). The tours at the bottom of the list were created automatically by Moodle and are disabled (crossed-out eye icon).
Each tour is linked to one URL pattern. If you want tours on two different pages of a course (e.g. the course overview and the first lecture), you need two separate tours.
Since CorrelAid courses share a similar structure, you can reuse existing tours: duplicate them (two-squares icon), then edit them (pen icon).
## Adapting a duplicated tour
When you duplicate a tour, you need to adjust several things:
#### 1. Tour settings (klick the pen icon)
* **Name** and **Description**
* **Apply to URL match**, e.g. `/course/view.php?id=123`. `%` works as a wildcard.
* **Filters:** Course or Category, to show the tour only in specific courses
* **Tour is enabled:** check that it is switched on
This page lists all steps of the tour. You can edit, delete or add steps.
#### 2. Tour steps (click the tour name in the list)
This page lists all steps of the tour. You can edit, delete or add steps.
The screenshot below shows the edit form of the step "Inhaltsverzeichnis" (table of contents) in the tour "CorrelAid\_DatenKommunizieren\_BLOCK\_Kursübersicht".
* **Target type (Zieltyp):** Choose between "Display in middle of page", "Block" or "Selector" ("Auswahl" in the German interface, as shown in the screenshot). With "Selector", the step points to a page element defined by a CSS selector.
* **CSS selector:** Required if the target type is "Selector". It must identify a *unique* element on the page. To find it, right-click the element in the browser, choose "Inspect", select the element the pop-up should point to and look for an ID or class. This can be tricky. An AI chatbot can help, but test the result in the tour.
* **Title:** heading of the pop-up
* **Content:** explanation text
## Testing
You can test the tour as often as you like: click the question mark on the course page (in the bottom right corner) and select "Reset user tour on this page" ("Tour erneut anzeigen" in the German interface).
---
# 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.correlaid.org/wiki/infrastructure/moodle/moodle-user-tours.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.
