muhammadidrusalawi/hris-api

AI Summary: This issue proposes to change the database behavior when a department is deleted. Currently, deleting a department also deletes all associated employees. The desired outcome is for employees to remain in the system, with their `department_id` field set to NULL instead of being deleted.

AI Summary: This issue requests a new API endpoint to retrieve all users assigned the 'manager' role. This is needed for various HRIS functionalities, such as assigning managers to departments and populating frontend dropdowns. The endpoint should filter users by role, adhere to existing authentication/authorization, and return a standardized JSON response with appropriate tests and documentation.

AI Summary: This issue proposes implementing owner-based scoping for employee data without altering the existing database schema. The solution involves leveraging the `user_id` relationship in the `employees` table and the `owner_id` field in the `users` table to ensure employees are only accessible within their designated owner's scope. This will prevent cross-owner data exposure by enforcing query-level filtering.

AI Summary: This issue proposes adding a new authentication method to the system, allowing users to log in solely with their employee code, bypassing the need for a password. This feature is specifically for internal HRIS use cases and must be implemented as a distinct login flow from the existing email/password authentication.