> 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/system-administration/configuring-the-system/imports/register-items.md).
# Register Items
This page explains how to import Register items.
## Overview
The Imports facility allows you to import Register Items of different types in bulk.
Most register imports are in CSV formats.
This section outlines some of the common register items, if your organisation uses other registers that support importing, you may also find the instructions for those here.
Please refer to general instructions for importing:
{% content-ref url="/pages/QP6MVwI3qEAEvatbmPc3" %}
[Imports](/system-administration/configuring-the-system/imports.md)
{% endcontent-ref %}
## Importing Assets
### Import Process
Refer to the general instructions under [Imports](/system-administration/configuring-the-system/imports.md).
When importing Assets, in the **Type** field, choose *Register Items*.
For **Parsing Rule**, select one of the following :
### Using the Test Only option to check for errors
It is strongly encouraged to tick the *Test Only* option before you import your Register items to see if any errors are generated before actually doing a full import of your data. The Test Only option will display any error or success messages that would happen on a normal import but it will not import any assets. Once the *Test Only* option has no error messages you can then untick the Test Only checkbox and run your import.
Enter an optional comment for the Audit log and click the Import button to begin importing your Assets.
---
# 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/system-administration/configuring-the-system/imports/register-items.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.