> 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/deploy/setup/production-setup/deploy-complaints-management/unified-approach/1.-login-and-add-tenant.md).

# 1. Login & Add Tenant

## Overview

This step connects the notebook to your CMS environment. It also creates your first **root tenant** (top-level tenant).

### You’ll need

* A running data loader notebook for CMS.
* Default admin credentials from your deployment.
* Your tenant identifiers (example: state `pg`, city `pg.citya`).

### 1.1 Login

Run the `login()` cell. Use an admin user that has `SUPERUSER`.

### 1.2 Create a root tenant

Run the `create_tenant()` cell. Fill these fields:

* **Tenant code / tenantId**: short, unique code. Example: `pg`.
* **Name**: internal name. Example: `Punjab`.
* **Display name**: UI label. Example: `Government of Punjab`.
* **Users**: at least one admin user for the new tenant.

Roles matter for what you can do next. Minimum: `SUPERUSER` for creating root tenants. Recommended for end-to-end testing and demos:

```
["SUPERUSER", "EMPLOYEE", "CSR", "GRO", "DGRO", "PGR_LME", "PGR_VIEWER", "CITIZEN"]
```

<figure><img src="/files/ZLjpQ3fsyS7Yls5jbWIl" alt=""><figcaption><p>Notebook cells for login and tenant creation.</p></figcaption></figure>

### 1.3 Run the cells

Press `Shift + Enter`. Run `login()` first. Then run `create_tenant()`.

### 1.4 Verify results

If all goes well, you should see the following notifications.

<div align="left"><figure><img src="/files/QzvKCQVse2LKoxdt63tJ" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/AAnGXALqUigj2lHWZWXy" alt=""><figcaption></figcaption></figure></div>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/complaints-management/deploy/setup/production-setup/deploy-complaints-management/unified-approach/1.-login-and-add-tenant.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.