How feedutia/portprime works
PortPrime CRM manages the user workflow for consignado-credit portability: users sign in, reach the CRM dashboard, and work with client, convenio, and error-catalog data. The Express server serves the frontend and protects data APIs with session authentication; data routes delegate reads and writes to the database module. The README documents role-based access and the dashboard, while sampled source confirms TOTP-capable authentication and Cosmos DB persistence. Some frontend-to-API wiring is not shown, so those connections are omitted; duplicate GitHub/ copies are not mapped separately.
Main entry points: server.js Express server · database.js Database adapter · dataRoutes.js Data API · index.html Login screen
Components 9
CRM interface
- Login screen
frontend/index.html - CRM dashboard
frontend/app.html - Auth helper
frontend/js/auth.js
Access and sessions
- Auth routes
backend/auth.js
CRM data
- Data API
backend/dataRoutes.js - Database adapter
backend/database.js
Application runtime
- Express server
backend/server.js
Other components
- CRM user
- Azure Cosmos DB
Connections 10
- CRM user → Login screen: opens
README.md - Express server → Login screen: serves
backend/server.js - Express server → CRM dashboard: serves
backend/server.js - CRM user → CRM dashboard: uses
README.md - Auth helper → Auth routes: checks session
frontend/js/auth.js - Express server → Auth routes: registers routes
backend/server.js - Express server → Data API: protects and mounts
backend/server.js - Data API → Database adapter: reads and writes
backend/dataRoutes.js - Express server → Database adapter: initializes
backend/server.js - Database adapter → Azure Cosmos DB: persists data