> 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/account-creation-and-onboarding-guide/glossary.md).

# Glossary

Below are the terms used in this guide and in the context of the DIGIT Complaint Management System.&#x20;

<table><thead><tr><th width="157.3125">Term</th><th>What it means</th></tr></thead><tbody><tr><td>Account</td><td>Your organisation's own space in DIGIT Complaint Management, for example a county government or a ministry. Everything you set up during onboarding belongs to your account. </td></tr><tr><td>Account admin</td><td>The person who manages an account. Whoever creates the account becomes its first account admin. You can add and invite more admins.</td></tr><tr><td>Account code</td><td>A short, unique ID for your account made of capital letters, numbers and hyphens, for example KE-BOMET-COUNTY-GOVERNMENT. It cannot be shared with any other account.<br><br>This usually cannot be changed once saved.</td></tr><tr><td>Account URL</td><td>A short web-friendly name for your account made of lowercase letters, numbers and hyphens, for example bomet-county-government. It must be unique.<br><br>This usually cannot be changed once saved.</td></tr><tr><td>Area</td><td>One place in your geography, for example "Bomet East" or "Silibwet Township". The system also calls an area a "boundary".</td></tr><tr><td>Bulk upload</td><td>Adding many records at once by uploading a filled-in spreadsheet, instead of typing them one at a time.</td></tr><tr><td>Code</td><td><p>A short, unique ID that the system uses for unique identification of a record (an area, department, designation or employee).</p><p><br></p><p>People see the name; the system uses the code. </p><p><br></p><p>This usually cannot be changed once saved.</p></td></tr><tr><td>Complaint category</td><td>The broad type of problem a citizen chooses when reporting, for example Street lighting.</td></tr><tr><td>Complaint Resolver</td><td>The role for the person who actually fixes the problem on the ground and closes the complaint.<br><br>Its system code is PGR_LME.</td></tr><tr><td>Department</td><td>A team or office that complaints are sent to, for example Roads and Infrastructure or Water and Sanitation.</td></tr><tr><td>Designation</td><td>An employee’s job title, for example Ward Officer or Engineer.</td></tr><tr><td>DGRO (Department GRO)</td><td>A department-level version of the GRO role. It does not count as the GRO a department needs to finish setup.</td></tr><tr><td>Draft</td><td>Changes you have made that are not yet saved to the system.</td></tr><tr><td>Employee code</td><td>A unique ID for each staff member, suggested automatically as EMP_0002, EMP_0003 and so on. It cannot be changed later for a particular employee.</td></tr><tr><td>Geography</td><td>The places your organisation serves, such as the county and the wards inside it, and how those places fit inside each other.</td></tr><tr><td>Geographic Boundary</td><td>The perimeter that encapsulates each unit of a geography - This may be for a country, and the geographic units under it such as County, State, Wards etc.  </td></tr><tr><td>Geographic Hierarchy </td><td>The order of levels of geography. Example, Country → County → Sub-County </td></tr><tr><td>GRO (Complaint Assessor)</td><td>The role for the person who receives new complaints for a department and assigns them to someone to fix.<br><br>GRO stands for Grievance Routing Officer. Every department that receives complaints needs at least one.</td></tr><tr><td>Hierarchy</td><td>The order of your levels from biggest to smallest, for example County → Sub-county → Ward. The top level is called the "root"; the bottom level is the "lowest" level.</td></tr><tr><td>Invitation</td><td>An email that gives a person access to your account. New people receive a link to set their password; people who already have an account see the invitation when they next sign in.</td></tr><tr><td>Jurisdiction</td><td>The areas where an employee is allowed to and accountable to work on complaints, for example one ward or the whole county.</td></tr><tr><td>Level</td><td>One layer of your geography, for example County, Sub-county or Ward. Every area belongs to exactly one level.</td></tr><tr><td>Logo</td><td>The small image that represents your organisation. It appears in the apps that citizens and employees use.</td></tr><tr><td>Management Console</td><td>The part of the system you use once the onboarding setup is finished, to make day-to-day changes. </td></tr><tr><td>Map outlines (GeoJSON)</td><td>An optional file that holds the real shape of each area so it can be drawn on a map. GeoJSON is a common file format for map shapes.</td></tr><tr><td>MB</td><td>Megabyte, a measure of file size. Most phone photos are 2 to 5 MB.</td></tr><tr><td>Onboarding</td><td>The guided set of five setup steps you complete after creating your account: Branding, Geography, Departments, Employees and Complaints Template.</td></tr><tr><td>Reserved word</td><td>A word the system keeps for its own use, such as "api", "citizen" or "employee". You cannot use it as your account URL.</td></tr><tr><td>Resolution time</td><td>Your own target for how long a complaint should take to fix. After this time, the complaint is shown as overdue. This is sometimes called the SLA (service level agreement) and this is set at a complaint category level. </td></tr><tr><td>Role</td><td>What a person is allowed to do in the system, for example assign complaints or resolve them. One person can have several roles.</td></tr><tr><td>Sign-in link</td><td>A one-time link sent to your email that signs you in without a password. It expires after 30 minutes and works only once.</td></tr><tr><td>Spreadsheet template</td><td>A ready-made Excel file with the right column headings. You download it, fill in your own rows, and upload it again.</td></tr><tr><td>Complaint Subcategory</td><td>A more specific problem inside a category, for example "Broken lamp" under Street lighting.</td></tr><tr><td>Theme</td><td>The main colour used across the citizen and employee apps. You pick one of three ready-made colour sets.</td></tr></tbody></table>

<br>


---

# 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/account-creation-and-onboarding-guide/glossary.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.
