samjoshua2002/educrm

Purpose and topology

educrm is a multi-tenant admissions CRM split into a Next.js administrative/public portal and a NestJS tenant API. It supports superadmin organization management, organization operations, staff/admin workflows, applicant self-service, public forms, lead capture, applications, and academic master data.

• admissions-mm-admin-main/src/app

• admissions-tenant-api-main/src/app.module.ts

• docker-compose.yml

Frontend entry points and role boundaries

The Next.js App Router frontend separates experiences by route group and role: authentication, internal main/admin views, applicant views, organization tenant views, and superadmin views. Layouts and role-specific sidebars provide the principal UI shell boundary.

• admissions-mm-admin-main/src/app/layout.tsx

• admissions-mm-admin-main/src/app/organization/layout.tsx

• admissions-mm-admin-main/src/app/superadmin/layout.tsx

Public form and lead ingestion

Public form URLs resolve by slug, while the backend exposes public-form submission and form-response endpoints. Submission data is persisted as form responses/submissions and feeds lead ingestion; lead assignment, verification, notes, status changes, and closure are separate workflow concerns.

• admissions-mm-admin-main/src/app/f/[slug]/page.tsx

• admissions-tenant-api-main/src/modules/forms/public-forms.controller.ts

• admissions-tenant-api-main/src/modules/leads/lead-ingestion.service.ts

Admissions and application lifecycle

Applications are a core domain aggregate with section-specific records for addresses, education, parents, work experience, qualifications, tests, and activities. Organization and main/admin application pages consume this lifecycle; the user portal exposes “my application.” Status updates and application activities form the audit/progression path.

• admissions-tenant-api-main/src/modules/applications/applications.service.ts

• admissions-tenant-api-main/src/modules/applications/entities/application.entity.ts

• admissions-mm-admin-main/src/app/(user)/my-application/page.tsx

Tenant administration and master data

Organizations are the tenancy root. Their staff administer branches, courses, academic sessions, course sessions, users/team members, forms, leads, applications, communications, payments, events, and students through organization-scoped routes and API modules.

• admissions-tenant-api-main/src/modules/organizations/organizations.service.ts

• admissions-tenant-api-main/src/modules/branches/branches.service.ts

• admissions-mm-admin-main/src/app/organization/settings/page.tsx

Authentication, authorization, and tenancy boundary

The API uses JWT authentication plus role and tenant guards, with common response transformation and exception handling. Frontend middleware is the corresponding route-access boundary; client auth state is maintained separately. Superadmin routes manage organizations and subscriptions, distinct from tenant routes.

• admissions-tenant-api-main/src/common/guards/jwt-auth.guard.ts

• admissions-tenant-api-main/src/common/guards/tenant.guard.ts

• admissions-mm-admin-main/src/middleware.ts

Data access, API integration, and runtime infrastructure

The frontend uses an API client, domain hooks, and a React Query provider/query client to fetch and cache backend resources. The Nest API follows controller → service → entity/DTO module boundaries and is backed by the schema represented in Database.sql. A local Next upload route is present; no specific third-party storage, payment, or messaging provider is identifiable from the tree.

• admissions-mm-admin-main/src/lib/api.ts

• admissions-mm-admin-main/src/components/providers/query-provider.tsx

• admissions-tenant-api-main/Database.sql