Objective:
Implement OTP generation and sending during user registration and login.

Tasks:

1. Integrate the OTP service with the user registration process.
2. Generate and send an OTP to users when they register.
3. Add OTP validation during the login process to enhance security.
4. Update the documentation to reflect the changes.

Acceptance Criteria:

• Users receive an OTP when registering.
• Users must validate the OTP during login.
• The OTP service functions correctly during both registration and login processes.
• Documentation is updated to include these changes.

Objective:
Create a service for users to reset their passwords using OTP.

Tasks:

• Implement a "Forgot Password" feature that allows users to request a password reset.
• Generate and send an OTP to the user's registered email for verification.
• Create an endpoint for users to verify their OTP and reset their password.
• Ensure security and validation measures are in place.
• Update the project's documentation.

Acceptance Criteria:

1. Users can initiate a password reset using the "Forgot Password" feature.
2. OTPs are sent to the user's email for verification.
3. Users can successfully verify the OTP and reset their password.
4. Security measures are implemented to protect this process.
5. Documentation is updated to include these changes.
6. Please integrate these issues into your project, and feel free to modify them as needed. Good luck with your development!

Objective:
The objective of this issue is to implement CRUD Service in inquiry table, which including create, update, and delete operations.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to implement CRUD Service in property_type table, which including create, update, and delete operations.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
Set up a service for sending one-time passwords (OTP) to users.

Tasks:

1. Choose a suitable package for generating OTPs.
2. Implement the OTP generation and sending logic.
3. Integrate the OTP service with the existing Express and TypeScript project.
4. Test the OTP service to ensure it functions correctly.

Acceptance Criteria:

• The OTP service is successfully set up and integrated into the project.
• OTPs can be generated and sent to users.
• The OTP service is error-free and meets security standards.

Objective:
The objective of this issue is to create an authentication endpoint using JSON Web Tokens (JWT) to facilitate role-based authentication for users in the Property Management System.

Tasks:

1. Create an authentication endpoint that accepts user credentials (e.g., username and password).
2. Verify user credentials and generate a JWT token if authentication is successful.
3. Include user role information in the JWT payload.
4. Implement role-based access control based on the user's role.
5. Update relevant documentation with the changes made.

Acceptance Criteria:

• Users should be able to authenticate and receive a JWT token upon successful login.
• JWT tokens should contain user role information.
• Access to certain functionalities should be restricted based on user roles.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to implement CRUD Service in properties table, which including create, update, and delete operations.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to implement CRUD Service in review table, which including create, update, and delete operations.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to implement CRUD Service in appointment table, which including create, update, and delete operations.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to create middleware guards using the express framework that enforce role-based authentication for specific routes and functionalities in the Property Management System, which is built using JavaScript, Express, and TypeScript.

Tasks:

1. Develop middleware guards that check the user's role based on the JWT token.
2. Apply these middleware guards to routes that require role-based authentication.
3. Ensure that unauthorized users are denied access to restricted routes.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Middleware guards should correctly check and enforce role-based authentication.
• Unauthorized users should be denied access to routes requiring specific roles.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to implement CRUD Service in follow_up table, which including create, update, and delete operations.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to implement CRUD Service in lead table, which including create, update, and delete operations.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to implement authentication guards in various endpoints, including create, update, and delete operations, to enforce role-based authentication in the Property Management System, which is built using JavaScript, Express, and TypeScript.

Tasks:

1. Identify the relevant endpoints for create, update, and delete operations.
2. Apply the role-based authentication guard to these endpoints.
3. Ensure that only authorized users with the appropriate roles can perform these actions.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• Authentication guards should be successfully applied to create, update, and delete endpoints.
• Unauthorized users should be prevented from performing these actions.
• The relevant parts of the documentation should reflect the changes made.

Objective:
The objective of this issue is to enhance security by implementing password hashing using bcrypt when creating a new user in the Property Management System.

Tasks:

1. Add the bcrypt library as a project dependency.
2. Modify the user creation process to hash the user's password using bcrypt.
3. Ensure that the hashed password is securely stored in the database.
4. Update relevant documentation with the changes made.

Acceptance Criteria:

• New users should have their passwords securely hashed using bcrypt during registration.
• The application should successfully create users with hashed passwords.
• The relevant parts of the documentation should reflect the changes made.

Create send email service