I need a lightweight, web-based application that lets me assign tasks to each team member (one or more for a single task) and follow their progress in real time. Users will sign in with a simple username-and-password flow; no social log-ins or two-factor layers are required at this stage. Core flow I have in mind •There are 3 levels of users. a) User b) Manager c) Admin User: The User can assign tasks or reply to tasks assigned to him. He can't see anyone else's window. Manager: Along with rights of user, he can view everyone's window but can't edit or delete. Manager can add Users. He can view only Users added by him. Admin: Along with rights of Manager and User, can edit, delete any comments or tasks. Admin can add Managers. • Basically 2 pages. The 1st page shows the list of tasks pending, both assigned to others and assigned by others. •Based on option selected, either we create a new task or check replies received or reply to tasks assigned by others. This moves us to the next page. • I create a project or sprint, break it into tasks, and allocate each task to one or more users. I can attach multiple files for a task • Each user sees only the tasks that belong to them, updates status (To-Do, In-Progress, Done, or a percentage slider), and can leave short notes. Replies can't be edited or deleted by user. They can only append existing tasks. • A task is considered complete only when the Task Assigner closes that task • A dashboard shows me every task, its owner, current status, and any overdue items at a glance. • Menus to add team member details, designation, password • Filters and reporting for both assigned tasks (assigned to someone) and pending tasks (assigned by someone), date-wise, person wise, completed task filtering, etc. Tech stack is flexible—Laravel, Django, Node, or even a pragmatic low-code framework is fine—as long as the end result runs smoothly in any modern browser (google chrome). Suggestions welcome. Deliverables Implementing the Project completely 1. Source code in a public or private Git repository. 2. A database schema (MySQL or PostgreSQL preferred) with seed data for testing. 3. Hosting in cloud. 4. A short video or screenshare walk-through confirming every feature works. Acceptance criteria • I can add, edit, assign, and close tasks without page reload errors. • Login and logout flows are secure and session-based. • Dashboard updates reflect the latest status without manual refresh. • Code passes a quick vulnerability scan for common issues (SQL injection, XSS). If you already have a boilerplate you can adapt quickly, great—tell me. Otherwise, outline your proposed stack, timeline, and any questions you still have so we can get started. We are based in New Delhi. Local Developers preferred but not mandatory.