> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/modules/overview.md).

# Overview

The following section outlines some of the key modules.

[Registers](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/using-the-datagrid.md), [Positions](https://docs.cw.crisisworks.com/system-administration/configuring-the-system/positions.md) and [Resources](broken://pages/rGPBlfWrNvfvFLAZUZhY) are grouped into and configured as a **Module**, which are typically found in the main menu navigation. Core modules are included with almost all implementations. Your package may include a combination of core modules and custom-built and configured modules.

Based on the configuration of each module, Register Items may be assigned to users and positions, and they may utilise resources and relate to assets. Additionally, Registers implement [workflows](https://docs.cw.crisisworks.com/concepts-and-fundamentals/concepts-and-fundamentals.md#workflow-and-communications) using combinations of status, priority, assignment, filters, escalations and [notifications](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/notifications-and-alerts.md), which help users to effectively manage the event.

The following sections outline some of the built in and custom modules included in the base system. Access to each of these modules will depend on your your position and duties as well as your organisation's configuration.

This following is a brief summary for each of the main system packages:

## Core Features

<table><thead><tr><th width="227">Module</th><th>Applications</th></tr></thead><tbody><tr><td><a href="https://docs.cw.crisisworks.com/modules/dashboard.md">Dashboard</a></td><td>The dashboard provides a near real-time feed of updates.</td></tr><tr><td><a href="https://docs.cw.crisisworks.com/system-administration/reporting.md">Reports</a></td><td>For producing formatted reports and extracting data. May contain (custom) reports specific your system's configuration.</td></tr><tr><td><a href="https://docs.cw.crisisworks.com/system-administration/configuring-the-system.md">System Administration</a></td><td>Only available to system administrators includes registers for configuring positions, templates, lookups and importing data.</td></tr><tr><td><a href="https://docs.cw.crisisworks.com/concepts-and-fundamentals/mobile-app.md">Mobile App</a></td><td>The mobile app provides users of Android or iOS an easy means of working in the field and includes additional device features for gathering evidence such as GPS, camera and audio.</td></tr></tbody></table>


---

# 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.cw.crisisworks.com/modules/overview.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.
