> 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.md).

# Configuring the System

This section outlines the System Administration functions including managing users, positions, lookup items and other system functions.

## Overview

System Administration includes maintenance tasks for the system and adding users.

### System Administration Positions

System Administrators can have different positions with different levels of access. Please ensure you're on duty with the right position for the type of tasks you wish to undertake.

These are as follows:

<table><thead><tr><th width="334">Position</th><th>Permissions overview</th></tr></thead><tbody><tr><td><strong>System Admin &#x26; Data Entry</strong></td><td><ul><li>Access all and configure registers in the the System Administration area</li></ul></td></tr><tr><td><strong>System Admin - User management</strong></td><td><ul><li>Access Positions and Position Groups</li><li>View, add and edit Contacts type of Users</li></ul></td></tr></tbody></table>

## Access

The System menu is available to System Administrators via the [user menu](/concepts-and-fundamentals/on-a-computer/your-user-profile-and-duties.md).

If you aren't on duty with a System Administration position you will not see the System Administration area.

You will only see the System Administration link under System if you are on duty with a [System Administration position](#system-administration-positions).

<figure><img src="https://3923904090-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNy7IznbrPLUq6GJDDQDk%2Fuploads%2F3eQVTXLt2gMmYnXGvhtE%2Fimage.png?alt=media&amp;token=781e26dc-300f-46c1-beea-bc437e04316a" alt=""><figcaption><p>System section of the User menu</p></figcaption></figure>

{% hint style="info" %}
You will need a System Administrator position in your user account to access System Administration. This can only be added by another administrator. Contact your administrator first if you need this permission. For information security reasons, the Datalink Help Desk requires authorisation to perform this task.
{% endhint %}

{% hint style="info" %}
In order to perform System Administration functions you must be on duty to at least one event with a System Administration position. If you aren't you may be able to access System Administration areas but not perform functions.
{% endhint %}

## System Administration Settings

The System Administration menu provides access to registers other users cannot access.

{% hint style="info" %}
To add new items into these registers, use the New Item button within each register.
{% endhint %}

{% hint style="info" %}
Users are managed via the Operations module's [Contacts](broken://pages/rGTm9vyCA4TordShc02E) register not through the System Administration menu.

Events is another system register that is [navigated to](/concepts-and-fundamentals/on-a-computer/working-with-events.md) and [managed separately](/system-administration/managing-events.md) through the Events menu.
{% endhint %}

The following sections outline the System Administration registers available for use in your system along with their key administration functions.


---

# 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.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.
