Role-Based Background Verification Platform
Budget: ₹500,000 – ₹1,000,000 INR
I’m building a secure, multi-tenant background-verification system with five dedicated portals: Super Admin, Client Admin, HR, Agent, and Candidate. The stack is set: React for the front end, Node.js for the back end, and MariaDB underneath. What I need now is the full implementation—clean code, clear structure, and deployment-ready.
Portals and core workflow
Super Admin must handle user management for every role, dig into system-wide reports, and tweak platform-level settings. Client Admins should manage their own users, monitor each candidate’s verification status in real time, and export tailored reports. HR teams will assign checks, view detailed candidate records, and keep a direct conversation thread with the field agents performing the verifications. Agents need a streamlined workspace to update findings, upload evidence, and flag issues, while Candidates require a simple interface to submit documents, track progress, and respond to clarifications.
Technical expectations
• React (hooks, functional components, modern state management).
• Node.js with a modular structure—Express or NestJS are both fine—exposing a RESTful API.
• MariaDB schema with migrations, relational integrity, and audit trails.
• JWT (with refresh tokens) for authentication plus role-based authorization at both API and UI level.
• Responsive UI, accessible design, and clear form validation.
• Docker-compose for local spin-up and an environment file ready for cloud deployment.
• Unit and integration tests covering critical paths.
Acceptance criteria
1. Each role logs in and sees only its permitted screens/actions.
2. End-to-end background-check flow: HR assignment → Agent update → Client/Candidate status reflection.
3. Super Admin can deactivate any user instantly and the change propagates without re-deployment.
4. All data changes recorded with timestamps and acting user ID.
5. Build, test, and run with one command: `docker-compose up --build`.
Hand-off will include full source code in a Git repo, database scripts, API documentation (Swagger or similar), and a brief deployment guide.
Portals and core workflow
Super Admin must handle user management for every role, dig into system-wide reports, and tweak platform-level settings. Client Admins should manage their own users, monitor each candidate’s verification status in real time, and export tailored reports. HR teams will assign checks, view detailed candidate records, and keep a direct conversation thread with the field agents performing the verifications. Agents need a streamlined workspace to update findings, upload evidence, and flag issues, while Candidates require a simple interface to submit documents, track progress, and respond to clarifications.
Technical expectations
• React (hooks, functional components, modern state management).
• Node.js with a modular structure—Express or NestJS are both fine—exposing a RESTful API.
• MariaDB schema with migrations, relational integrity, and audit trails.
• JWT (with refresh tokens) for authentication plus role-based authorization at both API and UI level.
• Responsive UI, accessible design, and clear form validation.
• Docker-compose for local spin-up and an environment file ready for cloud deployment.
• Unit and integration tests covering critical paths.
Acceptance criteria
1. Each role logs in and sees only its permitted screens/actions.
2. End-to-end background-check flow: HR assignment → Agent update → Client/Candidate status reflection.
3. Super Admin can deactivate any user instantly and the change propagates without re-deployment.
4. All data changes recorded with timestamps and acting user ID.
5. Build, test, and run with one command: `docker-compose up --build`.
Hand-off will include full source code in a Git repo, database scripts, API documentation (Swagger or similar), and a brief deployment guide.