# Alternative Approach
## Overview
Instead of using the single DataLoader.ipynb, you can use three separate notebooks for more focused data loading. This is useful when:
* Different team members handle different phases
* You want to re-run only one phase
* You prefer smaller, focused notebooks
## **The Three Notebooks**
Notebook
Phases
What It Does
1_TenantAndCommonMaster.ipynb
Phase 1 & 3
Tenant + Departments + Complaint Types
2_BoundarySetup.ipynb
Phase 2
Administrative boundaries
3_EmployeeOnboarding.ipynb
Phase 4
Employee creation
 
## **Execution Order**
Important: You MUST run notebooks in this order:
**Understanding Tenants**
CMS uses a hierarchical tenant structure:
* **Root Tenant (State)** – The top-level administrative entity representing a State. This is created during system deployment.
* **City Tenant (ULB)** – Urban Local Bodies created under the root tenant. Each city has its own tenant ID in the format: `.` (e.g., statea.citya)
All city tenants inherit configuration from their parent root tenant.
## Login Details - For Initial Access
**Root Tenant (State-level):** The root tenant is the top-level administrative entity (typically a State) under which all city/ULB tenants are created.
* Username: SUPERADMIN
* Password: eGov\@123
* Tenant ID: statea
**City Tenant (ULB-level):** City tenants are created under the root tenant and represent individual Urban Local Bodies.
* Username: CITYADMIN
* Password: eGov\@123
* Tenant ID: statea.citya
---
# Agent Instructions: 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:
```
GET https://docs.digit.org/complaints-management/complaints-resolution-v2.10/deploy/setup/production-setup/deploy-complaints-management/alternative-approach.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.