Help
LeadCaptureMT Online Help

Project Documentation and Help Manual

Complete operating guide for Super Admin, Client Admin, agents, team leaders and vendors. This page is available online inside the project at /help.

No matching help section found.

1. Overview

LeadCaptureMT is a URL based multi-tenant lead capture and project processing system for solar project work. It supports lead capture, client users, vendor assignment, required document uploads, vendor progress tracking, product details and lead PDF generation.

This online help is inside the project and can be opened from the menu or directly at /help.

2. Portals and login URLs

PortalURL PatternUsed By
Super Admin/admin/account/loginSystem owner / master administrator
Client/client/{client}/account/loginClient Admin, Team Leader, Agent
Vendor/vendor/{client}/account/loginVendor users assigned to projects
Help/helpAll users

Replace {client} with the client slug, for example client1.

3. Installation and first setup

  1. Publish the ASP.NET Core project to IIS or run it from Visual Studio.
  2. Configure the SQL Server connection in LeadCaptureMT.Web/appsettings.json.
  3. Run Db_Create_LeadCaptureDb.sql on SQL Server.
  4. For existing installations, run Db_Add_LeadSolarFields.sql and Db_Add_VendorManagementAndUploads.sql once.
  5. Give the application write permission to wwwroot/uploads.
  6. Open /admin/account/login and complete client setup.
Do not run update scripts repeatedly unless they are written as safe ALTER scripts. Keep a database backup before applying changes to production.

4. Super Admin guide

Super Admin controls master setup across all clients.

  • Create and activate clients.
  • Manage master features.
  • Enable or disable features for each client.
  • Create or edit client users where required.
  • Change the Super Admin password.

Recommended first setup flow: create client, enable features, create Client Admin, then share the client login URL.

5. Client Admin guide

Client Admin manages daily operations for one client.

  • Create and manage leads.
  • Manage lead statuses, users, properties and vendors.
  • Assign a vendor to a lead.
  • Upload required solar documents.
  • View vendor progress and vendor product details.
  • Export leads to CSV and generate lead PDF.

6. Lead management

The Lead form contains contact details, project details, pricing, payment and vendor assignment.

Contact and consumer fields
  • Lead name, mobile, WhatsApp, email, city and pincode.
  • Consumer name, consumer number and consumer type.
  • Status, assigned user and next follow-up.
Solar project fields
  • Project floor, roof type, project type and phase.
  • Project price, discount and net price.
  • Payment type: cash, loan or both.
  • Select vendor from Vendor Master.

7. Required solar documents

Lead Create/Edit includes required document uploads for solar processing.

  1. PAN card scan copy.
  2. Electricity bill scan copy.
  3. Self photo scan copy.
  4. Cancel cheque or bank passbook first page scan copy.
  5. ITR upload for loan above 2 lakh.
Assigned vendors can view and download uploaded lead documents, but only for projects assigned to that vendor.

8. Lead PDF

The Lead PDF is a complete printable record. It includes lead fields, consumer details, project/pricing/payment details, status, uploaded documents, lead actions, assignment audit, vendor progress and product details.

Use the PDF option from the Lead list or Lead edit screen.

9. Vendor master

Client Admin can open Vendors from the client panel. Vendor Master stores vendor name, contact person, mobile, email, address/details, username, password and active status.

Vendor login URL format: /vendor/{client}/account/login.

Only active vendors can log in. Passwords are stored as one-way hashes and cannot be decrypted; reset the password if forgotten.

10. Vendor portal

After login, a vendor sees only assigned projects. The project list shows lead number, lead generation date, customer details, project details, project start date, project complete date and progress count.

Inside a project, the vendor can save project dates, download uploaded lead documents, submit progress and fill product details.

11. Vendor work progress

For each step, the vendor must select a progress date. Date validation is done both in the browser and on the server.

#StepUpload
1Registration and subsidy amount certificate generationPDF
2Slip of paid payment amount of customerPDF
3Product dispatch to customerOptional PDF/JPG/PNG
4Basement work or concrete workOptional PDF/JPG/PNG
5Structures workOptional PDF/JPG/PNG
6Earthing work 3 pointOptional PDF/JPG/PNG
7Panel settingOptional PDF/JPG/PNG
8Inverter installingOptional PDF/JPG/PNG
9WiringOptional PDF/JPG/PNG
10Solar meterOptional PDF/JPG/PNG
11Net meteringOptional PDF/JPG/PNG
12Subsidy amount to customerOptional PDF/JPG/PNG
13Proper monitoring and provide remarksOptional PDF/JPG/PNG

12. Product details

Vendor fills power rating/type and company for Solar Panel, Inverter, Cable and Structure. Client users can view these details from Lead Edit and Lead PDF.

13. Users and access control

  • Super Admin handles system-wide setup.
  • Client Admin handles client-level setup and operations.
  • Team Leader and Agent access leads according to assigned visibility rules.
  • Vendor can access assigned projects only.
  • Vendor document download checks lead assignment before serving files.

14. Upload storage and backup

Uploaded files are stored under wwwroot/uploads. Include this folder in daily backup along with the SQL Server database.

  • wwwroot/uploads/lead-documents stores lead documents.
  • wwwroot/uploads/vendor-progress stores vendor progress files.
  • IIS application pool identity must have read/write permission.

15. Troubleshooting

Check correct portal URL, active status and password. Password hashes cannot be decrypted; reset the password if forgotten.

Check file type, file size, IIS request limit and write permission on wwwroot/uploads.

Open Lead Edit and confirm that the correct vendor is selected. Confirm vendor is active and using the correct client vendor URL.

Run the update SQL scripts once on the existing database: Db_Add_LeadSolarFields.sql and Db_Add_VendorManagementAndUploads.sql.

16. Deployment notes

  • Target framework: .NET 8.
  • Hosting: IIS with ASP.NET Core Hosting Bundle installed.
  • Database: SQL Server Express or compatible SQL Server.
  • Connection string is configured in appsettings.json.
  • Static files must be enabled because help files, CSS and uploaded documents are served from wwwroot.

17. Quick operating flow

  1. Super Admin creates client and Client Admin.
  2. Client Admin creates users, statuses, properties and vendors.
  3. Agent or Client Admin creates a lead.
  4. Client Admin uploads required solar documents and assigns vendor.
  5. Vendor logs in and opens assigned project.
  6. Vendor enters dates, updates progress steps and fills product details.
  7. Client team reviews progress from Lead Edit and exports/prints Lead PDF.