Admin
The SigmaDSA Admin section — Users, Roles, Loan Types, Lead Sources, Document Types, Notifications, WhatsApp Setup, Telegram Bots, Webhooks. Tenant-level configuration controlled by admin users.
The Admin section is where tenant owners configure the SigmaDSA application — who can log in, what they can do, what loan types you offer, where leads come from, what documents you collect, and how the system notifies users. Most users never visit Admin; tenant admins live here.
Sub-sections
The Admin sidebar is grouped into four categories:
Users & Roles
| Sub-section | What you configure |
|---|---|
| Users | Login accounts — username, password, email, role assignments, per-user permission overrides, deactivation. |
| Roles | Reusable permission bundles — Sales, Operations, Manager, Admin. Bulk-edit permissions at role level instead of per-user. |
Workflow Catalogue
| Sub-section | What you configure |
|---|---|
| Loan Types | Product catalogue — Home Loan, Personal Loan, Business Loan, etc. with per-product stages, codes, icons, colors. |
| Lead Sources | Where leads come from — Web, WhatsApp, Walk-in, Referral, Partner. Drives the Source filter on the Leads board and ROI reports. |
| Document Types | Document checklist categories — PAN, Aadhaar, Salary Slip, Bank Statement, ITR, GST. Mark which need AI analysis (OCR / BSA / GST parser). |
Notifications
| Sub-section | What you configure |
|---|---|
| Notifications | Email/WhatsApp/SMS templates per event (lead-assigned, callback-due, sanction-received). WhatsApp templates sync to Meta for approval. |
| Notification Logs | Audit trail of every notification sent — date, channel, recipient, status (Sent / Delivered / Read / Failed). |
AI Bots
| Sub-section | What you configure |
|---|---|
| WhatsApp Setup | Connect WhatsApp Business via Meta Embedded Signup. Customers initiate inquiries, team chats with the CRM via natural language. |
| Telegram Bots | Telegram bots created with BotFather, plus per-user Link Telegram for personal bot access. |
Most important to set up first
When you spin up a fresh tenant, the order that matters:
Create the Roles you need
Open Roles and define your team structure — e.g., Sales, Operations, Manager. Set each role as Public so it appears in the Users → Roles tab. Assign permissions at the role level (drastically easier than per-user).
Add Users and assign roles
Open Users, create a login for each team member, pick their role on the Roles tab. The role gives them the right permissions automatically.
Configure Loan Types if your products differ from defaults
The tenant ships with industry-standard loan types. Customize per-product workflow only if you have unusual stages.
Configure Lead Sources to match where your leads actually come from
Default sources cover most cases. Add your specific channels (e.g., "Magic Bricks", "BankBazaar lead-form") so the source filter on the Leads board is meaningful.
Wire up Notifications + WhatsApp
Set up notification templates and connect WhatsApp Cloud API so customers and team members get alerts.
Permission gating
Almost everything under Admin is permission-gated. By default:
- AbpIdentity permissions cover Users + Roles management.
- LoanCRM.Admin.* permissions cover Loan Types, Lead Sources, Document Types.
- AbpTenantManagement.* + integration permissions cover WhatsApp, Telegram, Webhooks.
Only users with the admin role (or a custom role with the right permissions) can see and edit these pages.
Next steps
Commissions Report
Commission earnings and payouts — earned vs received vs pending, per-lender + per-product split, payout aging, partner DSA payouts.
Users
Create and manage SigmaDSA user accounts — username, password, profile, role assignment, and per-user permission overrides. Permissions guide for lockout, deactivation, and role inheritance.