> 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/labs/free-apps/incident-reporter.md).
# Incident Reporter
The Incident Reporter lets you stage incidents on a live map during an exercise and turn them into published injects your participants actually receive.
\
You set up your map, personas, and key locations in advance, operators drop and post incidents during the exercise, and each report flows straight into Conducttr for participants to see and respond to.
### Getting started
Sign in and pick your project. **Admin** users can create projects; **Role-players** and **Players** join existing ones.
### Setup (Admin only)
Before the map is usable, an Admin (likely the Scenario Designer) configures the project:
* Add your **Conducttr API key**.
* Assign personas to the **Traffic**, **Weather**, and **Security** categories.
* Choose which **factions** appear on the map.
* Invite members as Admin, Role-player, or Player.
***
### The map
The map shows everything happening in the exercise:
* **Incident pins** — colour-coded by category, with impact rings sized by severity.
* **Persona dots** — live persona positions, coloured by faction.
* **Points of interest** — staff-only markers.
### Toolbar tools
* **Drop incident** — pick a category, then click-drag to set the location and impact radius.
* **Move** — select personas and draw a path to relocate them in Conducttr.
* **Select** — makes persona dots easy to click when they sit under an incident ring.
* **POI finder** — search and fly to a saved location.
* **Legends** — show or hide factions and categories to de-clutter the view.
### Reporting an incident
Dropping or clicking an incident opens the compose panel:
1. Choose who you're **posting as** (if the category has more than one persona).
2. Review the **auto-drafted report**, or write your own.
3. Set the **severity** and adjust the **impact radius**.
4. Pick the recipient **team, role, or position** and channel, then **publish**.
Publishing moves the persona to the incident location and sends the report with a map snapshot attached.
### Speaking as a persona
Click any persona dot to open the **Speak** panel and send a direct message as that persona — same recipient and channel options as a report, without creating an incident.
### Typical workflow
1. Admin (Dcenario Designer) sets up the project and assigns personas.
2. Operators monitor the map.
3. Drop an incident, review the report, set severity, choose recipients.
4. Publish — the persona moves and the message is sent.
5. Use **Move** to reposition personas as the scenario develops.
---
# 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://helpdocs.conducttr.com/labs/free-apps/incident-reporter.md?ask=&goal=
```
`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.