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

# Departments

## Overview

These are the departments that exist in your organisation or entity. Examples: “Water and Sanitation Department”, “Electricity Department”, etc.  In this step, you also add designations, which are the job titles your staff hold. Example: Ward Officer.

{% hint style="info" %}
**Remember:** You need at least one department and at least one designation to continue. Every employee you add later must belong to a department and hold a designation.
{% endhint %}

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2Fibo33h08n0L62Jv5g0AO%2Funknown.png?alt=media&amp;token=d6f4d222-befe-4120-bf5f-96d80008c399" alt="" height="391" width="624"></div>

## Steps

### Step 1. Add departments one at a time

1. Select Create manually (or Add department if you already have some).
2. Type the Department name. Example: Roads and Infrastructure.
3. A Department code is suggested from the name. Example: ROADS\_AND\_INFRASTRUCTURE. You can change it. This is used by the system to identify these departments.
4. Select Add department.

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2Fa6iPwRHf8e44jAhHKkNc%2Funknown.png?alt=media&amp;token=5da3ad03-8339-4b5c-a048-0604dcc9435b" alt="" height="391" width="624"></div>

### Step 2. Add designations (job titles)

1. Under Designations, select Add designation.
2. Type the Designation name. Example: Ward Officer, and check the suggested code. The code is used by the system to identify these designations.
3. Optional: tick the departments where this designation is used.
4. Select Add designation.
5. After adding the designation, we map it to all the departments that may hold employees with this designation.

<table><thead><tr><th width="135.14453125">Field</th><th>Note</th></tr></thead><tbody><tr><td>Name</td><td>Required. Under 100 characters.</td></tr><tr><td>Code</td><td>Required. Capital letters, numbers and underscores (_) only, for example WARD_OFFICER. Must not already be used. Cannot be changed once saved.</td></tr></tbody></table>

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2F3P4wZQmlAWU8bbt99QUW%2Funknown.png?alt=media&amp;token=c156a530-88eb-483e-bb69-dc4a9d109975" alt="" height="391" width="624"></div>

### Step 3. Add many at once (bulk upload)

1. Select Bulk upload, then Download template.
2. The file has two sheets: Department and Designation. Fill in one row for each.
3. Select Choose a file and pick your filled-in file.
4. Check the summary. Example: "3 departments and 5 designations", and any problems listed by row.
5. Select Bring them in.

<table><thead><tr><th width="147.1875">Sheet</th><th width="334.95703125">Columns</th><th>Example</th></tr></thead><tbody><tr><td>Department</td><td>code, name, active</td><td>WORKS, Public Works, true</td></tr><tr><td>Designation</td><td>code, name, description, department, active</td><td>INSPECTOR, Inspector, Senior Inspector, WORKS, true</td></tr></tbody></table>

{% hint style="info" %}
**Tip:** Use capital letters, numbers and underscores in codes, as you would when adding manually.

In the Designation sheet, the department column takes department codes. Separate several with commas. Example: ENV, WORKS.

Rows with active set to false are not imported. Codes you already have are skipped, so uploading the same file twice is safe.
{% endhint %}

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2FitD0ppEpZiwrWf2cAsIi%2Funknown.png?alt=media&amp;token=5ff673c9-2d88-494e-aeeb-53623e43db02" alt="" height="391" width="624"></div>

### Step 4. Edit or remove

* Select a row to edit its name. The code cannot be changed.
* Select Remove to stop using a department or designation.

{% hint style="info" %}
**Important:** Removing a department that has employees or complaint types linked to it can stop complaints from reaching anyone. Move those complaints first.
{% endhint %}


---

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