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

# Sign In

Sign-In to DIGIT Complaint Management Admin Console

## Overview

This is the sign-in page for the Configurator — the first screen you'll see when you go to set up or manage your city's account. 

## Steps

{% stepper %}
{% step %}

### Get an admin username

You cannot sign yourself up as an admin. Someone who is already an admin has to create your account for you. How this works depends on whether your city/state is brand new to the system or already set up.

* **Scenario 1: Your account is being set up for the first time**

When the system is first set up for a new state or city, it automatically creates one shared login for whoever is setting things up:

* State level: Username <mark style="color:$primary;">ADMIN</mark> and Password <mark style="color:$primary;">eGov\@123</mark>
* City level: Username <mark style="color:$primary;">CITYADMIN</mark> and Password <mark style="color:$primary;">eGov\@123</mark>

This is a temporary, shared login - not personal to any individual. Once things are up and running, the person using it should create proper, individual accounts for each real admin.&#x20;

* **Scenario 2: You are joining a system that’s already set up**

If your organisation already uses the system, an existing admin needs to create your account. They'll ask for basic details: your name, mobile number, department, and job title. They'll also choose what kind of admin access you get:

* Full admin access (can manage everything) - this is called <mark style="color:$primary;">SUPERUSER</mark>
* Master data admin access (can manage things like departments, complaint types, etc.) - this is called <mark style="color:$primary;">MDMS\_ADMIN</mark>
  {% endstep %}
  {% endstepper %}

<div align="left"><img src="https://2437503360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxNs29HvQfLFAPZCcDd7D%2Fuploads%2FRslp8XjFAmJ5ScjjuSuP%2Funknown.png?alt=media&amp;token=83425ae1-5ab6-4378-be3b-802ea8f16965" alt="" height="391" width="624"></div>

Here's an example of a completed sign-in: username, password, and the tenant filled in. Once you click Sign In, if this is your first time and your city hasn't been set up yet, you'll be taken straight into the onboarding wizard, starting at Phase 1: Tenant & Branding — the first step in setting up your city, covered in the next section.


---

# 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-onboarding-guide/sign-in.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.