Alternative Approach

Alternative Method: Using Three Separate Notebooks

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

CRS 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: <state-code>.<city-code> (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