Begin onboarding for Channel, Installation, Service, and Structural partner roles.
Verification-first onboarding is preferred. DigiLocker and verified identity/business
data should be used wherever available. Manual entry remains only as fallback.
DigiLocker preferredPAN verification firstAadhaar verification firstGSTIN verification where applicableManual fallback only when needed
Recommended onboarding order
Select partner role
Complete identity and business verification
Upload professional proof and certificates
Use manual fallback only if verification cannot complete
Submit for backend review and approval
Complete agreement and e-sign after approval
1. Select partner role
Choose the primary role for this onboarding. Additional role-specific sections will
appear automatically.
Channel Partner
Lead sourcing, customer onboarding support, and market development.
Installation Partner
Site execution, manpower, technical delivery, and installation readiness.
Service Partner
Maintenance support, service call handling, and post-commissioning support.
Structural Partner
Structural review, certification support, and technical design assessment.
2. Primary verification
Use verified digital data first. Manual fields should be used only if these routes are
unavailable or incomplete.
Preferred
DigiLocker / digital document fetch
Use DigiLocker or other approved digital document retrieval routes when available.
This should remain the preferred way to fetch identity and supporting documents.
Current active route
Identity and business verification
Use PAN, Aadhaar, and GSTIN verification paths before asking the partner to type and
upload everything manually.
PAN verificationPending
Aadhaar verificationPending
GSTIN verificationOptional / Pending
3. Professional and technical proof
Add qualifications, experience summary, and role-specific certificates. This section
should focus on technical capability, not identity duplication.
Installation partner eligibility
Shown only for Installation Partner role.
Structural certification proof
Shown for Structural Partner role.
4. Manual fallback
Use this only if DigiLocker or verification routes are unavailable, incomplete, or need
temporary fallback for exceptional cases.
Open manual fallback section
5. Backend review
Final review remains with Rooftop Urja admin/backend team before approval and partner ID generation.
6. Partner agreement and e-sign
This section becomes active only after backend review is approved. Once approved, the
partner agreement can be generated and signed digitally.
Save draft while verification is in progress, or submit the onboarding once primary
verification and professional proof are completed.