Notification Catalog
This is the complete catalog of the 150+ notification scenarios the Vruksha ERP can raise, organized across 15 modules. Each entry lists the triggering event, who receives it, its priority, and the channels used to deliver it.
For how notifications appear in the app, how to read and clear them, and how to manage your delivery preferences, see Using Notifications.
:::info How to read this catalog
Each notification has a stable type code (for example AUTH_001, SALE_011). The code is what the system stores against the notification record and uses to route delivery. Codes never change, so they are safe to reference in support tickets and reports.
:::
Channels
Every notification is delivered over one or more channels. The channel set is fixed per notification type but is then filtered by each recipient's delivery preferences.
| Channel | Description | Typical use |
|---|---|---|
| In-App | Real-time notification inside the application, stored in the notification center (bell icon). | All notifications |
| Detailed message with context, deep links, and attachments. | Important events, reports | |
| SMS | Short, time-sensitive alert. | Critical / urgent only |
| Interactive message for buyer-facing communication. | Sales, payments |
In-App is always available and cannot be disabled (it is the system's record of what happened). Email, SMS, and WhatsApp are governed by user preferences and, for SMS, by priority — SMS is reserved for high-priority and critical alerts.
Priority Levels
Priority drives color coding in the notification center, the order alerts are surfaced in, and the expected response time.
| Priority | Meaning | Target response |
|---|---|---|
| 🔴 CRITICAL | Requires immediate action; affects system integrity or a business-critical outcome. | Immediate (under 15 minutes) |
| 🟠 HIGH | Important event requiring timely attention. | Within 1 hour |
| 🟡 MEDIUM | Standard business notification. | Within 4 hours |
| 🟢 LOW | Informational; no immediate action needed. | Within 24 hours |
Distribution at a glance
| Metric | Count |
|---|---|
| Total notification types | 150 |
| Modules covered | 15 |
| 🔴 Critical priority | 15 |
| 🟠 High priority | 65 |
| 🟡 Medium priority | 50 |
| 🟢 Low priority | 20 |
1. Authentication & Security
Notifications for user authentication, security events, and account access. See Authentication Flows for the underlying flows.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| AUTH_001 | Successful Login | User logs in successfully | User | 🟢 LOW | In-App |
| AUTH_002 | Failed Login Attempt | Invalid credentials entered | User (if exists) | 🟡 MEDIUM | Email, In-App |
| AUTH_003 | Account Locked | Max failed login attempts exceeded | User, Admin | 🟠 HIGH | Email, In-App, SMS |
| AUTH_004 | Account Unlocked | Admin unlocks user account | User | 🟡 MEDIUM | Email, In-App |
| AUTH_005 | Password Reset Requested | User requests password reset | User | 🟠 HIGH | |
| AUTH_006 | Password Changed | Password successfully changed | User | 🟠 HIGH | Email, In-App |
| AUTH_007 | Session Expired | Session timeout reached | User | 🟢 LOW | In-App |
| AUTH_008 | New Device Login | Login from unrecognized device | User | 🟡 MEDIUM | Email, In-App |
| AUTH_009 | Email Verification Sent | New signup or email change | User | 🟠 HIGH | |
| AUTH_010 | Email Verified | User verifies email | User | 🟡 MEDIUM | Email, In-App |
2. User & Access Management
Notifications for the user lifecycle, roles, permissions, and invitations. See the RBAC Matrix for who can perform these actions.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| USER_001 | User Created (Disabled) | Admin creates a new user | Admin | 🟢 LOW | In-App |
| USER_002 | Login Invitation Sent | Admin sends a login invite | User, Admin | 🟠 HIGH | Email, In-App |
| USER_003 | Invitation Accepted | User completes setup | Admin | 🟡 MEDIUM | In-App, Email |
| USER_004 | Invitation Expired | Invitation link expires | Admin | 🟢 LOW | In-App |
| USER_005 | User Role Changed | Role assignment modified | User, Admin | 🟠 HIGH | Email, In-App |
| USER_006 | User Suspended | Admin suspends a user | User | 🟠 HIGH | |
| USER_007 | User Activated | User becomes active | User | 🟡 MEDIUM | Email, In-App |
| USER_008 | User Disabled | Admin disables a user | Admin | 🟡 MEDIUM | In-App |
| USER_009 | Subproject Role Assigned | User assigned to a subproject | User, Project Manager | 🟡 MEDIUM | Email, In-App |
| USER_010 | Subproject Role Removed | User removed from a subproject | User, Project Manager | 🟡 MEDIUM | Email, In-App |
| USER_011 | Permission Modified | Access level changed | User | 🟠 HIGH | In-App, Email |
| USER_012 | Profile Updated | User updates their profile | User | 🟢 LOW | In-App |
3. Sales Module
Notifications covering the full sales lifecycle from quotation to registration. See the Sales Orders guide and Sales Calculations.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| SALE_001 | Quotation Created | New quotation generated | Sales Staff, Buyer | 🟡 MEDIUM | Email, In-App, WhatsApp |
| SALE_002 | Quotation Shared | Quotation sent to buyer | Buyer, Sales Staff | 🟡 MEDIUM | Email, WhatsApp |
| SALE_003 | Quotation Expiring Soon | 3 days before expiry | Sales Staff, Buyer | 🟠 HIGH | Email, In-App, SMS |
| SALE_004 | Quotation Expired | Validity period ends | Sales Staff | 🟡 MEDIUM | In-App |
| SALE_005 | Quotation Converted to SO | Quotation becomes a Sales Order | Sales Staff, Sales Head | 🟠 HIGH | Email, In-App |
| SALE_006 | Sales Order Created | New SO generated | Sales Staff, Buyer, Sales Head | 🟠 HIGH | Email, In-App, SMS |
| SALE_007 | SO Status Changed | SO status updated | Sales Staff, Buyer | 🟡 MEDIUM | Email, In-App |
| SALE_008 | SO Approved | Admin approves SO | Sales Staff, Buyer | 🟠 HIGH | Email, In-App |
| SALE_009 | SO Payment Received | Payment recorded | Buyer, Sales Staff, Finance | 🟠 HIGH | Email, In-App, SMS |
| SALE_010 | SO Payment Due | Payment milestone approaching | Buyer, Sales Staff | 🟠 HIGH | Email, In-App, SMS |
| SALE_011 | SO Payment Overdue | Payment past due date | Buyer, Sales Staff, Finance, Sales Head | 🔴 CRITICAL | Email, In-App, SMS |
| SALE_012 | SO Cancellation Requested | Cancellation initiated | Admin, Sales Head | 🟠 HIGH | Email, In-App |
| SALE_013 | SO Cancelled | SO cancellation approved | Buyer, Sales Staff | 🟠 HIGH | Email, In-App |
| SALE_014 | SO Forfeited | SO forfeiture processed | Buyer, Finance | 🟠 HIGH | |
| SALE_015 | Sales Invoice Created | SI generated | Buyer, Finance | 🟠 HIGH | Email, In-App |
| SALE_016 | SO Split Executed | SO split into multiple | Buyer, Sales Staff | 🟠 HIGH | Email, In-App |
| SALE_017 | Unit Added to SO | Unit added post-creation | Buyer, Sales Staff | 🟡 MEDIUM | Email, In-App |
| SALE_018 | Payment Schedule Generated | Schedule created | Buyer | 🟡 MEDIUM | |
| SALE_019 | Refund Processed | Refund approved and executed | Buyer, Finance | 🟠 HIGH | Email, In-App, SMS |
| SALE_020 | Discount Applied | Discount added to SO | Sales Staff, Sales Head | 🟡 MEDIUM | In-App |
4. Unit & Inventory
Notifications for the unit lifecycle, status changes, and inventory operations. See Status Lifecycles for unit status meanings.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| UNIT_001 | Unit Created | New unit added | Project Manager | 🟢 LOW | In-App |
| UNIT_002 | Unit Status Changed | Status transition | Sales Staff, Project Manager | 🟡 MEDIUM | In-App |
| UNIT_003 | Unit Blocked | Temporary hold placed | Sales Staff | 🟡 MEDIUM | In-App |
| UNIT_004 | Unit Block Expiring | Block expires in 24 hours | Sales Staff | 🟠 HIGH | Email, In-App |
| UNIT_005 | Unit Block Expired | Block automatically released | Sales Staff | 🟠 HIGH | Email, In-App |
| UNIT_006 | Unit Booked | SO created for unit | Sales Staff, Project Manager | 🟠 HIGH | In-App, Email |
| UNIT_007 | Unit Registered | Registration completed | Buyer, Sales Staff, Admin | 🔴 CRITICAL | Email, In-App, SMS |
| UNIT_008 | Unit Frozen | Admin freezes unit | Admin, Project Manager | 🔴 CRITICAL | Email, In-App |
| UNIT_009 | Unit Unfrozen | Freeze removed | Admin, Project Manager | 🟠 HIGH | Email, In-App |
| UNIT_010 | Unit Split Executed | Unit divided | Admin, Project Manager | 🟠 HIGH | Email, In-App |
| UNIT_011 | Unit Merge Executed | Units combined | Admin, Project Manager | 🟠 HIGH | Email, In-App |
| UNIT_012 | Unit Switch Executed | Buyer switches unit | Buyer, Sales Staff | 🟠 HIGH | Email, In-App |
| UNIT_013 | Unit Shareholding Changed | Partner % modified | Admin, Partners | 🔴 CRITICAL | Email, In-App |
| UNIT_014 | Unit Price Updated | Rate revision | Sales Staff, Project Manager | 🟡 MEDIUM | In-App |
| UNIT_015 | Unit Cancelled (From SO) | SO cancellation | Project Manager | 🟠 HIGH | In-App |
5. Stock (Land) Management
Notifications for land acquisition, the stock lifecycle, and allocation. See Stock Lifecycle and Allocations.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| STK_001 | Stock Created | New stock added | Admin | 🟡 MEDIUM | In-App |
| STK_002 | Stock Status Changed | Lifecycle transition | Admin, Finance Manager | 🟠 HIGH | Email, In-App |
| STK_003 | Stock Registered | Registration complete | Admin, Partners | 🔴 CRITICAL | Email, In-App |
| STK_004 | Stock Allocated to Project | Stock mapped | Admin, Project Manager | 🟠 HIGH | Email, In-App |
| STK_005 | Stock Partially Allocated | Partial allocation | Admin | 🟡 MEDIUM | In-App |
| STK_006 | Stock Ownership Changed | Holder % modified | Admin, Partners | 🔴 CRITICAL | Email, In-App |
| STK_007 | Stock Transfer Initiated | Transfer request | Admin | 🟠 HIGH | Email, In-App |
| STK_008 | Stock Transfer Approved | Transfer completed | Admin, Partners | 🔴 CRITICAL | Email, In-App |
| STK_009 | Stock Payment Made | Payment to seller | Admin, Finance | 🟠 HIGH | In-App, Email |
| STK_010 | Stock Payment Due | Seller payment approaching | Finance, Admin | 🟠 HIGH | Email, In-App |
| STK_011 | Stock Cost Updated | Cost component changed | Admin, Finance | 🟡 MEDIUM | In-App |
| STK_012 | Stock Document Uploaded | New document added | Admin | 🟢 LOW | In-App |
6. Partnership & Ownership
Notifications for partnerships, partner management, and ownership structures. Holding-percentage rules are documented in Validation Rules.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| PART_001 | Partnership Created | New partnership | Admin, Partners | 🟠 HIGH | Email, In-App |
| PART_002 | Partnership Holding Changed | % modification | Admin, All Partners | 🔴 CRITICAL | Email, In-App |
| PART_003 | Partner Added to Partnership | New partner joins | Admin, Partners | 🟠 HIGH | Email, In-App |
| PART_004 | Partner Removed from Partnership | Partner exit | Admin, Partners | 🟠 HIGH | Email, In-App |
| PART_005 | Managing Partner Changed | MP designation change | Admin, All Partners | 🟠 HIGH | Email, In-App |
| PART_006 | Capital Call Initiated | Funding request | Partners | 🔴 CRITICAL | Email, In-App, SMS |
| PART_007 | Capital Call Response Received | Partner responds | Admin, Managing Partner | 🟠 HIGH | In-App |
| PART_008 | Settlement Recommended | System generates | Admin, Partners | 🟠 HIGH | Email, In-App |
| PART_009 | Settlement Processed | Settlement paid | Partner, Admin | 🔴 CRITICAL | Email, In-App, SMS |
| PART_010 | Partner Statement Ready | Report generated | Partner | 🟡 MEDIUM | Email, In-App |
| PART_011 | Due From Partner Updated | Balance changed | Partner, Admin | 🟡 MEDIUM | In-App |
| PART_012 | Due To Partner Updated | Balance changed | Partner, Admin | 🟡 MEDIUM | In-App |
| PART_013 | Profit Allocation Completed | Allocation run done | Admin, Partners | 🟠 HIGH | Email, In-App |
| PART_014 | Share Sale Initiated | Share transfer request | Admin, Partners | 🔴 CRITICAL | Email, In-App |
| PART_015 | Share Sale Approved | Transfer completed | All Partners | 🔴 CRITICAL | Email, In-App |
7. Project & Subproject
Notifications for the project lifecycle, layouts, and configuration.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| PROJ_001 | Project Created | New project added | Admin, Project Manager | 🟠 HIGH | Email, In-App |
| PROJ_002 | Project Status Changed | Lifecycle update | Admin, Project Manager | 🟡 MEDIUM | In-App |
| PROJ_003 | Subproject Created | New subproject | Project Manager | 🟡 MEDIUM | In-App |
| PROJ_004 | Subproject Layout Uploaded | SVG uploaded | Project Manager, Admin | 🟠 HIGH | In-App |
| PROJ_005 | Layout Published | Customer view enabled | Admin | 🟠 HIGH | In-App |
| PROJ_006 | Amenity Added | New amenity mapped | Project Manager | 🟢 LOW | In-App |
| PROJ_007 | Project Partnership Changed | Partner mapping modified | Admin, Partners | 🔴 CRITICAL | Email, In-App |
| PROJ_008 | Project Stock Mapping Changed | Stock link modified | Admin | 🟠 HIGH | Email, In-App |
8. Finance & Banking
Notifications for financial transactions, bank reconciliation, and accounting. See Bank Accounts.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| FIN_001 | Bank Account Created | New account added | Admin, Finance Manager | 🟡 MEDIUM | In-App |
| FIN_002 | Bank Statement Uploaded | Statement import | Finance Manager | 🟡 MEDIUM | In-App |
| FIN_003 | Transaction Mapped | Manual / auto mapping | Finance Manager | 🟢 LOW | In-App |
| FIN_004 | Reconciliation Discrepancy | Mismatch found | Finance Manager, Admin | 🟠 HIGH | Email, In-App |
| FIN_005 | Unmapped Transactions Alert | Daily summary | Finance Manager | 🟡 MEDIUM | Email, In-App |
| FIN_006 | Large Transaction Alert | Amount exceeds threshold | Admin, Finance Manager | 🟠 HIGH | Email, In-App, SMS |
| FIN_007 | Period Lock Requested | Lock initiation | Admin | 🟠 HIGH | In-App |
| FIN_008 | Period Locked | Lock approved | Finance Manager, Admin | 🔴 CRITICAL | Email, In-App |
| FIN_009 | Period Unlocked | Emergency unlock | Finance Manager, Admin | 🔴 CRITICAL | Email, In-App |
:::note Phase scope Some finance and loan items below (reconciliation, period locks, loans) are part of the notification design but are outside the Phase 1 scope. They are catalogued here so the type codes remain stable as those modules are enabled. :::
9. Loan Management
Notifications for bank, partner, seller, and vendor loans.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| LOAN_001 | Loan Created | New loan added | Admin, Finance Manager | 🟠 HIGH | Email, In-App |
| LOAN_002 | Loan Disbursement Received | Funds received | Finance Manager | 🟠 HIGH | In-App |
| LOAN_003 | EMI Due Reminder | 7 days before due | Finance Manager | 🟠 HIGH | Email, In-App |
| LOAN_004 | EMI Overdue | Payment missed | Finance Manager, Admin | 🔴 CRITICAL | Email, In-App, SMS |
| LOAN_005 | Loan Repayment Made | Payment recorded | Finance Manager | 🟡 MEDIUM | In-App |
| LOAN_006 | Interest Accrued | Periodic calculation | Finance Manager | 🟢 LOW | In-App |
| LOAN_007 | Loan Closed | Full repayment | Finance Manager, Admin | 🟠 HIGH | Email, In-App |
| LOAN_008 | Partner Loan Created | Partner lends | Partner, Admin | 🟠 HIGH | Email, In-App |
| LOAN_009 | Seller Due Converted | Due converted to loan | Admin, Finance Manager | 🟠 HIGH | Email, In-App |
10. Approval Workflow
Notifications for pending approvals, reviews, and workflow actions.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| APPR_001 | Approval Request Created | High-risk action initiated | Approver(s) | 🟠 HIGH | Email, In-App |
| APPR_002 | Approval Pending Reminder | 24 hours pending | Approver(s) | 🟠 HIGH | Email, In-App |
| APPR_003 | Approval Granted | Approver approves | Requester | 🟠 HIGH | Email, In-App |
| APPR_004 | Approval Rejected | Approver rejects | Requester | 🟠 HIGH | Email, In-App |
| APPR_005 | Escalation Triggered | SLA exceeded | Higher Authority | 🔴 CRITICAL | Email, In-App, SMS |
| APPR_006 | Bulk Approval Completed | Multiple approvals | Admin | 🟡 MEDIUM | In-App |
11. Document Management
Notifications for document uploads, downloads, and compliance. See the Documents guide.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| DOC_001 | Document Uploaded | New upload | Entity Owner | 🟢 LOW | In-App |
| DOC_002 | Document Approved | Compliance check passed | Uploader | 🟡 MEDIUM | In-App |
| DOC_003 | Document Rejected | Compliance failed | Uploader | 🟠 HIGH | Email, In-App |
| DOC_004 | Document Expiring | 30 days before expiry | Admin, Entity Owner | 🟠 HIGH | Email, In-App |
| DOC_005 | Document Expired | Expiry date passed | Admin, Entity Owner | 🔴 CRITICAL | Email, In-App, SMS |
| DOC_006 | Mandatory Document Missing | Compliance check | Admin, Entity Owner | 🟠 HIGH | Email, In-App |
12. Reports & Analytics
Notifications for scheduled reports, exports, and analytics alerts. See the Reports overview.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| RPT_001 | Report Generated | Scheduled / on-demand | Requester | 🟡 MEDIUM | Email, In-App |
| RPT_002 | Report Export Completed | Large export done | Requester | 🟡 MEDIUM | Email, In-App |
| RPT_003 | Report Generation Failed | Error in report | Requester, Admin | 🟠 HIGH | Email, In-App |
| RPT_004 | Scheduled Report Ready | Daily / weekly / monthly | Subscribers | 🟡 MEDIUM | |
| RPT_005 | Partner Report Pack Ready | Partner reports generated | Partner | 🟡 MEDIUM | Email, In-App |
| RPT_006 | KPI Threshold Alert | Metric exceeds limit | Admin, Relevant Manager | 🟠 HIGH | Email, In-App |
13. Audit & System
Notifications for audit events, system changes, and security alerts.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| AUD_001 | Critical Action Logged | High-risk operation | Admin | 🟠 HIGH | In-App |
| AUD_002 | Settings Changed | System config modified | Admin | 🟠 HIGH | Email, In-App |
| AUD_003 | Bulk Data Import | Excel / CSV import | Admin | 🟠 HIGH | Email, In-App |
| AUD_004 | Data Export Performed | Sensitive export | Admin | 🟠 HIGH | Email, In-App |
| AUD_005 | Suspicious Activity | Anomaly detected | Admin | 🔴 CRITICAL | Email, In-App, SMS |
| AUD_006 | Override Action Logged | Validation bypassed | Admin | 🔴 CRITICAL | Email, In-App |
| AUD_007 | Audit Trail Exported | Audit export | Admin | 🟠 HIGH | In-App |
14. Employee & HR
Notifications for employee management, payroll, and HR actions.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| EMP_001 | Employee Created | New employee added | HR Manager, Admin | 🟡 MEDIUM | In-App |
| EMP_002 | Employee Linked to User | User account linked | Employee, HR | 🟡 MEDIUM | Email, In-App |
| EMP_003 | Payroll Run Initiated | Payroll processing | HR Manager, Finance | 🟠 HIGH | In-App |
| EMP_004 | Payroll Completed | Payroll processed | HR Manager, Finance, Admin | 🟠 HIGH | Email, In-App |
| EMP_005 | Salary Credit Confirmation | Payment processed | Employee | 🟡 MEDIUM | Email, SMS |
| EMP_006 | Employment Status Changed | Status transition | Employee, HR | 🟠 HIGH | Email, In-App |
| EMP_007 | Cost Allocation Updated | Project mapping changed | Project Manager | 🟢 LOW | In-App |
15. Vendor & Procurement
Notifications for vendor management, purchase orders, and payments.
| ID | Event | Trigger | Recipients | Priority | Channels |
|---|---|---|---|---|---|
| VEN_001 | Vendor PO Created | New PO raised | Finance Manager, Vendor | 🟠 HIGH | Email, In-App |
| VEN_002 | Vendor PO Approved | PO approval | Finance Manager | 🟠 HIGH | In-App |
| VEN_003 | Vendor PI Created | Invoice received | Finance Manager | 🟡 MEDIUM | In-App |
| VEN_004 | Vendor Payment Due | Payment approaching | Finance Manager | 🟠 HIGH | Email, In-App |
| VEN_005 | Vendor Payment Processed | Payment made | Finance Manager, Vendor | 🟠 HIGH | Email, In-App |
| VEN_006 | Vendor Advance Paid | Advance released | Finance Manager | 🟡 MEDIUM | In-App |
| VEN_007 | Seller PO Created | Land purchase PO | Admin, Finance | 🟠 HIGH | Email, In-App |
| VEN_008 | Seller PO Cancelled | PO cancellation | Admin, Finance | 🔴 CRITICAL | Email, In-App |
Module-wise count
| Module | Count |
|---|---|
| Authentication & Security | 10 |
| User & Access Management | 12 |
| Sales Module | 20 |
| Unit & Inventory | 15 |
| Stock (Land) Management | 12 |
| Partnership & Ownership | 15 |
| Project & Subproject | 8 |
| Finance & Banking | 9 |
| Loan Management | 9 |
| Approval Workflow | 6 |
| Document Management | 6 |
| Reports & Analytics | 6 |
| Audit & System | 7 |
| Employee & HR | 7 |
| Vendor & Procurement | 8 |
| Total | 150 |
How notifications are stored
Each notification persists a record that the notification center reads from, plus a per-channel delivery log so the system knows whether each email, SMS, or WhatsApp message actually went out.
Notification record captures: organization, recipient user, the type code (for example SALE_011), title, message, priority, the related entity (type and ID), a deep-link action URL, when it was read, and any extra metadata.
Delivery log captures, per channel (In-App / Email / SMS / WhatsApp): the delivery status (Pending / Sent / Delivered / Failed), timestamps, and a failure reason if delivery did not succeed.
Related pages
- Using Notifications — reading, clearing, and configuring notifications in the app
- RBAC Matrix — who receives role-based notifications
- Status Lifecycles — the status changes that trigger many notifications
- Authentication Flows — the flows behind the authentication notifications