> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/access/configurator-management-guide.md).
# Configurator Management Guide
{% hint style="info" %}
## When and How to Use This Guide
To be used as a user manual and walk-through for day-to-day administration of an existing Tenant/Account using the DIGIT CMS Configurator's Management Console - the console you land in once onboarding is already complete.
**Key Note:** The example workflow used in this document is purely representative and may not reflect the default data shown when you onboard the DIGIT CMS Configurator.
**Representative Scenario:** In this document, the admin is a County ICT/e-Government Officer working for Bomet County Government, Kenya, onboarding Bomet County's own CMS tenant (root tenant “ke”, city tenant “ke.bomet” / “Bomet County”) for the first time - setting up its boundary hierarchy, departments (e.g. Health & Sanitation, Environment, Building & Roads), designations (e.g. Chief Sanitary Inspector, Accountant, Officer), complaint types, and its first batch of employees.
*Some screenshots in this guide may show data that deviates from this scenario (e.g. generic or placeholder values used for illustration) - treat these as illustrative rather than exact representations.*
{% endhint %}
## Overview
The Configurator is where you set up and manage everything about your complaint management system - without needing a developer. You use it once to onboard a new city, and then keep coming back to it to manage departments, staff, complaint types, notifications, and more, as things change.
It runs entirely in your browser and talks directly to the DIGIT platform, so there's nothing to install.
## Get Started
When you log in, choose the required Mode - [Onboarding](/complaints-management/access/configurator-onboarding-guide.md) or [Management](/complaints-management/access/configurator-management-guide.md) and your account (your city/organization). Everything you do afterwards applies only to that account.
If your account hasn't been set up yet, you will be guided through a one-time Onboarding Experience. Check out this [user guide for onboarding](/complaints-management/access/configurator-onboarding-guide.md).
If it's already set up, you will land in the [Management Console](/complaints-management/access/configurator-management-guide/management-admin-console.md), where you can edit anything at any time.
## Console Management
---
# 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.digit.org/complaints-management/access/configurator-management-guide.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.
