> 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/concepts/security.md).

# Security

## Role-based Access and Communications

The diagram below shows the differences between Conducttr roles. Note that when designing an exercise the term "role" refers to the player's utilisation during the exercise.

Privileged access requires 2FA. Standard access for exercise participants can have a variety of registration and login options including 2FA through to anonymous click-to-play access for open exercises.

Content published by inject from a Master Events List can be directed to certain players and not others based on their team, role, group and position.

<img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FeIHe85ryMpQcac8T2Cwm%2Ffile.excalidraw.svg?alt=media&amp;token=959d1f6c-0faa-4a23-bf9f-9b27cfe854fc" alt="" class="gitbook-drawing">

For Worlds clients there is an additional role which is that of World Admin. The World Admin can create business units (referred to by Conducttr as "hubs") and assign facilitators with permissions to access exercises published to their hub.

<img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2F3QEoM49M5ldNAZ74Sg9q%2Ffile.excalidraw.svg?alt=media&amp;token=63853b10-dcbb-46f9-91c6-0c18b2df8f08" alt="" class="gitbook-drawing">


---

# 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/concepts/security.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.
