> For the complete documentation index, see [llms.txt](https://olab4.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olab4.gitbook.io/help/quick-notes.md).

# Quick Notes

## Overview

For those who are quite experienced with **OpenLabyrinth** v3, here are a few quick notes to get you started so you can poke around in the OLab4 interface. <br>

## Basic Navigation:  Player <--> Designer

The Player and the Designer are not well integrated yet. In future, this will be improved.&#x20;

The Player is kinda the boss, controls user access etc. The Designer will be the kid sister, doing what it is told (and arguing frequently).

<https://player.olab4.net/> -- takes you to the Player. If you have the right permissions, this is where you would also perform maintenance and admin stuff like add other users etc.

[https://designer.olab4.net/](https://designer.olab4.net/login) -- takes you to the Designer, where you can edit maps etc. There is not yet a nice clean link between the two.

The URL scheme is similar between the Player and the Designer. You can cheat and jump straight to the map that you want to play or edit by adding the map number to the URL.

## Working with the Player

Things should be fairly similar to OLab3. There is a cleaner list of playable maps, with better search and descriptions. You can search by name or map number.&#x20;

The map number in the URL works more or less as things did for OLab3.&#x20;

## Working with the Designer

There is a list of editable Maps. Again, you can search by map name or number.&#x20;

As a Superuser, you will be able to open and edit any of the maps.  <br>

{% hint style="danger" %}
We'd prefer that you do not mess with the ones marked as “Demo… something” in the title as they are examples we are building as how-to’s etc. Also please avoid messing with numbered cases: these are our prime examples.
{% endhint %}

If you are not a Superuser but just an **Author**, you will only have access to your own maps or to templates. If you are just a **Learner**, you will not be able to edit any maps. You will only be able to play certain maps.&#x20;

### Setting up your editing workspace

There are a couple of odd things that will make your life easier when editing and testing cases in OLab4.5:

1. Use a different web browser for the Player and the Designer e.g. Chrome and Firefox
2. If you have just saved some changes to your case in the Designer, in order to see them in action, you will need to Logout and then Login again in the Player (yes, even when it is launched in a different browser).&#x20;
3. On that note, it is a good habit to Logout from the Player every time. Do not just close that window.&#x20;

Welcome to the joys of cached browser data. For a more detailed explanation about this, check out [Cached browser data here in the Help guide](/help/advanced-topics/cached-browser-data.md).

### Create a Map&#x20;

You can create your own Maps – start with Create Manually, or Create from Template. The latter allows you to start with some easy design models. There are only a few templates so far.

The Designer has been simplified a lot. As many users always commented, the OLab3 authoring interface was really messy. It should now be somewhat cleaner. We have used a similar concept-map design – you can add Links and Nodes as before.&#x20;

You can add things like Questions and Files or images using the Object Picker.&#x20;

{% hint style="success" %}
Have a little poke around and give us feedback on what you find.  <br>
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://olab4.gitbook.io/help/quick-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.