How gauravbalodi123/turtle_finance_dashboard works
Enumerate the Key Collections
• users
• advisors
• clients
• bookings
• tasks
• rowwisetasks
• subscriptionplans
• payments
• digioresponses
• files
• kycdata
• riskprofiles
• prospects
• members
• comments
• various form data (investmentForm, insuranceForm, taxPlanningForm, willDraftingForm, creditCardForm)
Collection Relationships
• bookings → users (refers to the client who booked)
• bookings → advisors
• tasks → users (owner/creator)
• rowwisetasks → tasks
• clients → riskprofiles
• clients → kycdata
• clients → digioresponses
• clients → payments
• subscriptionplans → users (active subscription)
• members → users (activated members)
• prospects → advisors (assigned prospect)
• comments → bookings or tasks (comment context)
• Use arrowheads to indicate “references” (e.g., ObjectId FK).
Indexes and Unique Constraints (optional)
• For critical collections (users, advisors), mark unique indexed fields such as email or userId.
• Notate them in small italics under each collection name.
Backup and Seed Scripts
• backup26june folder
• turtle-backup folders
• Admin routes → MongoDB
• Client routes → MongoDB
• Calendly/Fireflies integration scripts → MongoDB
Detail Level
• Only collections and relationships, not field‐level detail, unless a specific collection’s schema is critical.