my360tribe

The problem it solves

How it works end-to-end

1. Employee submits a requestAn employee logs in and submits a support request specifying the type of support needed, employment status, work location, operator branch, and any supporting documents.
2. Request enters the queueThe request is automatically linked to the submitting user and routed to the appropriate operator or intake care specialist based on configuration.
3. Operator manages the caseThe assigned operator sees the request in their dashboard, views case details, updates status, attaches documents, and communicates through the platform.
4. Automated emails fire at each stageThe platform sends branded HTML emails at every critical touchpoint account confirmation, password reset, status updates without manual intervention.
5. Files are handled securelySupporting documents are uploaded via the platform and stored either locally (development) or on AWS S3 (production), accessible only via time-limited presigned URLs.
6. Admin oversees everythingAdministrators manage user accounts, assign roles, and monitor the entire system from a single interface with every action role-gated and auditable.

The relay model

• Enterprise HR & People Operations
• Employee Assistance Programs (EAP)
• Corporate Mental Health & Wellness
• Career Transition Support Services
• Workforce Management Platforms
• Peer Support & Ambassador Networks

The platform supports 7 distinct user roles, each with different levels of access and a completely different view of the system.

Module structure

my360tribe Backend (NestJS)
│
├── Auth Module          → Login, registration, token management
├── Google Auth Module   → Google OAuth 2.0 integration
├── Users Module         → User CRUD and profile management
├── Requests Module      → Core support request lifecycle
├── Files Module         → Secure file upload and retrieval
├── Mail Module          → Email delivery and templates
├── Session Module       → Secure session tracking
├── Roles Module         → Role-based access definitions
├── Statuses Module      → User / request status management
└── Database Layer       → MongoDB via Mongoose ODM

Internal module pattern

Each module follows a consistent internal structure:

• Controllers — Handle incoming HTTP requests and delegate to services
• Services — Contain all business logic the core of each module
• DTOs — Define and validate the shape of incoming and outgoing data
• Domain Models — Represent the core business entities within the module
• Persistence Layer — Database interaction via Mongoose repositories

• RESTful API versioned under /api/v1/ all endpoints follow consistent resource naming
• Every sensitive endpoint enforces role-based guards at the controller level
• Authentication is stateless JWT tokens carry all required identity claims
• File storage is environment-aware local driver in development, S3 in production
• Email delivery uses Nodemailer in all environments, MailDev intercepts locally for testing

• JWT access tokens 15-minute expiry limits blast radius of token theft
• bcrypt password hashing plain text passwords never touch the database
• Single-use password reset tokens expire in 30 minutes
• Email confirmation tokens expire in 24 hours
• Server-side session hash allows instant token revocation
• Role guards on every sensitive endpoint no role can exceed its permissions
• AWS S3 presigned URLs private files never publicly accessible
• CORS policy configured at the application level
• No raw error stack traces in API responses safe error serialization

Full interactive documentation with request/response schemas available at /docs (Swagger UI)

• Docker Compose spins up the full stack locally NestJS app, MongoDB, Mongo Express, and MailDev
• File storage driver is environment-aware swap from local to S3 with a single config change
• MailDev intercepts all outgoing emails in development no real emails sent during testing
• MongoDB admin UI via Mongo Express for local database inspection
• Environment variables fully validated at startup the app will not boot with missing config

• 7 user roles with route-level role guards on every sensitive endpoint
• 10+ independent NestJS modules each self-contained and independently scalable
• 3 file storage drivers local for development, S3 for production, presigned URLs for secure access
• 2 authentication methods Email/Password and Google OAuth with stateless JWT sessions
• Automated email delivery for every critical touchpoint via Nodemailer + Handlebars templates
• Full Swagger / OpenAPI documentation generated automatically from code annotations
• Complete Docker Compose setup full local environment with one command