🏗️ Enkage Backend Project

What is Enkage?

Enkage is a modern, scalable backend API system built with Node.js and Express, designed for knowledge management systems similar to KKMA (Kuwait Kerala Muslim Association). It provides comprehensive management of members, organizations, committees, transactions, and multi-layered authentication.

• ✅ Multi-Layer Authentication: Separate auth for Admin, Committee, and StarClub members
• ✅ Role-Based Access Control: Dynamic permissions based on user roles and positions
• ✅ Hierarchical Organization: 3-layer organizational structure (Center, Zone, Branch)
• ✅ Committee Management: Positions, departments, and delegation support
• ✅ Member Management: Registration, renewal, family members, and referrals
• ✅ Transaction Processing: Payments, refunds, and comprehensive tracking
• ✅ Form Approvals: Multi-level approval workflows
• ✅ File Uploads: Secure file management with folder structure

Module Structure

The project follows a modular architecture where each feature is self-contained:

src/modules/
├── auth/           # User authentication
├── members/        # Member management
├── committees/     # Committee management
├── committeeMembers/ # Committee member assignments
├── organizations/  # Organization structure
├── organizationUnits/ # Layer hierarchy
├── organizationSettings/ # Configuration
├── transactions/   # Payment processing
├── formApprovals/ # Approval workflows
├── fileUpload/    # File management
├── locations/     # Location data
└── mixedauth/     # Multi-layer authentication
                    

Full System Access

• ✅ Manage all users in the system
• ✅ Create, edit, and delete all members
• ✅ Manage committee structures and assignments
• ✅ Configure organization hierarchy and settings
• ✅ View and manage all transactions
• ✅ Generate onetime passwords for members
• ✅ Reset 2FA for any member
• ✅ Export reports and data
• ✅ System configuration and settings

Based on Position Permissions

• ✅ View committee-specific reports and data
• ✅ Manage assigned committee members (if permitted)
• ✅ Approve/Reject transactions based on position
• ✅ View and manage assigned cases/forms
• ✅ Access layer-specific data based on committee assignment
• ✅ Department-specific access if assigned

Referral-Based Access

• ✅ View complete referral network tree
• ✅ View referral statistics and analytics
• ✅ Track referred members' status
• ✅ Access referral-based reports
• ✅ View income/benefits from referrals
• ✅ Manage and contact referred members

Three-Tier Access Control System

The system implements role-based filtering at multiple levels:

1. User Type Level: Admin sees all, Committee/StarClub see filtered data
2. Permission Level: Position-based permissions for committee members
3. Hierarchy Level: Organization layer (Center, Zone, Branch) filtering
4. Department Level: Department-specific access for committee members

Available Transaction Filters

The transaction table supports comprehensive filtering:

• Date Range: dateFrom, dateTo - Filter by transaction creation date
• Amount Range: amountMin, amountMax - Filter by transaction amount
• Type: transactionType - membership_fee, renewal_fee, late_fee, etc.
• Status: paymentStatus - pending, completed, failed, cancelled, refunded
• Organization: organizationId - Filter by specific organization
• Layer Hierarchy: center (Layer 1), zone (Layer 2), branch (Layer 3)
• Member: memberId - Filter by specific member
• Star Club: starClubMember - Filter by referring member
• Search: search - Search by name, transaction ID, payment ID
• Currency: currency - Filter by currency (KWD, USD, etc.)

Example: Transaction Filtering Logic

// 1. User logs in - JWT token contains user info
const user = { 
    id: 123, 
    layer: 'committee',
    committeeData: { layerId: 5, departmentId: 2 }
}

// 2. Request comes with filters
GET /api/v1/transactions/transaction-table?page=1&limit=20

// 3. Backend applies automatic filters based on user type
if (user.layer === 'committee') {
    // Only show transactions from members in same layer
    filters.layerId = user.committeeData.layerId;
    
    // Optional: Filter by department if assigned
    if (user.committeeData.departmentId) {
        filters.departmentId = user.committeeData.departmentId;
    }
}

// 4. Query database with applied filters
SELECT * FROM transactions 
WHERE layer_id = 5 
AND department_id = 2
LIMIT 20 OFFSET 0;