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

# Onboarding

## Overview

Onboarding is a set of five setup stages that prepare your account for use. Once you finish them, you have your Complaint Management System up and running with the basic configurations. Citizens can start to report complaints, and your staff can start handling them.\
\
The complex granular configurations and your day-to-day changes can be done within the Management Console, which will appear after you are done with the following five stages of onboarding.

## Steps

Complete the steps below for onboarding your account.

<table><thead><tr><th width="152.40234375">Step</th><th width="408.08203125">What you do</th><th>Button on the home page</th></tr></thead><tbody><tr><td>1. Branding</td><td>Add your logo and choose the visual theme that will show up on the citizen and employee screens .</td><td>Set Up Branding</td></tr><tr><td>2. Geography</td><td>The places your account serves, such as the county and the wards inside it, and how those places fit inside each other.<br><br>These translate to the places a complaint is raised in and the jurisdiction that an employee serves, for example County → Sub-county → Ward.</td><td>Define Geography</td></tr><tr><td>3. Departments</td><td>These are the departments that exist in your organisation or entity.<br><br>Example, “Water and Sanitation Department”, “Electricity Department” etc</td><td>Add Departments</td></tr><tr><td>4. Employees</td><td>Add the people who handle complaints. They are assigned to a department set previously.</td><td>Add Employees</td></tr><tr><td>5. Complaints Template</td><td>Choose what citizens can report, who handles it and how fast.</td><td>Choose Template</td></tr></tbody></table>

Completion of these 5 stages marks the end of ‘onboarding’.

### Home page

After you create your account, you land on the Home page, "Let's set up your account". It shows:

* A Start here or Next step card with the next step, a short explanation and a button to start it.
* How many steps you have finished. Example: "2 of 5 completed".
* Learn the basics: short videos for each step. Select a video to watch.
* Take a tour: a quick introduction to the system. It opens by itself the first time you visit.

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2FB4Tk0mLI4PwC6OcPE4Sy%2Funknown.png?alt=media&amp;token=6a769326-8e15-48ab-962f-6d24b74eac9a" alt="" height="355" width="624"></div>

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2FGK4Hc1VpTaaHknqa4iqJ%2Funknown.png?alt=media&amp;token=880c0d38-77a9-4e9d-8835-2bb70d0c74ae" alt="" height="353" width="624"></div>

### Navigate your way around

* Left menu: your logo and name, a progress bar, and the list of steps. A tick means finished, a filled dot means "to do next", and an empty circle means locked.
* Documentation: opens help pages for the step you are on.
* Help: you can also press F1, or Ctrl and / together.
* Your initial (top right): your account details, workspace settings and Sign out.

### Move to the next step

1. When you finish a step, select Save and continue.
2. If something is missing, you will see "Not complete yet" and what is needed. Make edits, fix it, then Save to proceed.

<table><thead><tr><th width="195.62109375">Step</th><th>What is needed before you can continue</th></tr></thead><tbody><tr><td>Branding</td><td>A saved logo. You can skip this and come back later. These options are available in the Management console to change after onboarding as well.</td></tr><tr><td>Geography</td><td>At least two levels of places, for example counties and the wards inside them.</td></tr><tr><td>Departments</td><td>At least one department and at least one job title (Designation).</td></tr><tr><td>Employees</td><td>At least one employee besides yourself.</td></tr><tr><td>Complaints Template</td><td>At least one complaint type with a department and a resolution time, and a complaint assessor (GRO- Grievance Routing Officer) in every department that has been set up to receive complaints.</td></tr></tbody></table>

### Finish setup

On the last step, select Finish setup. This marks the end of ‘onboarding’.  You are taken to the management area/console, where you make any later changes. From then on, your account always opens there.

{% hint style="info" %}
**Important:** If you see "Your role has view-only access", you can look at the step but not change it. Ask your account admin for access.
{% 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/onboarding.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.
