> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/worlds/concept.md).
# Concept
This page provides an understanding of Conducttr Worlds as a concept.
Conducttr Worlds allows you to run hundreds of simultaneous team exercises without your active involvement - saving you time and effort and ensuring more people are trained each year. With Conducttr Worlds your Facilitators can run exercises independently and concurrently while you access performance metrics for centralised reporting.
In summary: Worlds is a way to scale up your exercising without increasing your workload.
## How it Works
A **World** is comprised of an **exercise library** and business entities (which we call "hubs")
**Hubs (representing business entities)** are the simulation spaces where the exercising takes place - Facilitators log into a Hub, select an exercise and run that exercise at a time of their choosing.
The **World Admin** decides which exercises are available to which Hub.
Exercises are uploaded to the World via the Editor.
## Core attributes - what they mean
{% tabs %}
{% tab title="World" %}
A World is an administrative domain consisting of:
* Exercise Library
* Hubs
{% endtab %}
{% tab title="Exercise Library" %}
A collection of slots where exercises have been uploaded from the Scenario Editor
{% endtab %}
{% tab title="Exercise" %}
The logic and content associated with a training session.
{% endtab %}
{% tab title="Session" %}
A session is a record of an Exercise run, so when Facilitators run an exercise they create an exercise session
{% endtab %}
{% endtabs %}
### Hubs related
{% tabs %}
{% tab title="Hubs" %}
* A simulation space where the exercising takes place - Facilitators log into a **Hub**, select an exercise and run that exercise at a time of their choosing.
* Hubs present exercises from the Exercise Library. If an organisation wants multiple exercise libraries then it needs additional Worlds.
* All Worlds will have at least one default Hub
{% endtab %}
{% endtabs %}
### Exercise management related
{% tabs %}
{% tab title="Facilitator" %}
A Facilitator is someone with no prior experience of Conducttr, who are able to run exercises without ever using the Scenario Editor.
See more on Facilitators [here](/worlds/concept/facilitators.md).
{% endtab %}
{% tab title="Administrator" %}
An Administrator is someone who holds the master copy of the exercise. This enables them to manage exercise availability, presentation, Facilitator access, and updates.
See more on Administrators [here](/worlds/concept/administrators.md).
{% endtab %}
{% tab title="Worlds Admin Terminal" %}
A dedicated web application with a unique URL for your organisation.
This is where the World Owner and Administrators log in and utilise privileged administration access to carry out a number of key duties, namely:
* Create Hubs for each entity (e.g. business units)
* Add facilitators to each Hub and manage them
* Publish and manage the exercises available for facilitators
* Notify facilitators when exercises have been added
* Download exercise reporting
{% endtab %}
{% tab title="Hub Management" %}
Hub management means choosing which exercises from the library are made available and who is allowed to run exercises from the Hub (i.e. giving permission to people to be Facilitators)
{% endtab %}
{% endtabs %}
---
# 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://helpdocs.conducttr.com/worlds/concept.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.