Skip to main content

Chapter 1: Organisation Profile Setup

πŸ“˜Β Chapter 1 β€” Organisation Profile Setup

Customer Onboarding Guide β†’ i2i Core Documentation

The My Organisation section is the foundation of every customer setup on the i2i Core platform. Before enabling modules like Billing, CRM, Inventory, Network, or Partner Management, it is essential to configure all organisation details correctly.

This chapter provides detailed instructions on updating every section visible on the My Organisation page, including branding, URLs, GST configuration, invoice settings, bank details, support information, login settings, and logos.


🧭 1. How to Access Organisation Settings

After logging into the Admin Portal:

System  β†’  Settings β†’  My Organisation

This opens the complete organisation profile page.


πŸ›οΈ 2. Organisation Basic Details

This section defines the legal identity and primary business details of the organisation.

Fields Explained
Field Description
Organisation Name Legal name registered for business operations. Appears on invoices, notifications, and system reports.
GSTIN 15-digit GST identification number for Indian compliance. Mandatory for GST-enabled billing.
Address Registered address (full address must be accurate for invoicing).
Pincode Postal code associated with the organisation's address.
Taluka Sub-district / tehsil for regional classification.
City City where the organisation is located.
State State of registration.
Usage
  • Appears on customer invoices

  • Used in financial reports

  • Validates tax configuration

  • Branding across admin, partner, and customer portals


🧾 3. Organisation State GSTIN Configuration

Some organisations operate in multiple states and require state-wise GST mapping.

Purpose
  • Allows state-based tax calculations

  • Required for multi-city ISPs

  • Useful when invoices must display different GSTINs for different states

Fields
Field Description
State Code Official GST state code (e.g., 27 for Maharashtra)
State Name Name of the operating state
GSTIN State-specific GST number
Logo Invoice logo specific to that state (optional)
QR Code UPI/QR code for quick payments
Created On / Created By Auto-filled audit details
Actions
  • Click Add Configuration to create a new entry

  • Upload state-wise logo or QR code if applicable


🌐 4. Organisation URL Configuration

This section defines prefixes used to generate admin, partner, and customer portal URLs.

Fields Explained
Field Description
Organisation Prefix Prefix slug used for internal routing. Example: admin.
Admin URL URL for logging into the admin portal (e.g.,Β https://admin.domain.com).
Partner Prefix Prefix for reseller/partner portal. Example: reseller.
Partner URL URL for partners to access dashboards (e.g., https://reseller.domain.com).
Customer Prefix Prefix for customer self-care portal. Example: customer.
Customer URL URL for customers to log in (e.g., https://customer.domain.com).
Impact
  • Controls routing for all portals

  • Must be set correctly for login modules to function

  • Incorrect configuration may break links used in SMS/email notifications


πŸ”— 5. System URL Configuration

Defines module-specific URLs (payment, renewal, hotspot, KYC, etc.)

Fields Explained
Field Description
Payment URL URL for payment gateway portal.
Invoice URL Direct URL to view customer invoices.
Customer Renewal URL URL used in SMS/email reminders for renewals.
Guest WiFi URL Login URL for guest hotspot authentication.
eKYC URL For Aadhaar-based onboarding (if enabled).
Lead Payment URL Payment link for non-customer leads.
Hotspot URL Login URL for hotspot/captive portal.
Importance
  • Payment systems depend on these URLs

  • Customer renewal notifications use the renewal link

  • Hotspot login must point to the correct captive portal


πŸ“œ 6. Privacy Policy URL Configuration

These URLs are required for:

  • Customer portal footer

  • Signup pages

  • Payment gateway documentation

  • TRAI/Indian regulatory compliance

Fields
Policy Type Description
Privacy Policy Must link to a publicly accessible privacy policy page.
Terms & Conditions Customer usage policy must be displayed during signup/onboarding.
Cancellation and Refund Policy required for digital payments.
Shipping and Delivery Not applicable to ISP, but mandatory for payment gateways.
Contact Us Public contact information.

🧾 7. Organisation Invoice Details

These details appear on every invoice generated.

Fields Explained
Field Description
Organisation Email Email displayed on invoices for support.
Mobile No Customer helpline number.
Invoice Address Registered billing address (auto-filled from org details).
State State used for tax slabs.
Invoice Pattern Custom invoice numbering pattern (e.g., B2BINV/{yy}/{6d}).
MSME Whether the business is registered as an MSME.
  • Appears on top of invoices

  • Recommended: 700px width PNG

  • Upload via Choose Invoice Logo


🏦 8. Invoice Bank Details

Bank information is printed on invoices for offline payments.

Fields
Field Description
Bank Name Name of the bank used for business transactions.
Account No. Customer payment account.
IFSC Code Required for NEFT/IMPS transfers.
PAN No. Organisation PAN number.
Branch Bank branch (if applicable).
QR Code Upload the UPI QR for quick payment via Apps.

πŸ‘₯ 9. Partner Portal Login Settings

Controls how partners log into their portal.

Fields
Field Description
Partner 2FA Enable/disable 2-factor authentication.
Login SMS Gateway SMS service used to send OTP/login messages.
Login SMS Template Template for partner login messages.
Login Email Gateway Gateway to send login emails.

πŸ‘€ 10. Customer Portal Login Settings

Controls how customers access their self-care portal.

Fields
Field Description
Customer Portal Login Page Authentication method (Username & Password / Mobile OTP / Email OTP).
Login SMS Gateway SMS provider for OTP messages.
Login SMS Template Message template for OTP login (e.g., MobileVerification).

🎫 11. Ticket Template

Used for auto-generated ticket messages.

Fields
Field Description
Ticket Template Template used when a ticket is created through the customer portal, email, WhatsApp, or CRM.

πŸ“„ 12. Terms & Conditions

  • Customer portal

  • Signup screens

  • Payment gateway pages

  • Receipts

Fields
Field Description
Terms & Conditions Custom legal text.
Customer Care Number Shown with T&C for support.

πŸ“ž 13. Support Contacts

These details appear in:

  • Customer portal

  • Partner portal

  • Email notifications

  • PDF invoices

  • Auto-ticket acknowledgements

Support Types
  1. Customer Support

  2. Technical Support

  3. Billing Support

  4. Appellate Authority (TRAI Requirement)

Each support block contains:
  • Phone

  • Email

  • Availability (timings)

  • URL (optional link to support portal)


πŸ–ΌοΈ 14. Branding & Logos

This section allows uploading multiple logos, each serving a different purpose.

Logos Available
Logo Type Usage
Partner Support Info Logo Shown in partner tickets, partner emails.
Organisation Logo Universal brand identity used across all modules.
Admin Portal Logo Appears on the admin login page and the header.
Partner Portal Logo Used for all partner views.
Customer Portal Logo Primary logo for the customer app/portal.
Customer Portal Thumbnail Logo Shown in browser tab/app icon.
Logo Requirements
  • PNG preferred

  • Transparent background recommended

  • Horizontal/landscape format

  • 500–1000px width for best results


πŸ“Œ 15. Summary

By completing this full Organisation Setup:

  • All portals (Admin, Partner, Customer) display correct branding

  • Invoices are generated accurately with GST and bank details

  • Support contact details are visible to customers

  • URLs route correctly for login, payments, and renewals

  • Legal compliance (TRAI + GST) is achieved

  • All other modules can now be configured safely


Β