> 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/concepts-and-fundamentals/on-a-computer/using-the-datagrid.md).

# Using The Datagrid

All the data in the system is managed using the Datagrid, which is a central way to search, filter, and access your information.

## Overview

Registers store and manage data in the system and have a built in audit log to ensure that each and every action that changes the data is recorded.

A register's configuration defines the shape of its data, the forms used to collect its data, the relationships between data, plus the overall functionality and capabilities of the records such as whether they have maps, can relate to assets, support status transitions, have priority, support assignment, can be tagged, have escalation rules, as well as other behaviours or workflows.

General features of Registers include:​

* **View modes**
  * **Datagrid** – a list of items organised into columns to provide information on items specific to that register. The Datagrid includes access to the:
    * **Actions menu** - additional functions available in the register for bulk management of records (such as exporting, bulk editing or generating mail merge)
    * **Columns menu -** options for customising the datagrid columns and groupings
  * **Map** - a geo-spatial view of the items list including a visual map, markers, polygons and overlays (layers)
* **Search -** for refining the list by query or key words
* **Filters** - refine the list by status or preset query
* **Status** – indicates the current workflow progress of each item colour coded Status column
* **Links to Items** - usually blue coloured hyperlinks (such as the ID or Summary)​

Columns functions are available to further sort and group items to organise large amounts of information.


---

# 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/concepts-and-fundamentals/on-a-computer/using-the-datagrid.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.
