Expected Outcome
The system should automatically check for user activity.
Users who have been inactive for 30 days should be blocked.
Blocked users should be unable to log in until they contact support or follow a reactivation process.
Additional Requirements
Create a scheduled task (e.g., using node-cron or a similar library) to run the inactivity check daily.
Update the user schema to include a field for the last activity date.
Ensure proper notifications are sent to users who are about to be blocked (e.g., an email notification 5 days before the block).
Improvement Suggestions
Suggestions for a reactivation process (e.g., email verification or contacting support).
Feedback on potential performance impacts and how to handle large user databases efficiently.
Additional Information
Consider using a library like node-cron for scheduling the inactivity check.
Ensure the implementation is scalable and can handle a large number of users.
Make sure to document the feature clearly for future maintenance.
Expected Outcome
The system should automatically check for user activity.
Users who have been inactive for 30 days should be blocked.
Blocked users should be unable to log in until they contact support or follow a reactivation process.
Additional Requirements
Create a scheduled task (e.g., using node-cron or a similar library) to run the inactivity check daily.
Update the user schema to include a field for the last activity date.
Ensure proper notifications are sent to users who are about to be blocked (e.g., an email notification 5 days before the block).
Improvement Suggestions
Suggestions for a reactivation process (e.g., email verification or contacting support).
Feedback on potential performance impacts and how to handle large user databases efficiently.
Additional Information
Consider using a library like node-cron for scheduling the inactivity check.
Ensure the implementation is scalable and can handle a large number of users.
Make sure to document the feature clearly for future maintenance.