> 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-not-for-publish/2.-add-new-root-tenant.md).

# 2. Add New Root Tenant

## Overview

<table><thead><tr><th width="137.89453125">What </th><th>Description</th></tr></thead><tbody><tr><td>Purpose</td><td>Add a new State-level tenant and load master data</td></tr><tr><td>Key Rule</td><td>You MUST re-authenticate after creating new tenant</td></tr></tbody></table>

## Process Flow

<figure><img src="/files/KUljCeiN5zpWoGirLbPp" alt=""><figcaption></figcaption></figure>

***

### Step 1: Authenticate Existing Tenant

<table><thead><tr><th width="229.765625">Field</th><th>Example</th></tr></thead><tbody><tr><td>Gateway URL</td><td><a href="https://unified-dev.digit.org">https://unified-dev.digit.org</a></td></tr><tr><td>Username</td><td>MDMSADMIN</td></tr><tr><td>Password</td><td>********</td></tr><tr><td>Tenant ID</td><td>pg (existing tenant)</td></tr></tbody></table>

Click "🔐 Authenticate" → Verify success message

![](/files/Fpv1lnLXBxVwXRqHI2P3)

***

### Step 2: Create New Root Tenant

Fill the new tenant form:

<table><thead><tr><th width="253.10546875">Field</th><th>Example</th></tr></thead><tbody><tr><td>Tenant Code*</td><td>mh</td></tr><tr><td>Tenant Display Name*</td><td>Maharashtra</td></tr><tr><td>Tenant Type*</td><td>State</td></tr><tr><td>Logo URL*</td><td><a href="https://example.com/logo.png">https://example.com/logo.png</a></td></tr></tbody></table>

Click “ Create Root Tenant" → Verify tenant created

***

![](/files/pHNoTE00QU70lMZExj8h)

### Step 3: Re-Authenticate with New Tenant ⚠️

CRITICAL: You MUST re-authenticate before loading data!

Go back to the Authentication section and change:

<table><thead><tr><th width="301.8984375">Field</th><th>Change</th></tr></thead><tbody><tr><td>Tenant ID</td><td>pg → mh</td></tr></tbody></table>

Click " Authenticate" → Verify it shows: Tenant: mh

![](/files/pnDg0kit5o83R8OOFaCY)

***

### Step 4: Load Master Data

Run all phases for the new tenant:

<table><thead><tr><th width="149.95703125">Phase</th><th width="259.16015625">What to load</th><th>Target tenant</th></tr></thead><tbody><tr><td>Phase 1</td><td>City Tenants + Branding</td><td>mh</td></tr><tr><td>Phase 2</td><td>Boundaries</td><td>mh.mumbai, mh.pune</td></tr><tr><td>Phase 3</td><td>Departments, Complaints</td><td>mh.mumbai, mh.pune</td></tr><tr><td>Phase 4</td><td>Employees</td><td>mh.mumbai, mh.pune</td></tr></tbody></table>

***

## Common Errors

#### Key Reminder

⚠️ ALWAYS RE-AUTHENTICATE AFTER CREATING A NEW TENANT

&#x20;   Old: Tenant ID = pg

&#x20;   New: Tenant ID = mh  ← Change this before loading data!<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 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-not-for-publish/2.-add-new-root-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.