Tables

Module: Asset
Purpose: Stores asset type details.
Data: One row is created for each type of asset available in the system.
Process Usage:
- Users can create assets based on the defined asset types.
- Defines metadata and criteria for asset creation.
Key Points:
- Stores descriptive information about each asset type.
- Can define assignment criteria in JSON format.
- Tracks whether the asset type is active and available for use.
Business Impact: Ensures proper categorization, management, and controlled creation of assets.

Module: HRMS Expense Management
Purpose: Manages the multi-level approval workflow for expense claims, tracking approver decisions, comments, and approval timeline.
Data: Each row represents the approval lifecycle for a single expense claim, capturing approver actions, status changes, and decision rationale.
Process Usage:
- Tracks two-level approval workflow with representative approvals.
- Captures approver comments and rejection reasons.
- Maintains approval timeline and final decision status.
Key Points:
- Two-tier approval system with separate approver tracking.
- Comprehensive status tracking throughout approval lifecycle.
- Integration with payment processing and claim cancellation.
Business Impact: Ensures proper authorization controls, maintains approval audit trail, and streamlines expense claim processing workflow.

Module: HRMS Leave Management (Manual Adjustment Audit)
Purpose: Tracks manual leave balance adjustments and corrections performed by HR administrators.
Data: Stores audit records for manual leave additions/deductions with before/after balance snapshots.
Process Usage:
- Records manual balance corrections via HR admin interface.
- Provides audit trail for all manual leave adjustments.
- Supports balance reconciliation and dispute resolution.
Key Points:
- Captures complete context of manual adjustments including remarks and timestamps.
- Integrates with monthly leave tracking and balance rollover processes.
Business Impact: Essential for compliance, audit trails, and transparency in manual leave management operations.

Module: Core/Payroll Management - Financial Year Master
Purpose: Defines and tracks the official start and end dates, status, and control parameters for each financial year (FY) used by the organization for accounting, payroll, and compliance reporting.
Data: Stores the FY period, the company/SBU it applies to, and control flags indicating if the FY is active, running, or closed.
Process Usage:
- Period Control: Used to validate dates and determine the current active financial cycle for transactional processing.
- Year-End/Year-Begin: Essential for executing year-end closing procedures and setting up the new fiscal period.
Key Points:
- Crucial for statutory compliance, especially tax and TDS returns, which are tied to the financial year.
- The FYRunning flag manages the active status of the current working year.
Business Impact: Ensures consistent and accurate reporting and calculation across all finance and payroll modules.

Module: Payroll/Compensation Management - Pay Element Configuration History Log
Purpose: Stores an immutable, historical record of all changes made to a master Pay Element definition (e.g., Basic Salary, HRA, Provident Fund deduction). This is crucial for payroll auditing and compliance.
Data: Captures the unique ID of the original pay element, and a serialized string (History) of its entire configuration object (including name, code, type, formula, etc.) at the time of the change.
Process Usage:
- Auditing: Provides a complete audit trail to track when, why, and by whom the calculation rules, names, or types of a specific pay element were changed.
- Compliance: Essential for demonstrating that the correct pay element rules were applied during past payroll runs.
- Reference: Allows retrospective analysis of pay element definitions for troubleshooting or legal review.
Key Points:
- Snapshot Storage: The History column stores the full configuration object, often in JSON format.
- Linked to the active pay element master table via PayelementId.
Business Impact: Ensures the integrity and traceability of the core building blocks of the organization’s salary structures and payroll calculations.

Module: Reimbursement/Payroll Management - Employee Payment Ledger
Purpose: Stores individual payment records for employees that are separate from their regular fixed salary, typically used for approved reimbursements, variable bonuses, or other ad-hoc earnings/deductions intended to be included in a specific month’s payroll.
Data: Captures the payment amount, the specific payroll element it relates to, the target employee, the payroll month/year it should be processed in, and its current processing status.
Process Usage:
- Payroll Input: Records in this table are pulled by the payroll engine during the run for the specified PaySlipMonth/PSYear to calculate the final net pay.
- Reimbursement Closure: Marks approved claims or expenses as ready for payment.
Key Points:
- Variable Component: Manages dynamic and one-time payments/earnings that fluctuate month-to-month.
- The PayElementID links the amount to a specific recognized pay type (e.g., “Mobile Reimbursement,” “Travel Allowance”).
Business Impact: Ensures accurate and timely processing of all employee entitlements and deductions outside of the standard salary structure.

Module: HRMS Leave Management
Purpose: Central configuration table that defines comprehensive leave policies and rules for different leave types.
Data: Stores complete policy configurations including allotment rules, application restrictions, carry-forward settings, and special leave provisions.
Process Usage:
- Serves as the master configuration for leave entitlement calculations and validations.
- Used by leave balance engines, application validators, and policy enforcement systems.
Key Points:
- Supports multiple leave types (Paid, Unpaid, Maternity, Paternity, Compensatory Off, Anniversary, Optional Holiday).
- Configures complex business rules including probation restrictions, sandwich rules, and encashment policies.
Business Impact: Critical for accurate leave accruals, compliance with labor laws, and consistent policy application across the organization.

Module: HRMS Document Management
Purpose: Central repository for all document templates used across the HRMS system for automated letter generation.
Data: Each row represents a reusable template for generating various HR documents like offer letters, appointment letters, salary slips, etc.
Process Usage:
- Serves as the blueprint for generating employee-specific documents with dynamic data binding.
- Supports both HTML-based and DOCX-based template formats.
- Enables standardized document creation across the organization.
Key Points:
- Flexible template system supporting multiple document types and formats.
- Integrated notification system for workflow automation.
- Granular control over template visibility and acknowledgment requirements.
Business Impact: Ensures consistency in HR communications, reduces manual effort, and maintains compliance with document standards.

Module: HRMS Attendance & Work Schedule (Audit)
Purpose: Stores an immutable, historical record of all changes to employee work schedule assignments.
Data: Each row records the state of an employee’s schedule allocation (tbl_workscheduleallocation) at the time of a change.
Process Usage:
- Populated by database triggers on CUD operations on the parent allocation table.
- Used for auditing and dispute resolution regarding when a schedule was changed for an employee.
Key Points:
- Essential for compliance to prove which work schedule was assigned to an employee at any point in time.
- Enables point-in-time reconstruction of an employee’s schedule assignments.
Business Impact: Ensures transparency and compliance in scheduling, vital for accurate payroll and attendance.

Module: Objectives and Key results (OKR)
Purpose: Stores the individual question, configuration, and multi-rater responses for the qualitative section of an OKR/Performance review.
Data: Each row represents a specific question posed during the review, including the question title, weightage, and the value, percentage, and comments submitted by the employee (Self), M1, M2, and HR.
Process Usage:
- Linked to a main OKR review record to capture non-KR-specific performance data.
- Used to track and compare scores and qualitative feedback across different reviewers.
Key Points:
- Enables a holistic view of performance beyond just Key Result attainment.
- Critical for behavioral and competency assessments.
Business Impact: Provides the qualitative data necessary for final rating calibration and development planning.

Module: Employee Lifecycle/Confirmation Management - Probation Period Policy Master
Purpose: Stores the active, master rule sets that define the standard duration and application criteria for the employee probation period.
Data: Captures the policy name, the duration in days, the effective date of the rule, and the criteria (e.g., job grade, department) that determine which employees are subject to this policy.
Process Usage:
- Default Setting: Used to determine the default probation end date for a new employee based on their join date and applicable criteria.
- Confirmation Workflow: Feeds the duration into the confirmation process workflow.
- Auditing: Changes to this table trigger a record entry into tbl_ProbationPeriodSetUpHistory.
Key Points:
- Rule Master: This table holds the current, actively used set of rules.
- The ApplicationCriteria field allows for varying probation policies across different employee groups.
Business Impact: Standardizes the initial employment period across the organization, ensuring fairness and compliance.

Module: Asset & Inventory Management (Audit)
Purpose: Provides a complete, immutable audit trail for all changes and lifecycle events of a company asset (e.g., laptop, monitor, license).
Data: Each row captures a full snapshot of the parent asset record (tbl_assets) at the time a significant action occurs (allocation, return, status change).
Process Usage:
- Automatically populated whenever a CUD operation or allocation change occurs on the parent asset table.
- Used by administrators and auditors to review the entire chain of custody and status changes.
Key Points:
- Immutable Log: Ensures data integrity for financial and allocation compliance.
- Snapshot: Stores all core asset, depreciation, and current allocation data at the event time.
Business Impact: Essential for tracking company property, resolving employee/asset disputes, and managing asset depreciation schedules.

Module: HRMS Asset & Inventory Management (Request Workflow)
Purpose: Stores all requests submitted by employees for company assets (e.g., a laptop, a software license, a new monitor) and tracks the multi-stage approval workflow.
Data: Contains the requested asset type, required dates, employee request details, and the status/reason for approval/rejection at each reporting level (Rep1, Rep2, HR).
Process Usage:
- Initiated by an employee needing an asset.
- Guides the request through a multi-step approval chain.
- Upon final approval, facilitates the allocation of a physical asset (linked via allocated_asset_id).
Key Points:
- Manages the lifecycle of a request, from submission to final approval or rejection.
- Distinguishes between the request and the actual allocation.
Business Impact: Ensures controlled, justified, and audited distribution of company resources.

Module: Asset Management - Asset Return Request Workflow
Purpose: Manages the workflow for requesting the return of a company asset from an employee (e.g., due to transfer, replacement, or resignation).
Data: Captures the asset being requested, the reason for the request, the current status of the request, and the HR/Admin personnel responsible for processing it.
Process Usage:
- Workflow Tracking: Initiates and tracks the multi-step process from request creation to final asset receipt and update of the allocation log.
- Accountability: The hr_id ensures clear responsibility for the return process.
- The status field is crucial for tracking progress (e.g., PENDING, APPROVED, REJECTED, RETURNED).
Key Points:
- De-allocation Step: This record precedes the actual update to the tbl_assets_allocation table, acting as the necessary approval step.
- Linked to the specific asset via asset_id.
Business Impact: Provides a structured, auditable process for managing the retrieval of company assets, minimizing loss and ensuring timely reassignment.

Module: Employee Profile
Purpose: Stores employee document information.
Data: One row is created for each document uploaded or mapped to an employee.
Process Usage:
- Captures employee documents for personal, address, qualification, banking, experience, passport/visa, reference, and training certificate records.
- Tracks document metadata such as upload date, file size, and S3 storage location.
Key Points:
- Documents are linked to employees and mapped to document titles.
- Supports various document types based on predefined categories.
Business Impact: Ensures proper storage, tracking, and retrieval of employee documents for HR and compliance purposes.

Module: Objectives and key results (OKR)
Purpose: Stores the definitions and settings for the standardized performance review questionnaires used to evaluate an employee’s OKR achievements at the end of a cycle (or during check-ins).
Data: Captures the template name, the required reviewers (self, Manager 1, Manager 2, HR), and the total count and weightage of the questions included.
Process Usage:
- Review Setup: Used by administrators to define the structure and scope of the OKR review process.
- Workflow Control: The is_ flags determine the mandatory participants in the multi-rater review workflow.
- Provides the metadata for generating the actual review forms whose questions are stored in a related detail table.
Key Points:
- Standardization: Ensures consistent and structured evaluation criteria across the organization.
- Multi-Rater Support: Configures the 360-degree review components.
Business Impact: Critical for fair and formalized OKR performance measurement and feedback.

Module: Payroll - Salary Structure Template
Purpose: Stores the definitions and rules for standardized salary structures. Each record defines a specific compensation framework, including the acceptable range of CTC/Gross Salary and the criteria for its applicability.
Data: Captures the template name, type, min/max financial limits (CTC/Gross), applicability rules, and status.
Process Usage:
- Employee Assignment: Used by HR/Payroll to quickly and consistently assign a defined salary structure to new or existing employees.
- Validation: Enforces minimum and maximum limits for CTC/Gross salary when calculating or assigning compensation.
- The OneToMany relationship links this template header to its detailed components (e.g., Basic, HRA, Deductions) stored in tbl_SalaryStructureTemplateElement.
Key Points:
- Standardization: Ensures equitable and compliant compensation practices.
- Range Control: Manages salary bands through MinCTC, MaxCTC, etc.
Business Impact: Critical for scalable and compliant payroll setup and compensation management.

Module: Employee Profile
Purpose: Stores reference details provided by employees.
Data: One row is created for each reference associated with an employee.
Process Usage:
- Captures reference name, contact details, and email.
- Tracks references for verification and HR processes.
Key Points:
- Links references to employees via employeeid.
- Supports HR verification and historical tracking through the history table.
Business Impact: Ensures proper tracking of employee references for verification, onboarding, and compliance.

Module: Asset Management - Asset Custom Field Values
Purpose: Stores the specific data or values entered for the custom fields that are associated with individual assets. This is the operational data store for all non-standard asset attributes.
Data: Captures the unique combination of an Asset ID and a Custom Field ID, along with the actual value (e.g., Serial Number, Warranty End Date) entered by the user.
Process Usage:
- Data Retrieval: Used to fetch all extended/custom details of a specific asset when viewing its profile.
- Reporting/Filtering: Allows for searching and reporting on asset data using organization-specific custom fields.
- Changes to this table are logged in tbl_assets_custom_field_mapping_history.
Key Points:
- Transactional Data: This is the table that holds the dynamic data collected via the flexible custom field configuration.
- It represents a many-to-many relationship where the value is the payload.
Business Impact: Provides a flexible and powerful way to track detailed, organization-specific information for every managed asset.

Module: Employee Lifecycle/Separation Management - Inactive Employee Request
Purpose: Stores the details of a request to change an employee’s status to inactive (e.g., resignation, termination, long-term leave) and tracks the multi-stage approval workflow for the request.
Data: Captures the employee ID, the reason for inactivation, the requested date of change, and the status and details of up to two reporting manager approvals.
Process Usage:
- Initiated when an event triggers an employee’s separation or long-term status change.
- Tracks the sequential sign-off from managers (Rep1, Rep2) before the final status is recorded in the main employee master.
Key Points:
- Workflow Control: Manages the formal approval process for employee exit/status change.
- The FinalStatus dictates the official status change.
Business Impact: Provides a structured, audited process for managing employee separation and official employment status changes.

Module: Employee Profile
Purpose: Stores historical records of employee bank details.
Data: One row per change in employee bank details.
Process Usage:
- Tracks changes to employee bank details over time.
- Used for approval workflows where HR/admin can approve or reject updates.
Key Points:
- Maintains status and rejection reason for audit and compliance.
- Supports overriding future records and effective date tracking.
Business Impact: Ensures accurate banking information, compliance, and traceability for payroll processing.

Module: HRMS Geo-fencing Module
Purpose: Defines notification rules and recipients for geo-fencing events, enabling targeted alerts for boundary violations, idle time, GPS status changes, and other location-based events.
Data: Each row represents a specific notification configuration that determines who gets notified, how they get notified, and for what type of geo-fencing event.
Process Usage:
- Configures alert recipients and delivery methods for geo-fencing rule violations.
- Supports different notification types (email, SMS, push) and event categories.
- Enables targeted notifications to specific employees or roles for different event types.
Key Points:
- Multi-channel notification support with configurable delivery methods.
- Granular event type classification for precise alert targeting.
- Flexible recipient assignment (specific employees or role-based).
Business Impact: Ensures timely awareness of location compliance issues, enables quick response to attendance anomalies, and provides comprehensive monitoring of field workforce movements.

Module: Learning Management
Purpose: Used to store certificate templates for generating course completion certificates.
Data: One row is created for each unique certificate template design.
Process Usage:
- Utilized by the system to generate certificates dynamically based on stored HTML templates.
- The active template (currently “Template 1”) is fetched by name during certificate generation.
Key Points:
- Stores HTML content with placeholders for dynamic data such as learner name, course title, and completion date.
- Supports scalability for multiple certificate designs in the future.
Business Impact: Enables automated, consistent, and branded certificate generation across the Learning Management module.

Module: Task Management
Purpose: Stores option values and display labels for template custom fields (ENUM-like behavior).
Data: One row is created for each selectable option of a custom field.
Process Usage:
- Used to provide predefined selectable options for custom fields in daily tasks.
- Supports default values and stage-specific options.
Key Points:
- Each option is linked to a specific custom field.
- Tracks creation and modification metadata.

Module: HRMS Role Module
Purpose: Defines the master list of application pages, menus, and their associated permissions for the system navigation structure.
Data: Each row represents a navigable page or menu item with its URL path and default permission flags.
Process Usage:
- Used by the frontend application to dynamically build navigation menus and sidebar components.
- Serves as the foundation for role-based permission assignments in tbl_userrole.
Key Points:
- Supports hierarchical menu structures through parent-child relationships.
- Provides default permission templates that can be customized per role.
Business Impact: Centralizes UI navigation management, enables dynamic menu generation, and provides the base structure for access control configuration.

Module: Objectives and key results (OKR)
Purpose: Stores the specific configuration of questions as they are linked to an active, assigned OKR review cycle or assessment instance.
Data: This table is a snapshot/copy of the master question details, ensuring immutability for live review forms.
Process Usage:
- Review Instantiation: Created when an OKR review cycle is launched and assigned to employees.
- Provides the precise, stable list of questions to be used for a given review, even if the master template is later modified.
Key Points:
- Version Control: Decouples active reviews from future template changes.
- The master_id likely links to the specific assigned review record rather than the master template ID.
Business Impact: Guarantees data integrity and consistency for all in-progress performance reviews.

Module: OKR
Purpose: Stores the high-level categories, themes, or strategic pillars (e.g., Finance, Customer Success, Product Innovation) under which organizational and individual Objectives (Os) are classified.
Data: Captures the unique ID and the name of the strategic category.
Process Usage:
- Alignment & Grouping: Used to categorize objectives for better strategic alignment, filtering, and reporting.
- Goal Setting: Provides a standardized list of strategic focus areas when employees and managers create new objectives.
- Reporting: Allows leadership to analyze the distribution of objectives across different strategic areas of the business.
Key Points:
- Master Data: This table is maintained by administrators to define the structure for goal classification.
- It imposes a strategic framework on the OKR creation process.
Business Impact: Ensures all OKRs are relevant to defined strategic priorities and facilitates clearer organizational reporting and alignment.

Module: HRMS Document Management
Purpose: Stores all employee-generated letters and documents with comprehensive tracking and acknowledgment capabilities.
Data: Each row represents a single letter/document generated for an employee, containing both HTML content and file-based documents.
Process Usage:
- Used for generating offer letters, appointment letters, salary slips, and other HR communications.
- Supports both HTML-based and DOCX template-based document generation.
- Enables employee acknowledgment workflow for critical documents.
Key Points:
- Dual storage approach: HTML content for immediate viewing and file storage for official documents.
- Comprehensive audit trail with creation/modification tracking.
- Flexible publishing controls for ESS portal visibility.
Business Impact: Central repository for all employee communications with legal compliance through digital acknowledgments.

Module: Employee Profile
Purpose: Stores history of employee reference details.
Data: One row is created for each historical version of an employee reference record.
Process Usage:
- Tracks changes to employee reference information over time.
- Captures status, approvals, and rejection reasons.
Key Points:
- Links to the main reference table (tbl_employeereferences) via emprefid.
- Provides an audit trail for HR approval/rejection process.
Business Impact: Ensures proper tracking and approval of employee references, supports compliance and auditing.

Module: HRMS Employee Lifecycle & Performance
Purpose: Manages and tracks the probationary period for individual employees, recording key dates, confirmation status, and any extensions.
Data: Stores the planned probation duration, actual confirmation date, and justifications for any variations from the plan.
Process Usage:
- Used to automate reminders and tasks related to the end of the probation period.
- Provides the historical record for an employee’s initial employment status transition.
Key Points:
- Critical for compliance and documenting the formal decision to make an employee permanent.
- Tracks fields related to extension and final confirmation.
Business Impact: Ensures a structured and legally compliant process for employee confirmation or termination post-probation.

Module: Task Management
Purpose: Stores project information including timelines, estimated effort, and task allocation.
Data: One row per project, capturing project metadata, progress tracking, and employee assignment details.
Process Usage:
- Used to manage projects and track total hours spent on tasks.
- Supports assigning templates, defining priorities, and monitoring milestones.
- Stores watchers (employees monitoring the project) and applicable criteria.
Key Points:
- Tracks project status, priority, and extended deadlines.
- Aggregates task allocation hours for overall project reporting.
Business Impact: Enables project tracking, resource planning, and reporting on time and progress.

Module: HRMS Payroll Management - Hold Salary Audit History
Purpose: Stores an immutable, time-stamped log of all changes and historical states for employee salary hold records (from tbl_HoldSalary). This is a critical audit trail for payroll compliance and dispute resolution.
Data: Captures a snapshot of the held amount, status, period of hold, and intended release period every time the original hold record is created or modified.
Process Usage:
- Auditing: Provides a complete historical timeline of the salary hold lifecycle (from creation to release/cancellation).
- Compliance: Used to prove why, when, and by whom a salary amount was held or released during past payroll cycles.
Key Points:
- Immutability: Records here are generally preserved and not modified.
- The AbstractAuditingEntity parent class provides the necessary audit fields (e.g., CreatedBy, CreatedDate) to show the change details.
Business Impact: Ensures controlled, transparent, and auditable management of withheld employee compensation.

Module: HRMS Notification & Workflow Engine
Purpose: Defines the rules, content, and recipients for automated email notifications triggered by specific system events (e.g., status change, request submission, reminder).
Data: Stores event names, email template IDs for both staff and employees, criteria for recipient targeting, and status flags.
Process Usage:
- Referenced by system services to identify which email to send (template) and to whom (criteria) when a defined event occurs.
- Manages complex notification logic, including whether an employee should also receive the “staff” version of a mail.
Key Points:
- Essential for transactional communication, alerts, and workflow management.
- Provides granular control over who receives which notification variant.
Business Impact: Ensures timely and accurate communication related to HR processes and employee lifecycle events.

Module: HRMS Time & Attendance (Shift Management)
Purpose: Stores the foundational configuration and parameters for all standard and custom work shifts used across the organization.
Data: Defines shift timings, duration, grace periods, and rules for attendance processing.
Process Usage:
- Referenced by the attendance processor to validate employee punches (late-in/early-out) and calculate total working hours.
- Used by scheduling and employee profile management modules to assign shifts.
Key Points:
- Version 1 of the shift master, indicating a potential for future schema evolution.
- Critical for payroll accuracy and labor law compliance.
Business Impact: Ensures consistent application of work hours and attendance rules across the workforce.

Module: HRMS Payroll Compliance - PF Rule History (Audit)
Purpose: Stores an immutable, time-stamped history of the different Provident Fund (PF) statutory rules, contribution rates, and caps that were effective over time.
Data: Captures the rates for employee contribution, the breakdown of employer contributions (Pension Fund/EPS, EPF), administrative charges (EPF AC, EDLI AC), maximum wage caps, and the effective date of the rule.
Process Usage:
- A snapshot record is created whenever a PF rule master (tbl_ProvidentFundRuleDetail) is created or modified.
- Payroll processing queries this table (using the payroll month/year) to retrieve the exact rules applicable for calculating PF deductions and contributions for a given period.
Key Points:
- Statutory Compliance: Essential for audit trails and demonstrating historical adherence to government regulations.
- Effective Date: The EffectiveDate is the key differentiator between historical records.
Business Impact: Ensures payroll accuracy, minimizes compliance risks, and supports historical payroll recalculations.

Module: Separation Management - Workflow Setup Master
Purpose: Stores the configuration rules that define the required steps and timelines for an employee separation (resignation, retirement, termination).
Data: Contains flags for mandatory steps like multi-level approval, departmental clearance, and exit interviews, along with associated timeline parameters.
Process Usage:
- Process Definition: Determines the exact workflow an employee’s separation request must follow.
- Controls the initiation timing of post-resignation tasks like clearance and notification.
Key Points:
- Allows for different separation types (e.g., retirement vs. resignation) to follow different rules (implied by linking this setup to a specific employee group/reason).
- The diff method in the model suggests it is heavily audited for changes.
Business Impact: Standardizes and automates the entire employee exit process, ensuring all compliance and handover steps are followed.

Module: Employee Profile
Purpose: Maintains the historical record of qualifications added or updated by employees.
Data: Stores qualification details submitted by employees, pending HR/Admin approval.
Process Usage:
- When an employee adds or edits qualification details, the record is first saved here.
- HR/Admin reviews the record, approves or rejects it, and then approved data reflects in tbl_employeequalification.
Key Points:
- Supports qualification approval workflow.
- Tracks changes to educational details before they are finalized.
- Maintains remarks for rejected or modified entries.
Business Impact: Ensures that only verified education details are stored in the main qualification record, improving data reliability and audit tracking.

Module: Objectives and Key results (OKR)
Purpose: Stores the current, live definitions and aggregated progress metrics for all high-level Objectives (O) in the Objectives and Key Results (OKR) framework.
Data: Contains the Objective name, period, ownership, and calculated progress figures (completion percentage, status) derived from the linked Key Results (KRs).
Process Usage:
- Objectives are created manually or from templates, defining the strategic focus.
- The completion_percentage and completion_value fields are periodically updated by the system based on the aggregated progress of the associated Key Results.
Key Points:
- Represents the strategic “What” aspect of the OKR framework.
- Acts as the parent record for multiple Key Result records (tbl_okr_key_results).
Business Impact: Provides the central view for tracking strategic goal achievement across the organization, departments, and individuals.

Module: Task Management
Purpose: Maps template assignments to specific employees.
Data: One row is created for each mapping between a template assignment and an employee.
Process Usage:
- tbl_template_assign stores search criteria and template IDs.
- This table links those templates and assignments to employee IDs.
- Facilitates tracking and connection between templates and employees for task management.
Key Points:
- Each mapping links a single template assignment to one employee.
- Supports reporting and search functionality for task assignments.

Module: Employee Profile
Purpose: To maintain a historical record of employee nominee details.
Process Usage:
- Stores nominee information for each employee along with approval status.
- Tracks whether nominee details are Approved, Rejected, or Pending by HR/Admin.
- Maintains remarks for rejected records.
Business Impact: Ensures transparency and traceability of employee nominee details across approval stages.

Module: Asset & Inventory Management
Purpose: Stores the comprehensive master data for all third-party vendors (suppliers) who provide company assets or related services (e.g., maintenance, licensing).
Data: Contains contact information, tax identification numbers (GST/PAN), banking details for payments, and contract specifics.
Process Usage:
- Used as a foreign key (vendor_id) in asset records to track the source of purchase.
- Provides financial data needed for purchase orders, payments, and tax compliance (GST/PAN).
Key Points:
- Centralized repository for vendor relationship management.
- Essential for procurement, finance, and asset auditing.
Business Impact: Streamlines procurement, payment, and financial compliance related to asset acquisition.

Module: HRMS Time & Attendance (Location Management)
Purpose: Stores configuration details for specific, authorized geographical locations where an employee is permitted to perform attendance actions (punch-in/out).
Data: Contains location name, coordinates (latitude/longitude), and required geofencing parameters for validation.
Process Usage:
- Referenced by the mobile application during punch-in/out to check if the employee’s current GPS location is within the defined punchinradius or fencingradius.
- Used to validate and restrict attendance based on defined work locations.
Key Points:
- Critical for ensuring that remote or field employees are reporting from authorized sites.
- Can be used for temporary project sites or permanent work-from-home locations.
Business Impact: Enhances attendance compliance and reduces time theft for non-office-based staff.

Module: HRMS Document Management System
Purpose: Serves as the master repository for all official HR and company documents (e.g., policies, forms, manuals).
Data: Stores metadata, file path, access control, and classification details for each document.
Process Usage:
- Controls which employees can view or download specific documents based on organizational units or roles.
- Used by HR staff to manage the centralized library of official documents.
Key Points:
- Essential for ensuring version control, compliance, and easy employee access to required documents.
- Documents are typically stored on a file server, and this table stores the link and metadata.
Business Impact: Streamlines HR operations and improves employee self-service for information access.

Module: Task Management
Purpose: Stores the actual values entered by users for custom fields in daily tasks.
Data: Each row represents the value of a specific custom field for a daily task.
Process Usage:
- Records user input for text, date, or selectable custom fields.
- For selection fields, stores both the option ID and the selected value.
Key Points:
- Links custom field values to a specific daily task.
- Supports auditing, reporting, and template-based task creation.
Business Impact: Enables accurate capture of user-provided task details and supports data-driven task analysis.

Module: HRMS Asset Management - Asset Type to Custom Field Mapping Master
Purpose: Stores the current, active rules for linking pre-defined custom fields (from tbl_assets_custom_field) to various master asset types (e.g., Laptop, Monitor, Vehicle).
Data: Captures the linkage between a specific Asset Type ID and a Custom Field ID, along with configuration attributes like whether the field is mandatory, public, or active.
Process Usage:
- Form Customization: Used to dynamically generate the asset registration form for a given asset type, ensuring only relevant custom fields are presented.
- Validation: Enforces data integrity by using the is_mandatory flag during asset creation.
Key Points:
- Many-to-Many Linkage: This table serves as the junction between the Asset Type master and the Custom Field definition master.
- The settings here govern the data collection requirements for each asset category.
Business Impact: Enables the organization to collect specific, relevant, and required information for different types of assets, improving inventory detail and audit compliance.

Module: HRMS Geo-fencing Module
Purpose: Stores analyzed geo-fencing event pairs with calculated time durations between location events for employee movement analysis and attendance validation.
Data: Each row represents a time-bound event pair (start and end) with calculated duration, enabling analysis of employee presence, movement patterns, and GPS availability periods.
Process Usage:
- Tracks time durations between related geo-fencing events (GPS ON/OFF, location entries/exits).
- Calculates idle time periods and employee presence duration at locations.
- Provides analyzed data for attendance compliance and movement pattern reporting.
Key Points:<br-**Paired event tracking with start and end location data.
- Automated duration calculation in minutes between events.
- Supports both movement tracking and GPS status change monitoring.
Business Impact: Enables accurate time tracking for attendance purposes, monitors GPS reliability, and provides insights into employee movement patterns and location compliance.

Module: Objectives and Key results (OKR)
Purpose: Stores the specific Key Results (KRs) and Objectives that are part of a defined, reusable OKR template.
Data: Each row represents one KR or Objective, detailing its name, labels, target values, review configuration, and weightage.
Process Usage:
- Used when assigning goals to an employee; these records are copied to the live review tables (tbl_okr_review) to start a new cycle.
- Acts as the configuration layer for goal setting, defining what will be measured and how it will be reviewed.
Key Points:
- Defines the multi-rater requirement (is_self_review, is_m1_review, etc.) for each goal.
- Contains all standard goal metadata (measurement type, frequency, weightage).
Business Impact: Provides the structured, standardized content for annual or cyclical performance goals across the organization.

Module: System Configuration & Utilities (Email)
Purpose: Stores configuration details for automated email notifications and scheduled reports.
Data: Defines the frequency (cycle, day), type, and recipients for system-triggered emails.
Process Usage:
- Referenced by a background scheduler service to determine which emails to send and when.
- Allows administrators to configure recurring notifications without code changes.
Key Points:
- Central control for all scheduled outbound email communication.
- Critical for reminders, system reports, and policy updates.
Business Impact: Ensures timely communication of critical information to stakeholders.

Module: Attendance
Purpose: Stores historical records of employee attendance updates.
Data: One row is created for each attendance update for a specific employee and date.
Process Usage:
- Tracks when an employee’s attendance is updated or reverted.
- Maintains flags for effect removal to indicate whether the update was later reverted.
Key Points:
- Provides an audit trail of attendance changes.
- Useful for compliance, payroll verification, and reporting.

Module: HRMS Transfers & Requisitions
Purpose: Stores the master record for every internal employee transfer or relocation request raised within the organization.
Data: Contains details about the requested move, including the originating and destination organizational units, financial implications, and approval status.
Process Usage:
- Used to track the lifecycle of a transfer request from initiation through final approval/rejection.
- Serves as the primary data source for transfer audit trails and reporting.
Key Points:
- Essential for documenting staffing movements and organizational changes.
- Contains multiple custom fields (com1 through com10) for flexible data capture.
Business Impact: Facilitates controlled and auditable employee mobility across departments, branches, or companies.

Module: HRMS Document Module
Purpose: Tracks document assignments to employees and manages the digital acknowledgment workflow for critical HR documents.
Data: Each row represents a document assigned to an employee that requires formal acknowledgment, capturing the complete digital signature process.
Process Usage:
- Manages the lifecycle of document assignments from assignment to acknowledgment.
- Captures legally compliant digital signatures with audit trail.
- Tracks employee acceptance of policies, agreements, and compliance documents.
Key Points:
- Comprehensive audit trail for legal and compliance requirements.
- Integrated digital signature capture with geo-location and IP tracking.
- Status-based workflow management for document acknowledgment.
Business Impact: Ensures regulatory compliance, provides legal proof of document receipt and acceptance, and automates the acknowledgment process.

Module: HRMS Recruitment & Onboarding
Purpose: Tracks the collection and verification status of all documents required from a candidate after a job offer is made.
Data: One row per required document type for a single job offer.
Process Usage:
- Populated when an offer is generated with a document checklist.
- Updated by candidates via the portal (uploading files) and by HR during verification.
- Used to gate the final “Ready to Join” status.
Key Points:
- Manages mandatory vs. optional documents.
- Stores file paths/links, verification status, and remarks.
- Can handle multiple file uploads for a single document type.
Business Impact: Critical for legal/compliance adherence, background verification, and ensuring a smooth, auditable onboarding process.

Module: HRMS Leave Management (Attendance-Based Allocation Configuration)
Purpose: Defines which day types count towards attendance for pro-rata leave calculations when allocation is based on attendance.
Data: Stores boolean flags indicating which attendance categories should be included in leave entitlement calculations.
Process Usage:
- Used by leave allocation engine when AllotLeaveCountBasedOn.ATTENDANCE is configured.
- Determines the denominator for pro-rata calculations based on actual working days.
Key Points:
- Only relevant when allotment is configured to be attendance-based rather than fixed.
- Controls which types of absences/presences count as “attended” days.
Business Impact: Critical for accurate pro-rata leave calculations for employees with variable attendance patterns.

Module: Employee Profile
Purpose: Stores the history of employee past experience records added or updated by employees.
Data: Each record represents a change or submission in the employee’s experience details.
Process Usage:
- Employees submit new or updated experience entries.
- HR reviews and either approves or rejects these records.
- Once approved, data reflects in tbl_employeeexperience (the main table).
Key Points:
- Tracks organization, designation, duration, and salary on leaving.
- Maintains auditability of all employee experience updates.
Business Impact: Enables HR to verify and manage accurate historical work experience information for employees, essential for validation, appraisal, and background checks.

Module: Payroll Compliance - Form 24Q
Purpose: Stores the consolidated details of the monthly/quarterly tax challans (deposits) made to the government treasury, representing the Tax Deducted at Source (TDS) from employee salaries, necessary for generating the Form 24Q quarterly compliance report.
Data: Captures the period (Financial Year, Quarter, Month), challan identifiers (BSR Code, Serial Number), and the full financial breakdown of the deposited amount (TDS, Surcharge, Cess, Interest, Fees).
Process Usage:
- Generated post-payroll to record tax remittance details.
- Used to populate Annexure 2 (Challan Details) of the Form 24Q return filing.
Key Points:
- Represents a single tax deposit transaction (Challan).
- Essential for statutory compliance and matching TDS deductions with deposits.
Business Impact: Ensures accurate and compliant reporting of TDS on salaries to the Income Tax Department.

Module: HRMS Expense Management
Purpose: Defines complex, multi-criteria payment calculation rules for expense policies, enabling sophisticated amount computations based on multiple conditions and custom fields.
Data: Each row represents a specific payment calculation rule that can be applied to expense claims, supporting fixed amounts, variable calculations, and conditional logic based on custom field values.
Process Usage:
- Configures multiple calculation methods for a single expense policy with conditional application.
- Enables tiered, slab-based, or formula-driven payment calculations.
- Supports integration with custom expense fields for dynamic amount determination.
Key Points:
- Multiple calculation rules per policy with weighted priority system.
- Flexible criteria-based rule application using JSON conditions.
- Support for both fixed amounts and dynamic calculations.
Business Impact: Enables sophisticated expense reimbursement calculations, supports complex policy structures, and provides flexibility for organization-specific payment rules.

Module: HRMS Time & Attendance (Shift Audit Log)
Purpose: Provides a historical, immutable audit log of all modifications made to shift configurations in the public.tbl_shiftmasterv1 master table.
Data: Stores a complete snapshot of the shift record whenever any change occurs, ensuring compliance and trackability.
Process Usage:
- Automatically populated by system triggers or application logic on updates to the shift master table.
- Used for auditing, dispute resolution, and reviewing the exact shift configuration effective on any past date.
Key Points:
- Essential for legal compliance to prove which shift rules were active at a specific time.
- Every row is a unique version of a shift record.
Business Impact: Guarantees transparency and non-repudiation of all shift configuration changes.

Module: Separation - Notice Period Setup History/Audit Log
Purpose: Stores an immutable record of every version and change made to the master Notice Period Policy configurations (tbl_NoticePeriodSetUp).
Data: Captures the policy name, the duration of the notice period (for probation and post-confirmation), the effective date of the policy change, and the specific application criteria.
Process Usage:
- Auditing: Essential for maintaining a historical record of notice period rules for compliance and legal purposes.
- Retrospective Calculation: Used to determine the correct, applicable notice period for an employee based on the policy that was effective on their date of joining or the date of their resignation/termination.
Key Points:
- Immutability: Each record is a snapshot of the policy at a specific point in time.
- Links back to the live setup table via NoticePeriodSetUpId.
Business Impact: Guarantees accuracy and defensibility of notice period calculations (and pay-in-lieu calculations) during employee separation.

Module: HRMS Expense Management
Purpose: Defines comprehensive expense policy rules with configurable limits, frequency controls, and eligibility criteria for different expense types across the organization.
Data: Each row represents a complete expense policy configuration with multi-level limits, submission rules, and calculation methods for specific expense categories.
Process Usage:
- Configures expense eligibility rules and limits for different employee groups.
- Defines submission deadlines, payment cycles, and approval workflows.
- Sets frequency and amount limits across multiple time periods (daily, monthly, quarterly, etc.).
Key Points:
- Multi-dimensional limit system with time-based constraints.
- Flexible eligibility criteria using JSON-based rule engine.
- Integrated payment calculation and variation handling.
Business Impact: Ensures consistent expense policy enforcement, prevents policy violations, and automates expense validation and limit checking across the organization.

Module: HRMS Asset Management - Asset Allocation Log
Purpose: Records the transaction of assigning a specific company asset to an individual employee, serving as the live record of current asset custody.
Data: Captures the unique asset ID, the employee ID it is allocated to, the dates of allocation and expected/actual return, and associated remarks/attachments.
Process Usage:
- Current Status: The presence of an active record (where return_date is null or in the future) indicates the asset is currently in use by the specified employee.
- Asset Tracking: Essential for maintaining an accurate inventory of who holds what.
- Off-boarding: Used during employee separation to identify which assets must be returned.
Key Points:
- Custody Record: This table establishes accountability for company property.
- Linked to the asset master table via asset_id and the employee master via employee_id.
Business Impact: Critical for asset control, loss prevention, and facilitating smooth employee off-boarding and departmental clearance.

Module: HRMS Employee Tracking
Purpose: Provides complete, immutable audit trail for all employee tracking policy assignment changes and historical tracking configurations.
Data: Each row represents a historical record of employee tracking policy assignments, preserving the relationship between employees and their tracking policy versions over time.
Process Usage:
- Automatically populated when tracking policy assignments are created, modified, or deleted.
- Used by administrators and auditors to review historical tracking policy assignments and changes.
- Essential for compliance reporting and tracking policy lifecycle management.
Key Points:
- Maintains historical relationships between employees and tracking policy versions.
- Provides audit trail for tracking policy assignment changes and employee monitoring history.
- Enables reconstruction of tracking configurations at any point in time.
Business Impact: Critical for regulatory compliance audits, employee monitoring history tracking, and maintaining complete audit trail of tracking policy assignments.

Module: Separation - Employee Departmental Clearance Tracking
Purpose: Records the status and details of the required clearance process for a specific departing employee with a particular department (e.g., IT, Finance, Admin).
Data: Captures the clearance ID, the department responsible, the status (Cleared/Pending), the department head responsible for sign-off, and any final remarks.
Process Usage:
- Checklist Tracking: Acts as a line item in the overall employee exit clearance process, ensuring all departmental handovers are completed.
- Workflow Control: The Status field is updated by the department head to certify that the employee has completed all obligations (e.g., returned assets, cleared dues) to that department.
Key Points:
- Audit Trail: Provides auditable proof of the employee’s clearance status from each required department.
- Linked to the overall resignation clearance record (RClearanceID).
Business Impact: Critical for risk mitigation during employee separation, ensuring recovery of company assets and closure of departmental responsibilities.

Module: HRMS Leave Management
Purpose: Defines restrictions preventing specific leave types from being combined in consecutive leave applications.
Data: Stores relationships between leave types that CANNOT be clubbed together in single leave applications.
Process Usage:
- Used during leave application validation to prevent mixing of incompatible leave types.
- Enforces strict leave policies where certain leave types cannot be used consecutively.
Key Points:
- Creates restrictions between incompatible leave types.
- Prevents policy violations in multi-day leave applications.
Business Impact: Ensures compliance with leave policies by preventing invalid leave combinations.

Module: Employee Profile
Purpose: Stores historical records of employee contact information changes.
Data: Each record represents a modification or new entry in the employee contact details submitted by the employee.
Process Usage:
- Tracks proposed updates to employee contact details from Employee Profile → Personal Tab → Contact Details.
- Records include phone numbers, email addresses, and social media links.
- Submitted changes are stored here until reviewed and approved/rejected by HR.
Key Points:
- Approved records are reflected in the main contact information table.
- Supports auditability and change history for employee personal contact data.
Business Impact: Maintains a detailed change history of employee contact details, ensuring compliance, transparency, and traceability of updates.

Module: Resignation Clearance
Purpose: Stores all records for employee-initiated resignation requests.
Data: Captures the employee’s original request details, proposed relieving dates, manager/HR approvals, and the final separation status.
Process Usage:
- Initiated by the employee via ESS.
- Moves through a multi-level approval workflow (Rep1, Rep2, HR).
- Triggers related processes like Department Clearance and Exit Interview.
Key Points:
- Central source of truth for an employee’s separation and clearance status.
- Highly sensitive data, critical for full and final settlement calculations.
Business Impact: Manages the entire employee off-boarding lifecycle, ensuring compliance with notice periods and internal clearance protocols.

Module: HRMS Task/General Management - Template Custom Fields Master
Purpose: Stores the definitions for generic, reusable custom data fields that can be associated with various templates (e.g., Task Templates, Workflow Templates) across the HRIS system.
Data: Captures the field’s internal name, data type, display label, help text, and flags indicating if it is a system default or actively used.
Process Usage:
- Template Design: Administrators select fields from this master list to build customized forms or tasks.
- Form Rendering: Used to determine the appropriate input type (e.g., text box, calendar, dropdown) when a user interacts with a form derived from a template.
Key Points:
- Reusability: Fields are defined once and can be linked to multiple different templates.
- Extensibility: Allows for dynamic extension of data capture capabilities across various modules.
Business Impact: Provides a flexible, low-code way to tailor the HRIS to specific organizational data requirements.

Module: HRMS Role Module
Purpose: Defines granular page-level permissions and access rights for specific roles within the system.
Data: Each row represents a permission setting that grants a role specific capabilities (view, save, edit, delete) for a particular page or menu item.
Process Usage:
- Used by the security interceptor to validate user permissions when accessing application features.
- Enables fine-grained access control beyond basic role assignments.
Key Points:
- Implements role-based permission matrix at the UI component level.
- Supports hierarchical permission structures through parent-child relationships.
Business Impact: Provides precise control over feature access, ensures data security, and enables customized user experiences based on role capabilities.

Module: SMTP
Purpose: Stores SMTP configuration details for companies.
Data: One row per company SMTP configuration.
Process Usage:
- Used to send system-generated emails (HR notifications, offer letters, etc.).
- Contains credentials and server information for email dispatch.
Key Points:
- Supports multiple email accounts (e.g., HR account and offer email account).
- Tracks SMTP server, port, SSL, and authentication details.
Business Impact: Ensures reliable email delivery for HR and operational communication.

Module: HRMS Attendance/Time Management - Daily Attendance and Import History
Purpose: Stores an immutable, detailed historical record of employee daily attendance entries, including the original imported/punched data and any subsequent corrections made by HR or the employee/manager.
Data: Captures the employee ID, the date, the recorded/corrected In and Out times, total hours worked, and flags indicating if the entry resulted from a bulk import or a subsequent change.
Process Usage:
- Auditing: Provides a transparent and auditable trail of attendance data, essential for compliance and resolving time discrepancies.
- Correction Tracking: Used to see the history of a specific daily attendance record in the master table (e.g., tracking the original punch vs. the manually corrected time).
Key Points:
- Data Integrity: Ensures that all attendance modifications are logged.
- The AbstractAuditingEntity parent class captures who made the change and when.
Business Impact: Critical for accurate payroll inputs and robust time management compliance.

Module: Objectives and key results (OKR)
Purpose: Stores the granular definition of questions that belong to a master OKR Review Questionnaire Template.
Data: Captures the full question text, its display sequence, the weight assigned for scoring, and the required format of the answer.
Process Usage:
- Form Content: Used to populate the list of items presented in an OKR performance review form.
- Scoring Logic: The weightage and answer_type are essential inputs for calculating the final review score.
- Links to the template header record via master_id (likely from tbl_okr_questionaries_master).
Key Points:
- Template Component: Defines the specific content of the “questions” part of the OKR review process.
- The structure mirrors that of other template detail tables for consistency.
Business Impact: Ensures that the performance review is standardized, structured, and quantifiable across all employees.

Module: Objectives and Key results (OKR)
Purpose: Stores the definitions and core metadata for all reusable Objectives and Key Results (OKR) templates. These templates define the goal structure and period settings before being assigned to employees.
Data: Captures the template name, frequency, duration, custom labels for Objectives and KRs, and the total summary of goals and weightage contained within the template.
Process Usage:
- Templates are created by HR/Admin users to standardize goal-setting across departments or roles.
- Used as the source for creating new, assigned OKR cycles in tbl_okr_template_assign.
Key Points:
- This table holds the template header; the detailed structure (the actual Objectives and KRs) is likely stored in a related detail table.
- Critical for organizational goal alignment and consistent performance management.
Business Impact: Enables scalable and standardized deployment of the OKR framework.

Module: Attendance
Purpose: Stores detailed records of employee punch-in/out events that were automatically rejected by the system based on predefined business or compliance rules (e.g., out of punch radius punches).
Data: Contains all original punch metadata, including time, location coordinates (lat/long), employee ID, device details (battery status, punch source), and a link to the original tracker record.
Process Usage:
- A record is created when a UserTracker record fails validation and is prevented from being recorded as a valid punch.
- Used for auditing system rejections, troubleshooting, and potentially for manual review/override of invalid punches.
Key Points:
- Quarantine: Acts as a holding area for invalid/untrusted attendance data.
- Mirrors the structure of the live punch table (UserTracker) to preserve all context.
Business Impact: Ensures the integrity and compliance of the official attendance data by isolating problematic entries.

Module: HRMS Employee Information & Safety
Purpose: Stores the contact details of the person(s) to be notified in the event of an employee emergency, accident, or critical health issue.
Data: Records the name, address, phone numbers, and relationship for each designated emergency contact.
Process Usage:
- Essential for use by HR, Security, or Administration staff during an on-site emergency or when an employee is unreachable.
- Often a mandatory field during the onboarding process.
Key Points:
- Critical for ensuring employee safety and compliance with workplace safety regulations.
- Includes provisions for two separate phone numbers for improved reliability.
Business Impact: Facilitates immediate contact with an employee’s family or next-of-kin during a crisis.

Module: Objectives and Key results (OKR)
Purpose: Stores an immutable, time-stamped history of changes made to master OKR templates (the structure of goals, weightage, and review periods).
Data: Captures the template name, frequency, total goals/weightage, and the complete JSON structure of the Objectives and Key Results defined in the template at the time of the change.
Process Usage:
- A new record is created whenever the corresponding live template in tbl_okr_template is created or modified.
- Used for auditing template changes and ensuring that an assigned OKR cycle always uses the exact template definition that was active at the time of assignment.
Key Points:
- Immutability: Essential for compliance and ensuring consistency in goal assignment.
- JSON Content: The template_fields column is critical as it holds the full structural definition of the Objective/KR hierarchy.
Business Impact: Guarantees that historical performance reviews are linked to the correct, original goal definitions.

Module: HRMS Employee Tracking
Purpose: Manages the assignment of tracking policies to individual employees, defining their specific location tracking requirements and monitoring rules.
Data: Each row represents a tracking policy assigned to an employee, linking employee records to their applicable tracking configurations and monitoring rules.
Process Usage:
- Associates employees with specific tracking policies based on role, department, or individual requirements.
- Enables granular control over employee monitoring levels and tracking frequency.
- Supports flexible policy assignment for different workforce segments (field staff, remote workers, office staff).
Key Points:
- Simple many-to-many relationship between employees and tracking policies.
- Enables role-based tracking configuration and compliance requirements.
- Supports dynamic policy updates and employee reassignments.
Business Impact: Ensures appropriate tracking levels for different employee types, maintains compliance with monitoring policies, and enables flexible workforce management.

Module: Employee Profile
Purpose: Stores employee qualification records (degrees, diplomas, ongoing studies).
Data: One row is created per qualification entry for an employee.
Process Usage:
- Employees add qualification details via the profile UI; HR can review and approve changes.
- Records are used in background checks, profile completeness, and reporting.
Key Points:
- Captures institution, subject, duration, scores, and pursuit status.
- Supports auditability when combined with the history table.
Business Impact: Ensures reliable records of employee educational credentials for compliance, hiring verification, and talent management.

Module: HRMS Employee Information & Personal Records
Purpose: Stores the personal and contact details for an employee’s family members, dependents, or designated emergency contacts.
Data: Records the type of relationship, name, occupation, birthdate, and contact number for each related person.
Process Usage:
- Used by HR for emergency contact lists and statutory compliance (e.g., dependent benefits, insurance forms).
- Provides necessary data for benefits administration and compliance reporting.
Key Points:
- Essential for critical communication and legal/insurance purposes.
- Distinguishes between different types of relations (e.g., spouse, child, parent, emergency contact).
Business Impact: Ensures the organization has accurate and up-to-date information for critical situations and employee welfare programs.

Module: Employee Profile
Purpose: Stores historical records of employee certifications and trainings.
Process Usage:
- When an employee adds or updates a certification or training record, it is stored here until approved by HR/Admin.
- Once the record is approved, it is reflected in the main table tbl_employeecertification.
Key Points:
- Tracks all certification and training submissions with approval status.
- Maintains approval/rejection reasons for audit and HR review.
- Enables controlled updates to employee certification data.
Business Impact: Ensures data accuracy and accountability for employee qualifications and training records.

Module: Learning Management
Purpose: Stores details of chapters within a course.
Process Usage:
- Each course consists of multiple chapters, and this table defines each chapter’s metadata and learning content.
- Used by the Learning Management System (LMS) to render video content, textual content, and related materials for learners.
Key Points:
- Linked to tbl_course to represent chapters belonging to a specific course.
- Stores video, thumbnail, and HTML-based learning materials.
- Maintains the display order for sequential course delivery.
Business Impact:
Supports structured learning delivery and modular content management for courses, enabling easy updates, tracking, and learner progress visualization.

Module: HRMS Organizational Management
Purpose: Records the details of every transfer request concerning an employee moving from one team or project to another within the same organization, often without a change in department or location.
Data: Stores the effective date, approval status, and rationale for the team change.
Process Usage:
- Used to update the employee’s current team assignment in the core employee profile.
- Provides an audit trail for all internal team movements.
Key Points:
- Essential for accurate project staffing, cost center allocation, and internal reporting on team distribution.
- Tracks the complete workflow lifecycle of the team transfer request.
Business Impact: Facilitates controlled and documented internal resource mobility.

Module: System/Utility - Pending Email Queue
Purpose: Stores email messages that have been generated by the application but are queued to be sent asynchronously or processed by a batch job (e.g., due to temporary email server downtime, rate limiting, or to improve transactional response time).
Data: Captures a unique ID, the full serialized content of the email message (message_json), and auditing details (who/when the request to send was created).
Process Usage:
- Asynchronous Sending: A scheduled job (daemon/cron) periodically reads records from this table, attempts to send the emails, and then deletes successful entries.
- Recovery: Ensures that critical notifications (e.g., password resets, approval requests) are not lost if the email service is temporarily unavailable.
Key Points:
- Queue Management: Acts as a reliable queue for outbound communication.
- The entire email payload (recipient, subject, body, attachments) is stored in the message_json column.
Business Impact: Guarantees reliable delivery of system notifications and prevents email sending latency from slowing down core application transactions.

Module: HRMS Role Module
Purpose: Defines and manages all user roles and their permissions within the HRMS system.
Data: Each row represents a distinct role with specific access rights and privileges that can be assigned to users.
Process Usage:
- Used by the security framework to determine user permissions and access levels across all system modules.
- Serves as the foundation for role-based access control (RBAC) throughout the application.
Key Points:
- Integrates with the Many-to-Many relationship with users through the user_roles junction table.
- Supports hierarchical role differentiation and company-specific role configurations.
Business Impact: Central to security management, ensures proper segregation of duties, and enables scalable permission management across the organization.

Module: Learning Management
Purpose: Used to store Learning Management Assessment Answers details.
Data: One row is created for each assessment question option.
Process Usage:
- Stores options linked to specific questions.
- Marks whether an option is correct or incorrect.
- Enables accurate score calculation after an assessment is submitted.
Key Points:
- Each option belongs to a specific question.
- Indicates whether the option is correct or not.
- Supports automated result evaluation and analytics.
Business Impact: Ensures assessment accuracy and transparency in user scoring.

Module: HRMS Geo-fencing Module
Purpose: Manages the assignment of geo-fencing rules to individual employees with configurable weightage for attendance calculation and compliance scoring.
Data: Each row represents a specific geo-fencing rule assigned to an employee, defining how their location data should be evaluated for attendance and compliance purposes.
Process Usage:
- Links employees to specific geo-fencing rules and locations.
- Configures rule importance through weightage values for scoring calculations.
- Enables personalized location tracking policies for different employee roles.
Key Points:
- Many-to-many relationship between employees and geo-fencing rules.
- Weightage-based scoring system for compliance evaluation.
- Flexible rule assignment supporting different tracking requirements per employee.
Business Impact: Enables customized location tracking policies, supports role-based attendance rules, and provides weighted compliance scoring for field workforce management.

Module: OKR
Purpose: Stores the individual training modules, articles, or resources (videos, documents) provided to employees to educate them on the Objectives and Key Results (OKR) framework and system usage.
Data: Captures the title/name of the training item, its categorization, and a detailed description or summary of the content.
Process Usage:
- Learning Management: Used by the OKR module to display relevant training materials to users (managers, employees) on how to effectively use the system and methodology.
- Content Organization: Links content to a master category (e.g., “OKR Basics,” “Key Result Measurement”) for easy navigation.
Key Points:
- Resource Hub: Acts as the central hub for self-service learning related to performance goals.
- The description likely contains the content itself, a link to the content, or a summary.
Business Impact: Ensures employees are properly educated on the OKR process, leading to better goal alignment and higher quality OKR submissions.

Module: Asset Management - Asset Type Custom Field Mapping History/Audit Log
Purpose: Stores an immutable, historical record of all changes made to the configuration that links custom fields to specific asset types.
Data: Captures a snapshot of the linkage details (Asset Type ID, Custom Field ID) and the rule attributes (is_mandatory, is_public, is_active) at the time of the change.
Process Usage:
- Auditing: Provides a transparent record to track when and why a custom field’s visibility or mandatory status was changed for a given asset type (e.g., Laptops, Furniture).
- Compliance: Used to verify the mandatory data fields that were required for a specific asset type at any point in the past.
Key Points:
- Snapshot: Each record is a snapshot of the settings from the master tbl_assets_type_custom_field_mapping table.
- The AbstractAuditingEntity parent class captures who made the change and when.
Business Impact: Ensures controlled, traceable, and auditable management of asset data collection requirements.

Module: Employee Profile
Purpose: Stores historical records of employee language proficiency details added or updated by employees.
Process Usage:
- When an employee adds or updates their language proficiency details, the record is stored here until reviewed by HR/Admin.
- Upon approval, the corresponding record is reflected in the main table tbl_employeelanguage.
Key Points:
- Tracks the approval workflow for employee-declared language skills.
- Maintains a record of what the employee submitted and what was approved/rejected.
- Ensures only verified language details are visible in the employee’s official profile.
Business Impact: Enhances data reliability in HR records by enforcing an approval process for language information.

Module: Separation/Resignation Clearance Task/Checklist
Purpose: Stores the individual, low-level tasks (or checklist items) required to complete a specific departmental clearance during the employee resignation process.
Data: Captures the task name, associated assets, the status of the task completion, remarks, and the final sign-off details.
Process Usage:
- Links to a parent departmental clearance record (RClearanceId, likely pointing to tbl_ResignationClearance).
- Used to track the detailed handovers, such as returning specific assets (e.g., Laptop, ID Card) or clearing specific responsibilities.
- The status of these tasks contributes to the final status of the parent departmental clearance.
Key Points:
- Granular Control: Provides a detailed, auditable checklist for the exit process.
- Asset Handover: Directly links clearance tasks to specific company assets via asset_id.
Business Impact: Ensures all company property is recovered and all departmental responsibilities are handed over properly upon employee separation.

Module: Learning Management
Purpose: Stores assessment details for chapters within a course.
Data: Each row represents an assessment linked to a specific chapter.
Process Usage:
- Defines assessment information for chapters in the Learning Management module.
- Used to connect with the question table (tbl_question) to define assessment questions.
Key Points:
- Ensures structured evaluation for each learning chapter.
- Supports pass/fail configuration and grading criteria.
Business Impact: Provides a foundation for measuring learner understanding and performance within each course chapter.

Module: Employee Profile
Purpose: Categorizes and defines the various document titles used across the Employee Profile module.
Data: Each record represents a specific document title configuration (e.g., Aadhaar Card, PAN Card, Qualification, etc.).
Process Usage:
- Serves as a master table for document categorization across the employee profile.
- Defines whether a document type is mandatory and what type of mapping it belongs to.
- Used by multiple submodules like Qualification, Experience, Address Proof, and Identification documents.
Key Points:
- Helps organize employee documents logically and consistently.
- Maintains attributes such as document requirement, verification need, and upload rules.
Business Impact: Ensures uniform categorization and validation of all employee-related documents across the HRMS system.

Module: Objectives and Key results (OKR)
Purpose: Stores an immutable, historical snapshot of a Key Result (KR) whenever its status, definition, or progress metrics are updated in the main tbl_okr_key_results table.
Data: Records all KR definition details, target values, ownership, and, most importantly, the progress metrics (latest check-in value, date, percentage) at the time of the change event.
Process Usage:
- A new record is created automatically upon every KR check-in or when the KR’s structural properties are modified.
- Used for auditing goal changes, tracking progress trends over time, and resolving disputes regarding check-in values.
Key Points:
- Immutable Log: Guarantees a time-stamped history of every KR state.
- Snapshot: Mirrors all fields from the live KR table to preserve context for the audit event.
Business Impact: Provides a transparent and verifiable record of goal achievement progress throughout the OKR cycle.

Module: Performance/Confirmation Management - Probation Rating Master Scale
Purpose: Stores the defined rating scale and their specifications used across probation review forms within the organization.
Data: Captures the numeric value (if applicable) and the descriptive meaning (Specification) of each rating level (e.g., Number=4, Specification=“Exceeds Expectations”).
Process Usage:
- Form Population: Used to populate the selectable options for evaluators when scoring performance on a probation review form.
- Standardization: Ensures a consistent and standardized scoring mechanism across all reviews associated with a specific form.
- Linked to a specific form (FormID) for context and the company (CompID) for multi-tenant isolation.
Key Points:
- Rating Definition: Defines the criteria for performance assessment.
- The Number field provides the quantifiable score, while Specification provides the qualitative description.
Business Impact: Ensures fair, consistent, and structured evaluation of employee performance during the crucial probation period.

Module: Probation Management - Probation Review Category Master
Purpose: Stores the high-level categories or sections used to group and organize questions within a structured employee probation assessment form.
Data: Captures the display name of the category (e.g., “Technical Competence,” “Cultural Fit”), its association with a specific form, and its active status.
Process Usage:
- Form Structuring: Used to group individual tbl_ProbationQuestion records, making the review form logical and easy to navigate.
- Scoring: Categories often represent weighted sections in the final probation score calculation.
- Linked to a list of rating options via probationRatingList (Implied FK).
Key Points:
- Organizational Structure: Defines the dimensions of performance being evaluated during probation.
- Multi-tenant setup via CompID.
Business Impact: Standardizes the framework for evaluating new employee performance, ensuring all key areas are assessed.

Module: Employee Profile
Purpose: Stores passport and visa details for employees.
Data: One row is created for each passport or visa record associated with an employee.
Process Usage:
- Maintains information about employee immigration documents.
- Tracks issue and expiry dates for compliance and HR management.
Key Points:
- Supports tracking of both passports and visas.
- Provides additional comments for internal reference.
Business Impact: Ensures HR compliance, visa/passport tracking, and accurate employee documentation.

Module: HRMS Time & Attendance (Notification Audit Log)
Purpose: Stores the historical, immutable audit log of all changes made to individual employee attendance notification preferences in public.tbl_attendancenotification.
Data: Contains a snapshot of the notification settings (type, frequency, channel) at the time a modification was made.
Process Usage:
- Used for auditing and compliance to track who changed an employee’s notification settings and when.
- Essential for troubleshooting issues where an employee claims they did or did not receive specific alerts.
Key Points:
- Ensures accountability for changes to user-specific communication preferences.
- The id in this history table is unique for each change event.
Business Impact: Provides a transparent record of all configuration changes affecting automated attendance alerts.

Module: Attendance - Shift Group Assignment History
Purpose: Stores an immutable, historical record of changes to the composition of Shift Groups. It logs the assignment of individual shifts (from tbl_ShiftMasterV1) to master shift groups.
Data: Captures the unique ID of the specific shift, the ID of the shift group it was assigned to, and a reference ID to the master shift’s configuration history (ShiftMasterV1HistoryId) for contextual auditing.
Process Usage:
- Auditing: Provides a complete timeline of how shift group definitions have changed over time, which is critical for retrospective analysis of attendance rules.
- Compliance: Used to verify which shift rules were active for an employee on a specific date based on their assigned shift group.
Key Points:
- Mapping History: Tracks the many-to-many relationship changes between Shift Master and Shift Group Master tables.
- The AbstractAuditingEntity parent class captures the user and time of the change.
Business Impact: Ensures controlled, traceable, and compliant management of shift scheduling and attendance rules.

Module: Employee Profile
Purpose: Stores history of guarantor details for employees.
Data: One row per update or modification of a guarantor record.
Process Usage:
- Tracks modifications to guarantor information.
- Maintains status and rejection reasons for approval workflows.
Key Points:
- Supports audit and rollback of guarantor data.
Business Impact: Ensures HR compliance and traceability of guarantor changes.

Module: HRMS Geo-fencing Module
Purpose: Defines comprehensive geo-fencing rules for employee location tracking, attendance validation, and movement monitoring with configurable notifications and compliance controls.
Data: Each row represents a complete geo-fencing rule configuration including location boundaries, notification triggers, punch validation, and employee eligibility criteria.
Process Usage:
- Configures virtual boundaries for employee attendance and location compliance.
- Defines notification rules for movement, idle time, and GPS status changes.
- Controls punch-in/out validation and exception handling across different platforms.
Key Points:
- Multi-location geo-fencing with configurable boundaries and tolerances.
- Cross-platform support (Mobile/Web) with different rule sets.
- Comprehensive notification system for compliance monitoring.
Business Impact: Ensures accurate attendance tracking, enables field employee monitoring, provides real-time compliance alerts, and maintains location-based workforce management.

Module: HRMS Leave Management
Purpose: Maintains complete historical record of leave carry forward, lapse, and encashment operations performed during year-end processing.
Data: Stores annual leave balance adjustments including carried forward amounts, lapsed leaves, and encashed balances.
Process Usage:
- Tracks year-end leave balance processing for compliance and audit purposes.
- Provides historical data for employee queries and dispute resolution.
- Supports reporting on leave utilization patterns over multiple years.
Key Points:
- Captures multiple carry forward scenarios (regular, tenure-based, with expiry).
- Maintains separate tracking for lapsed and encashed leave balances.
Business Impact: Essential for financial auditing, compliance reporting, and transparent leave balance management.

Module: General Details
Purpose: Stores currency master details.
Data: One row is created for each currency.
Process Usage:
- Maintains a list of currencies used in the system.
- Captures currency full name and related metadata.
Key Points:
- Used in financial transactions and reporting.
- Most columns are reserved for future use or internal code logic.
Business Impact: Ensures consistency and proper identification of currencies across applications.

Module: Task Management
Purpose: Stores historical snapshots of custom field values for daily tasks.
Data: Each row represents a version of a custom field value at a specific point in time.
Process Usage:
- Tracks changes to custom field values in daily tasks.
- Supports auditing and rollback of user-entered data.
Key Points:
- Links historical values to the corresponding daily task and task history.
- Maintains option IDs and values for selection-type fields.
Business Impact: Ensures accountability and traceability for changes in task data, aiding reporting and compliance.

Module: Performance/OKR Management - Rating Scheme Master
Purpose: Stores the high-level definitions for various rating scales or evaluation schemes (e.g., 5-point scale, 3-point scale, OKR 0.0-1.0 achievement scale) used across the performance and goal management modules.
Data: Captures the unique name and a descriptive context for each defined rating scheme.
Process Usage:
- Selection: Allows administrators to select and assign a specific rating scheme to different performance reviews, OKR cycles, or employee groups.
- Configuration Linkage: This record serves as the header for a set of detailed rating levels (which would be stored in a related detail table like tbl_rating_scheme_detail).
Key Points:
- Standardization: Enables the organization to use multiple, standardized methods for evaluating performance.
- This table defines the type of scale, not the individual levels (e.g., Excellent, Good).
Business Impact: Ensures flexibility and consistency in performance appraisal and OKR scoring across the entire organization.

Module: Payroll Compliance - Form 24Q Challan Details
Purpose: Stores the detailed information about the tax amount (TDS) deducted from employee salaries and subsequently deposited to the government, on a month-by-month, challan-by-challan basis, for inclusion in the quarterly Form 24Q compliance filing.
Data: Captures the breakdown of the deposited tax amount (TDS, Cess, Interest, Fee, Penalty), the deposit mode, bank details (BSR Code, Challan Serial No.), and the verification details.
Process Usage:
- Used to generate Annexure 2 (Challan Details) of the quarterly Form 24Q return.
- Tracks the complete payment lifecycle from salary deduction to government deposit.
Key Points:
- Each record relates to a single tax challan deposit for a specific month/year.
- Crucial for statutory compliance verification and preventing errors in tax credit allocation.
Business Impact: Essential for accurate and timely submission of quarterly TDS returns and for ensuring employees receive the correct tax credit.

Module: Payroll - Payroll Cycle Configuration Master
Purpose: Defines the complete scheduling and processing rules for different payroll cycles (e.g., Monthly, Weekly) across various organizational units.
Data: Captures the cycle type, effective date, cutoff day for pay period, and tentative dates (as day numbers) for crucial payroll steps like attendance processing and final pay date.
Process Usage:
- Scheduling Engine: Used by the system to determine the exact dates for a given month/period, ensuring consistency in payroll execution.
- Timeline Communication: Provides the key dates for HR and employees regarding attendance submission, approval deadlines, and salary payment.
Key Points:
- Frequency Control: cycleType defines the pay frequency (Monthly, Bi-weekly, etc.).
- Date Rules: The various Date fields (as day integers) are used to dynamically calculate the actual calendar dates for each payroll run.
Business Impact: Ensures timely, consistent, and compliant management of the recurring payroll process.

Module: OKR
Purpose: Stores the global, tenant-specific settings and rules that govern the Objectives and Key Results (OKR) management process.
Data: Captures critical configuration parameters such as who manages the OKR process (hr_ids), when the annual/company cycle begins, the maximum achievable rating limit, and the weightage given to different reviewers.
Process Usage:
- Process Control: Dictates the fundamental parameters for OKR creation, review timing, and scoring calculations.
- System Limits: The max_final_percentage_limit ensures that final employee OKR scores adhere to organizational rating guidelines (e.g., preventing scores over 100%).
- Assignment: The hr_ids field is used to identify the responsible administrators/HR personnel for OKR oversight.
Key Points:
- Global Settings: These configurations apply organization-wide or to a specific tenant company.
- Flexibility in defining the review structure (reviewer_weightage).
Business Impact: Standardizes the OKR methodology, ensures consistency in performance goal setting, and controls the final scoring outcomes.

Module: Employee Profile
Purpose: Maintains historical records of employee passport and visa details.
Data: Stores changes or new entries made by employees before HR/Admin approval.
Process Usage:
- When an employee adds or modifies passport or visa information, the record is stored here first.
- HR/Admin reviews the record and updates the main table (tbl_employeeimmigration) upon approval.
Key Points:
- Supports an approval workflow for immigration data.
- Preserves a history of all employee-submitted immigration details.
- Includes approval status and rejection reasons for audit tracking.
Business Impact: Ensures that only verified passport and visa details are reflected in official HR records, improving compliance and data integrity.

Module: Objectives and Key results (OKR)
Purpose: Stores the summary and overall status of an employee’s Objective and Key Results (OKR) review cycle.
Data: Contains high-level information like the review period, total tasks, overall weightage, and the current status of each reviewer (Self, M1, M2, HR).
Process Usage:
- A new record is created when an OKR review period starts.
- Used to track the progress of the multi-level review workflow.
- Calculates the final overall review percentage after all steps are complete.
Key Points:
- Acts as the parent record for the tbl_okr_review details.
- Statuses (self_status, m1_status, etc.) govern the workflow flow.
Business Impact: Essential for managing performance review cycles, determining final scores, and feeding into appraisal processes.

Module: Payroll - Hold Salary Tracking
Purpose: Records instances where a specific amount of an employee’s salary is intentionally withheld or put on hold for a given payroll month, and tracks its subsequent status and release plan.
Data: Captures the employee, the payroll period the amount was held, the amount held, the current status of the hold, and the intended release period.
Process Usage:
- Payroll Calculation: The amount recorded here is deducted from the net pay during the designated Month/Year payroll run.
- Release Tracking: Used to monitor when the held amount is to be processed and paid out in a future payroll cycle (ReleaseMonth/ReleaseYear).
Key Points:
- Financial Control: Essential for managing salary advances, final settlements, and other scenarios requiring temporary withholding.
- The HoldSalaryStatus drives the processing logic.
Business Impact: Ensures controlled and auditable management of withheld employee compensation.

Module: Employee Profile/Edit Profile - Employee Self-Description
Purpose: Stores the employee’s personal, often free-text, description or narrative about themselves, their interests, professional summary, or skills (the “About Me” section of a profile).
Data: Captures the unique ID, the employee ID, the related company ID, and the text content of the employee’s self-description (SelfDetail).
Process Usage:
- Profile Display: Used to populate the “About Me” section on an employee’s internal profile, often visible to colleagues and managers.
- Directory/Search: Provides unstructured text that can be used to search for employees based on skills or interests not captured in formal fields.
- Personalization: Allows employees to add a personal touch to their official HR record.
Key Points:
- Unstructured Data: The SelfDetail column is free-text, not a structured data point.
- Linked to the employee master record via EmployeeID.
Business Impact: Enhances internal networking, team building, and understanding of employee capabilities beyond their job title.

Module: Asset Management - Custom Field Value History/Audit Log
Purpose: Stores an immutable, time-stamped log of all changes made to the values of custom fields associated with specific company assets (e.g., changing the asset’s location, updating a license key).
Data: Captures the linkage IDs, the specific asset ID, the custom field ID, and the value (custom_field_value) of that field at the time the change occurred.
Process Usage:
- Auditing: Provides a complete timeline of how an asset’s descriptive data has changed over its lifecycle (e.g., who updated the service tag, when a warranty date was extended).
- Data Integrity: Used to track data modifications and ensure accountability for changes to critical asset details.
Key Points:
- Value Tracking: This table tracks the content of the asset data, unlike other history tables which track configuration changes.
- Acts as a snapshot of the record from the master tbl_assets_custom_field_mapping table.
Business Impact: Critical for asset compliance, warranty tracking, and maintaining a verifiable history of all asset specifications and statuses.

Module: HRMS Employee Tracking
Purpose: Stores summarized trip information for employees, capturing travel periods, distances, and expense claim status for automated expense processing.
Data: Each row represents a completed trip or travel period with calculated distance and expense generation status, serving as the bridge between tracking data and expense claims.
Process Usage:
- Aggregates raw tracking data into meaningful trip segments with calculated distances.
- Tracks expense claim generation status for automated travel reimbursement.
- Provides trip-level context for travel pattern analysis and expense validation.
Key Points:<br-**Trip-level aggregation of tracking data with distance calculations.
- Integration point between location tracking and expense management systems.
- Automated expense claim generation tracking and status management.
Business Impact: Enables automated travel expense processing, provides trip-level analytics for travel patterns, and ensures accurate distance-based reimbursement calculations.

Module: Learning Management
Purpose: Stores historical snapshots of chapter details whenever updates occur.
Process Usage:
- Tracks changes made to chapters, such as title, content, or video updates.
- Used for auditing, rollback, or content version tracking purposes.
Key Points:
- Maintains historical versions of chapters without affecting active content.
- Contains all key chapter fields for accurate reconstruction of past states.
Business Impact:
Improves auditability and content governance by preserving historical versions of learning materials.

Module: Objectives and Key results (OKR)
Purpose: Stores the master library of all available Objectives and Key Result (KR) definitions that can be selected and configured when creating any specific OKR template.
Data: Contains generic definitions, default targets, and review settings for potential goals/metrics.
Process Usage:
- Acts as the source library from which items are selected and copied into tbl_okr_template_fields_assign for use in a specific template.
- Facilitates the creation and reuse of standardized organizational goals.
Key Points:
- Represents a pool of potential goals, not goals assigned to a template.
- Defines the default properties for objective naming, measurement, and review processes.
Business Impact: Ensures consistency and standardization of goal language and metrics across all OKR templates.

Module: Task Management
Purpose: Maintains history of task changes from tbl_task.
Data: Each entry represents a snapshot of a task whenever a modification occurs.
Process Usage:
- Tracks changes in task metadata, description, deadlines, and attachments.
- Provides audit trail for task management and compliance.
Key Points:
- No foreign keys for review_id in history table; snapshot is independent.
- Useful for reports, rollback, and auditing purposes.
Business Impact: Ensures traceability and accountability in task management processes.

Module: Task Management
Purpose: Stores daily task information assigned to employees.
Data: One row per task, containing task metadata, assignment info, attachments, and timing details.
Process Usage:
- Used to track tasks assigned to employees, including recurring and non-recurring tasks.
- Supports linking to projects, templates, and sub-tasks.
- Stores attachments in JSON format for screenshots or other files.
Key Points:
- Tracks total time spent on the task and extended deadlines.
- Supports hierarchical tasks with recurring parent references.
- Linked to tbl_task_hours for individual employee effort tracking.
Business Impact: Enables task management, progress tracking, and reporting for projects and daily operations.

Module: OKR
Purpose: Stores the planned target or achieved progress percentage for a specific Objective (O) for each month within the active OKR cycle. This enables time-phased tracking and calculation of progress over the quarter or year.
Data: Captures the unique objective ID, the specific month and year, and the corresponding percentage value (either planned weightage or achieved progress).
Process Usage:
- Monthly Progress: Used to aggregate and display the monthly contribution to the overall Objective progress.
- Forecasting/Target Setting: Can be used to store a planned distribution of effort/expected achievement across months (e.g., 20% in Month 1, 30% in Month 2, 50% in Month 3).
- Reporting: Essential for generating graphs and reports that visualize progress trends over time.
Key Points:
- Time-series Data: This table is crucial for time-based analysis of OKR performance.
- Linked directly to the master Objective table via objective_id.
Business Impact: Provides granular visibility into the execution cadence of goals, allowing managers to identify and correct deviations from the plan early.

Module: Separation - Resignation Clearance
Purpose: Stores individual clearance tasks that must be completed by various departments (e.g., IT, Finance, Library) for a specific employee undergoing the exit/resignation process.
Data: Contains the department assigned, the specific point-of-contact (POC) for the task, the status of the clearance (pending/completed), and general remarks.
Process Usage:
- Links to the overall resignation case header (RCHeaderID).
- Each record represents one mandatory clearance step (e.g., “Clear IT Assets,” “Settle Dues”).
- Used to track the overall progress of the employee’s exit process.
Key Points:
- The central table for managing the workflow and status of departmental sign-offs.
- Status is updated by the assigned department POC.

Module: HRMS Role Module
Purpose: Provides a complete, immutable audit trail for all changes to role definitions and configurations.
Data: One row is created for each significant modification to a role record in tbl_rolemaster.
Process Usage:
- Automatically populated by application logic when role properties are updated.
- Used by administrators and auditors to track the evolution of role permissions and settings over time.
Key Points:
- Maintains historical integrity of role changes for compliance and troubleshooting.
- Stores snapshots of role data at the time of each modification event.
Business Impact: Essential for security audits, change management, and understanding the historical context of permission changes.

Module: Learning Management
Purpose: Maintains version history for course records stored in tbl_course.
Data: Each entry represents a snapshot of a course’s state whenever modifications occur in the main course table.
Process Usage:
- Tracks changes in title, category, deadline, and other course metadata.
- Enables audit trail and rollback capability for compliance and administrative purposes.
Key Points:
- Linked to main table by course_id.
- Used for historical reference, analytics, and change audits.
Business Impact: Supports accountability and traceability in course management workflows.

Module: HRMS Time & Attendance (Work Schedule Master)
Purpose: Stores the current, master configuration for different employee work schedules used across the organization.
Data: Defines required working hours (daily/weekly/monthly), flexible work settings, and the calculation basis for attendance and leave.
Process Usage:
- Directly referenced by the attendance processing engine to calculate an employee’s daily and period attendance status (e.g., present, half-day, absent).
- Linked to employee records to apply specific working hour rules.
Key Points:
- Critical for payroll accuracy, compliance with labor laws regarding work hours, and standardizing scheduling rules.
- Supports configuration for both fixed and flexible work arrangements.
Business Impact: Ensures fair and compliant tracking of employee working time.

Module: OKR
Purpose: Stores the actual data values entered into custom fields specifically configured for an OKR Key Result, representing the current or latest state of that custom data.
Data: Links a specific Key Result (key_result_id) to a custom field definition (custom_field_id) and records the value (custom_field_value) provided by the user.
Process Usage:
- Live Data: Used to fetch the current values for a Key Result’s custom attributes when viewing or updating the OKR.
- Dynamic Fields: Provides flexibility to track non-standard attributes necessary for OKR tracking and evaluation.
Key Points:
- Value Store: This table holds the instance data/values, not the field definition itself.
- Likely Current State: This table tracks the live, ongoing data for the custom fields attached to a Key Result.

*Module: Performance Management System (PMS) - Form Master
Purpose: Stores the configuration details for various performance or review form templates (e.g., Annual Review Form, Probation Review Form).
Data: Defines the form’s name, key terminology (KRA/KPI labels), review flow, and whether weightages are used.
Process Usage:
- Used as a blueprint when initiating a new performance review or probation confirmation review.
- Links to PmsPerspective to define the sections/perspectives within the form.
Key Points:
- Centralizes form design, ensuring consistency across different performance cycles.
- LevelOfAssessment dictates the number of reviewers (Self, M1, M2, HR).
Business Impact: Foundation for all structured performance and confirmation reviews.

Module: HRMS geo-fencing Module
Purpose: Defines the association between geofencing rules and physical work locations to enforce location-based attendance policies.
Data: Each row represents a unique assignment of a geofencing rule to a specific employee work location.
Process Usage:
- Used by the mobile app and backend services to determine applicable geofencing rules for check-in/check-out validation.
- Managed by administrators to configure which rules apply to which physical locations.
Key Points:
- Enforces unique combinations of rules and locations through a composite unique constraint.
- Serves as the configuration backbone for location-based access control and attendance tracking.
Business Impact: Ensures accurate location validation for attendance, prevents time fraud, and maintains compliance with work-site policies.

Module: Confirmation - Probation Period Setup History/Audit Log
Purpose: Stores an immutable record of every version and change made to the master Probation Period Policy configurations (from a related tbl_ProbationPeriodSetUp table).
Data: Captures the policy name, the duration of the standard probation period, the effective date of the policy, and the specific criteria used to determine which employees the policy applies to.
Process Usage:
- Auditing: Provides a historical record of probation rules for compliance, legal defense, and ensuring correct policy application to employees based on their joining date.
- Retrospective Lookup: Used to look up the correct probation duration policy that was in effect for an employee at the time of their hiring.
Key Points:
- Immutability: Each record is a snapshot of the policy at a specific point in time.
- Links back to the active setup table via ProbationPeriodSetUpId.
Business Impact: Ensures consistent, accurate, and compliant application of probation policies during the employee confirmation cycle.

Module: Employee Profile
Purpose: To store employee current and permanent address details.
Data: One row is created per employee to hold current and permanent address fields as entered via the Profile Approval page or directly by admins.
Process Usage:
- Stores address details submitted from the profile approval workflow or admin UI.
- Used for contact information, mailing, and identity verification.
Key Points:
- Contains both current and permanent address fields and related metadata.
Business Impact: Ensures accurate contact information for employees and supports HR workflows, compliance, and communication.

Module: Asset Management - Asset Type to Employee Eligibility Mapping
Purpose: Stores the rules defining which specific asset types (e.g., Laptop, Desk Phone, Company Car) are allocated, available to, or authorized for an individual employee.
Data: Captures a mapping between a specific Asset Type ID and an Employee ID.
Process Usage:
- Authorization/Eligibility: Used during asset allocation or request processes to validate if a given employee is allowed to possess or request an asset of a particular type.
- Default Allocation: May be used to pre-define the standard set of assets an employee should receive upon joining (e.g., all new hires get a “Standard Laptop” asset type).
Key Points:
- Many-to-Many Relationship: An employee can be mapped to multiple asset types, and an asset type can be mapped to many employees.
- Acts as a dynamic eligibility check rather than a static allocation record.
Business Impact: Ensures controlled distribution of company resources and streamlines the onboarding/asset request process by enforcing eligibility rules.

Module: HRMS Employee Lifecycle & Compensation
Purpose: Records the details of every promotion, vertical movement, or band/level change approved for an employee.
Data: Stores the effective date, new position details, and associated metadata for each promotion event.
Process Usage:
- Used to update the employee’s active designation, pay cadre, band, and level in the core employee master table.
- Provides a historical log for career progression and salary review/audit processes.
Key Points:
- Essential for tracking employee growth, managing compensation changes, and calculating tenure in position.
- Includes a flag to confirm if the promotion has been fully implemented across all dependent systems.
Business Impact: Ensures accurate reflection of organizational hierarchy and compensation structure for each employee.

Module: HRMS Document Workflow & Communication
Purpose: Stores predefined questions, reasons, or communication templates that are prompted to a user when they accept, reject, or acknowledge an official system-generated letter.
Data: Links text/questions to a specific type of letter and its acceptance status.
Process Usage:
- Used by the UI to dynamically prompt the user for required input (e.g., “State your reason for rejection”) when changing the letter status. br>Key Points:
- Critical for compliance workflows where a formal record of the user’s reason for action is required.
- The questions field likely contains the text or structured data for the user prompt.
Business Impact: Ensures consistent data collection and provides auditability for all official letter communications.

Module: Attendance - Captured Image Storage
Purpose: Stores images captured from an employee (typically via a webcam or mobile camera) during login, logout, or at random intervals as part of a system designed for remote work compliance and attendance verification.
Data: Captures the unique ID of the image record and the Base64 encoded string of the actual image data.
Process Usage:
- Verification: Used to visually confirm the identity and presence of the employee during clock-in/out or while marked as “working.”
- Auditing: Provides a visual audit trail for attendance logs and can be tied back to specific clock-in/out events (though the linkage ID is implicitly handled through a related table or the audit fields).
Key Points:
- Sensitive Data: Contains personally identifiable data (PII) and requires strict security and retention policies.
- Base64 Storage: The image is stored as a large text string for database compatibility and retrieval.
Business Impact: Supports compliance and ensures accountability for time worked, particularly in remote or non-office environments.

Module: Payroll Compliance - Professional Tax (PT) Deduction Detail
Purpose: Stores the detailed, calculated monthly Professional Tax deduction amount for each employee, linking the deduction to the relevant payroll period and compliance accounts.
Data: Captures the employee ID, the SBU, the payroll month/year, the state PT account number, and the deducted tax amount.
Process Usage:
- Generated during the payroll calculation run for each month.
- Provides the necessary granular data for generating monthly/quarterly Professional Tax compliance returns and remittances.
Key Points:
- State Tax: Crucial for managing the state-specific statutory compliance related to Professional Tax.
- Links the calculated deduction amount to the governing rule and organizational structure.
Business Impact: Ensures compliance with state-specific Professional Tax laws and accurate deduction from employee salaries.

Module: Timesheet
Purpose: Stores project/task details for employees.
Data: One row per project or task assigned to employee(s).
Process Usage:
- Tracks projects or tasks, including descriptions, priorities, stages, and estimated hours.
- Can assign specific employees or entire departments.
- Supports watchers to monitor task progress.
Key Points:
- Stores both recurring and non-recurring projects.
- Includes S3 attachment references.
- Allows tracking of task stage and priority.
Business Impact: Enables detailed project planning, timesheet tracking, and resource management.

Module: HRMS Attendance & Timekeeping
Purpose: This is a mapping table that assigns a specific attendance policy to an individual employee.
Data: Each row represents a single, explicit link between one employee and one attendance policy.
Process Usage:
- Used when an employee requires a policy different from the default (e.g., a default policy might apply to their Grade or Location, but this table overrides it).
- When the daily attendance process runs, it checks this table first for an employee. If a record exists, it uses the “policyid” found here.
- If no record exists, the system falls back to the default policy.
- Populated by an HR Admin via an “Assign Policy to Employee” screen.
Business Impact: Provides granular, per-employee control over attendance rules. Essential for managing exceptions (e.g., special rules for part-timers, senior management, or specific roles).

Module: Asset Management - Custom Field Options Master
Purpose: Stores the pre-defined, selectable options (e.g., choices for a dropdown or radio buttons) for custom fields where the field_type in tbl_assets_custom_field is a selection type (Dropdown, Multi-select, etc.).
Data: Captures the display value of the option, links it to its parent custom field definition, and specifies its active/default status.
Process Usage:
- Form Rendering: Used to populate the list of choices presented to the user when filling out a custom field for an asset.
- Data Standardization: Ensures that asset data is captured using a controlled set of standardized values (e.g., only “Windows 10” or “Mac OS” for an “Operating System” field).
Key Points:
- Detail Configuration: Acts as a detail table for the custom field definition master.
- The option_value is the actual text/value that is stored or displayed.
Business Impact: Improves data consistency and quality in asset records by restricting input to approved choices.

Module: HRMS Communications & Announcements
Purpose: Stores all formal internal communications, notifications, and events intended for various employee groups.
Data: Contains the content, schedule, targeting, and status of published announcements.
Process Usage:
- Used by the system to display announcements on employee dashboards and push notifications.
- Manages the scheduling and delivery of internal communication based on start/end dates.
Key Points:
- Essential for corporate communication, internal marketing, and regulatory notices.
- Supports multiple delivery methods (dashboard, email, push notification).
Business Impact: Ensures timely and targeted dissemination of official information to the workforce.

Module: Learning Management
Purpose: Contains history of selected option IDs for each question within an assessment attempt.
Data: One row is created for each question answered by a user during an assessment attempt.
Process Usage:
- Stores user-selected options for each question under a specific assessment attempt.
- Maintains a record of selections for audit, review, or analytical purposes.
- Data is retained for historical tracking and not actively used in calculations beyond scoring.
Key Points:
- Helps in reconstructing user responses for each attempt.
- Useful for debugging, reporting, or re-evaluation scenarios.
Business Impact: Provides transparency and traceability of user answers across assessments.

Module: Payroll - Salary Structure Template Element Details
Purpose: Stores the granular rules for each component (pay element) included in a master salary structure template defined in tbl_SalaryStructureTemplate.
Data: Captures the pay element ID, its calculation method (fixed, percentage, formula), the fixed amount or percentage value, and its grouping section within the salary slip.
Process Usage:
- Structure Definition: Works with the parent template to form a complete, assignable salary structure.
- Payroll Calculation: Provides the specific rules used by the payroll engine to calculate the value of each element for an employee assigned to this template.
Key Points:
- Calculation Logic: The combination of CalculationType, ValueAmount, and ValuePercentage is the core formula for the element.
- The SectionName (A, B, C, etc.) is crucial for grouping elements on a salary slip (Earnings, Deductions, Employer Contributions).
Business Impact: Ensures that salary components are consistently and correctly computed according to predefined organizational rules.

Module: HRMS Document Module
Purpose: Provides complete, immutable audit trail for all changes to document records in the system.
Data: Each row represents a historical snapshot of a document record at the time of modification, preserving the exact state for compliance and tracking.
Process Usage:
- Automatically populated via system triggers or application logic when documents are created, updated, or deleted.
- Used by administrators and auditors to review document lifecycle and changes.
- Essential for compliance reporting and dispute resolution regarding policy changes.
Key Points:
- Immutable record of all document modifications for legal and compliance requirements.
- Preserves complete document state including targeting criteria and access controls.
- Enables point-in-time reconstruction of document versions.
Business Impact: Critical for regulatory compliance, audit requirements, and maintaining historical accuracy of policy and document changes.

Module: HRMS Email Configuration
Purpose: Stores HTML email templates and notification configurations used across various system modules for automated communications.
Data: Contains complete HTML email templates with dynamic placeholders, styling, and business logic for different notification scenarios.
Process Usage:
- Serves as template repository for automated email notifications (TDS approvals, attendance alerts, probation processes).
- Provides configurable email templates with dynamic data binding using Thymeleaf expressions.
- Supports multiple communication types including emails, push notifications, and system alerts.
Key Points:
- Uses Thymeleaf templating engine for dynamic content rendering.
- Supports rich HTML formatting with embedded CSS and responsive design.
- Enables business users to customize email content without code changes.
Business Impact: Essential for automated employee communications, notification consistency, and brand-compliant messaging across the organization.

Module: Compliance/Payroll Management - Gratuity Rule Detail Configuration
Purpose: Stores the specific parameters and components that determine how an employee’s Gratuity amount is calculated, in accordance with regulatory compliance and organizational policy.
Data: Captures which pay elements (earnings) form the basis of the “last drawn salary,” the minimum service tenure required, and the period for calculating average salary.
Process Usage:
- Gratuity Calculation: Used by the system’s calculation engine to identify the correct components and formula variables when an employee becomes eligible for gratuity (e.g., during separation).
- Compliance: Links the rule set to a specific compliance account or policy (ComplienceAccountId).
Key Points:
- Component Definition: PayElementsId and PayElementsName define the constituent parts of the salary considered for gratuity.
- Eligibility & Base: ServiceMonths defines minimum eligibility, and LastNoOfMonths defines the look-back period for the salary average.
Business Impact: Ensures the organization’s Gratuity liability is calculated accurately and consistently as per legal and internal rules.

Module: HRMS Time & Attendance (Work Schedule Audit)
Purpose: Stores the historical, immutable audit log of all changes made to employee work schedule configurations.
Data: Contains a snapshot of the work schedule rules (min hours, flexible settings, etc.) at the time a modification occurred.
Process Usage:
- Used for auditing, compliance checks, and reconstructing the exact work schedule rules applicable to an employee on any past date.
- Populated automatically upon creation, update, or deletion of a master work schedule record.
Key Points:
- Critical for payroll accuracy and legally defensible attendance calculations.
- The workscheduleid links the historical record back to its active counterpart.
Business Impact: Provides a robust trail of configuration changes for all employee scheduling rules.

Module: HRMS Leave Management
Purpose: Defines monthly allocation patterns and date-based proration rules for leave balance calculations.
Data: Stores date ranges and corresponding allocation values for precise monthly leave distribution.
Process Usage:
- Used by leave balance engine for pro-rata calculations based on joining dates.
- Supports complex allocation scenarios like decreasing entitlements or seasonal variations.
Key Points:
- Enables granular control over how leave balances are distributed across months.
- Supports both fixed and customized allocation patterns.
Business Impact: Critical for accurate leave accruals, especially for mid-month joiners and complex pro-rata scenarios.

Module: Separation/Off-boarding Management - Department Clearance Task Setup History Log
Purpose: Stores an immutable, historical record of all changes made to the individual sub-tasks that are part of a master Department Clearance Setup (e.g., specific steps required for “IT Clearance”).
Data: Captures a snapshot of the TaskName, links to the original task setup ID, and links to the history record of its parent clearance setup (DepartmentClearanceHistoryId).
Process Usage:
- Auditing: Provides a transparent timeline to track when a specific clearance task (e.g., “Collect Laptop,” “Disable Email Account”) was added, modified, or removed from a clearance checklist.
- Compliance: Used for retrospective checks to ensure that the required clearance tasks were in effect at the time an employee separated.
- Contextual Logging: Links to tbl_DepartmentClearanceSetUpHistory to provide full context of the parent rule set at the time of the change.
Key Points:
- Sub-task Tracking: Tracks the granular steps within the broader clearance process.
- The taskName is the primary piece of data being audited.
Business Impact: Ensures controlled and auditable management of the off-boarding checklist, critical for security and asset recovery.

Module: Objectives and Key results (OKR)
Purpose: Stores an immutable, time-stamped audit log of the assignment process and configuration of a specific OKR cycle for an employee.
Data: Captures the full snapshot of the assignment header (template name, dates, weightage) and the exact template fields used at that point in time.
Process Usage:
- A new record is created when the assignment is finalized, updated, or when a major status change occurs.
- Used for auditing and determining the exact set of goals that were active during a specific period.
Key Points:
- Immutable Log: Guarantees a record of the assignment configuration and dates.
- Template Fields: Stores the full JSON of the assigned goals to preserve the exact structure of the template at the time of assignment.

Module: HRMS Recruitment & Onboarding (Audit)
Purpose: Provides a complete, immutable audit trail for all changes to a candidate’s document records.
Data: One row is created for each significant action (e.g., upload, status change, remark addition) on a candidate_offer_document record.
Process Usage:
- Automatically populated by system triggers on CUD operations on the parent table.
- Used by administrators and auditors to review the lifecycle of document verification.
Key Points:
- Ensures data integrity and provides a historical log for compliance.
- Stores a JSON snapshot of the data at the time of the event.
Business Impact: Essential for auditability, dispute resolution, and tracking SLAs for the verification process.

Module: Employee Profile
Purpose: Stores version history of employee documents uploaded in the system.
Data: One row is created for each document change, upload, or approval/rejection event associated with an employee.
Process Usage:
- Tracks all document modification requests made by employees for approval.
- Maintains audit trail when document uploads are approved or rejected by HR/Admin.
- Ensures transparency and traceability of document versioning for compliance purposes.
Key Points:
- Each history record is linked to the main employee document record (tbl_employeedocument).
- Stores approval status and HR/admin remarks for each document revision.
Business Impact: Enables HR to monitor document changes, ensures compliance with audit requirements, and maintains historical integrity of employee documents.

Module: HRMS Expense Management
Purpose: Manages the assignment of custom fields to specific expense types, controlling field visibility, requirements, and display order in expense submission forms.
Data: Each row represents a custom field assigned to an expense type, defining its behavior, presentation order, and mandatory status within that specific expense context.
Process Usage:
- Configures which custom fields appear for different expense types (Travel, Meals, Accommodation, etc.).
- Controls field ordering, requirement rules, and default values per expense type.
- Manages custom field lifecycle and availability across different expense categories.
Key Points:
- Many-to-Many relationship between expense types and custom fields with additional configuration.
- Granular control over field behavior per expense type context.
- Supports staged rollout and retirement of custom fields.
Business Impact: Enables tailored expense capture experiences, ensures relevant data collection for different expense categories, and provides flexible field management across the organization.

Module: Payroll Compliance - PF Deduction Detail
Purpose: Stores the detailed, calculated monthly contributions for the Provident Fund (PF) and related schemes for each employee, segregated by its components (EPF, EPS, EDLI, Admin Charges).
Data: Captures employee and employer PF account numbers, contribution amounts for the employee and the employer (broken down), VPF, and the corresponding payroll period.
Process Usage:
- Generated during the final payroll processing run for each month.
- Provides the granular data necessary for generating monthly PF challan payments and statutory compliance reports (e.g., ECR file).
Key Points:
- Tracks both the Employee’s and the Employer’s statutory share.
- Separates contributions into PF (EPF), Pension (EPS), and Insurance (EDLI) components as required by law.
Business Impact: Essential for maintaining statutory compliance with EPF regulations and ensuring accurate remittance to the PF authorities.

Module: Task Management
Purpose: Stores historical snapshots of template custom field values.
Data: Each row represents a version of a custom field associated with a template at a specific point in time.
Process Usage:
- Tracks changes to template custom fields, including label updates, required flags, status changes, default values, and options.
- Supports audit and rollback of template custom field configurations.
Key Points:
- Maintains a history of all modifications to template custom fields.
- Useful for troubleshooting, auditing, and reviewing changes in template configuration.
Business Impact: Ensures accountability and traceability for changes in task template definitions, improving governance and compliance.

Module: HRMS Document Management & Workflow
Purpose: Stores predefined questions or communication templates that are displayed to users when they interact with a document requiring status change (e.g., Acceptance, Rejection).
Data: Links text/questions to a specific document acceptance status ID.
Process Usage:
- Used by the UI to dynamically prompt the user for input (e.g., “Why are you rejecting this document?”) based on the status they are selecting.
- Standardizes the communication and data captured during document lifecycle events.
Key Points:
- Critical for compliance workflows where specific reasons or acknowledgments are required for status transitions.
- The questions field likely contains the text or structured data for the prompt.
Business Impact: Ensures required information is collected at critical decision points in the document approval process.

Module: Objectives and Key results (OKR)
Purpose: Stores the current, active, and measurable Key Results (KRs) assigned to an employee or department for a specific OKR cycle.
Data: Contains the KR definition, target values, progress tracking metrics (current value, latest check-in), ownership details, and current status.
Process Usage:
- Updated regularly through “check-in” actions by KR owners.
- Used to calculate current achievement percentage and weighted contribution to the overall Objective.
- Feeds data into the formal tbl_okr_review tables at the end of a review period.
Key Points:
- Tracks both the goal configuration and the dynamic progress/status.
- Differentiates between individual and group/departmental KRs.
Business Impact: Provides real-time visibility into performance against strategic goals and enables timely interventions.

Module: HRMS Employee Information & Skills
Purpose: Stores the detailed records of all languages an employee is proficient in, along with their skill levels (read, write, speak).
Data: Records the language name and a boolean or rating scale for each skill type.
Process Usage:
- Used by recruiting and staffing teams to identify employees with specific language skills for projects or roles.
- Populates the language section of an employee’s professional profile.
Key Points:
- Essential for global organizations or those serving multilingual client bases.
- Includes a flag to identify the employee’s native language.
Business Impact: Enhances internal talent matching and improves organizational capability assessment.

Module: OKR
Purpose: Stores the actual data values entered into custom fields specifically configured for an OKR Key Result at the point of assignment or initial creation.
Data: Links a specific Key Result (key_result_id) to a custom field definition (custom_field_id) and records the value (custom_field_value) provided by the user.
Process Usage:
- Initial Data Capture: Used to store configuration details or metadata when a Key Result is first defined or assigned.
- Flexibility: Allows for tracking non-standard, context-specific data points for Key Results (e.g., target market, project code, or specific metric link).
Key Points:
- Value Store: This table holds the instance data/values, not the field definition itself.
- Likely Initial State: The “assign” suffix suggests these values represent the state at assignment/creation.

Module: HRMS Document Management
Purpose: Stores reusable letterhead templates with headers, footers, watermarks, and layout configurations for official document generation.
Data: Contains complete letterhead designs including HTML headers/footers, positioning measurements, watermarks, and activation status.
Process Usage:
- Serves as template repository for official HR letters, certificates, and organizational documents.
- Provides consistent branding and formatting across all generated documents.
- Enables dynamic selection of letterheads based on document type and organizational requirements.
Key Points:
- Supports precise positioning control for header/footer placement.
- Allows watermark integration for confidential or draft documents.
- Maintains soft delete capability for template management.
Business Impact: Essential for maintaining professional document standards, brand consistency, and efficient document generation workflows.

Module: OKR (Objectives and Key Results)
Purpose: Stores the rating measurement slab details for OKR evaluation schemes.
Process Usage:
- Each OKR rating scheme consists of multiple slabs defining performance measurement ranges.
- Used when calculating employee OKR performance ratings based on numerical or percentage scores.
- Helps in mapping actual performance values to a qualitative rating label (e.g., Excellent, Good, Needs Improvement).
Key Points:
- Each record defines a value range (min–max) with an associated rating label and score.
- Color codes are used to visually represent performance levels in dashboards and reports.
Business Impact:
Provides structured and consistent rating definitions for OKR evaluation, ensuring transparency and standardization in performance measurement.

Module: HRMS Document Module
Purpose: Central repository for dynamic data placeholders used in document templates and automated communications.
Data: Each row defines a reusable tag that can be embedded in templates to dynamically fetch and display employee-specific data during document generation.
Process Usage:
- Powers the template engine by replacing tags with real-time data from HR database.
- Enables creation of personalized documents without hard-coded values.
- Supports complex data retrieval through SQL queries and calculations.
Key Points:
- Tag-based substitution system for dynamic content generation.
- Supports both simple field references and complex calculated values.
- Integrated with email event system for automated communications.
Business Impact: Eliminates manual data entry in document generation, ensures data accuracy, and enables highly personalized employee communications.

Module: HRMS Employee Information & Self-Service (Audit Log)
Purpose: Stores the historical, immutable audit log of all submissions and status changes made by an employee to their self-reported profile details (e.g., personal bio, skills, certifications).
Data: Contains snapshots of the submitted data (selfdetail), the workflow status, and reasons for rejection.
Process Usage:
- Used for auditing and compliance to see how and when an employee’s personal data changed over time.
- Tracks the complete workflow of a self-service update request (submission, review, rejection).
Key Points:
- Ensures accountability for changes made to employee profiles.
- The selfdetail field likely stores a JSON snapshot of the data submitted by the employee.
Business Impact: Provides a transparent record for all employee-driven master data changes.

Module: Objectives and key results (OKR)
Purpose: Stores the definitions for dynamic, non-standard data fields that are added to the Key Result (KR) entity in the OKR framework.
Data: Captures the field’s name, data type, required status, and any associated lookup list for fields based on a fixed set of values.
Process Usage:
- Form Generation: Used to render organization-specific input fields when an employee creates or edits a Key Result.
- Validation: Enforces mandatory fields (is_required) and data types (field_type).
- Linked to a specific OKR template (template_id) to ensure the custom fields only appear in cycles based on that template.
Key Points:
- Extensibility: Allows for deep customization of the OKR tracking process beyond standard metrics.
- Fields defined here collect extra contextual or supplementary data for each Key Result.
Business Impact: Enables the organization to capture all necessary data points related to Key Result achievement, improving the quality and relevance of goal tracking.

Module: Employee
Purpose: Tracks deleted employee records and related structure.
Data: One row is created for each deleted employee, storing all relevant employee information.
Process Usage:
- When an employee is deleted, their personal and structural data is captured.
- Employee details and structure are stored in JSON format for audit and recovery.
Key Points:
- Maintains a historical snapshot of deleted employee data.
- Supports auditing, compliance, and potential restoration processes.
Business Impact: Ensures traceability and accountability for employee deletions, aiding compliance and internal audits.

Module: Asset - Custom Field Master
Purpose: Stores the definitions and rules for dynamic, non-standard fields that administrators can add to asset registration and tracking forms.
Data: Captures the internal field name, the user-facing label, the data type (text, number, date), validation rules (regex), and active status.
Process Usage:
- Form Generation: Used to dynamically render extra fields when HR/Admin creates or edits an asset record.
- Validation: Enforces data quality through regex_expression and displays error_message when validation fails.
- Provides flexibility to track unique asset characteristics (e.g., “Monitor Size,” “License Key”).
Key Points:
- Extensibility: Enables the system to adapt to varied organizational asset tracking needs.
- This table defines the custom fields themselves, not the values (values are stored in a separate asset value table).
Business Impact: Ensures comprehensive and accurate tracking of all relevant data points for company assets, improving inventory management and audit readiness.

Module: HRMS Time & Attendance (Audit)
Purpose: Provides a complete, immutable audit trail for all changes to attendance policy records in public.tbl_attendancepolicy.
Data: Stores a historical copy of the policy configuration whenever a change is made to the parent record.
Process Usage:
- Used for auditing, compliance, and viewing the policy configuration effective at a specific historical date.
- Populated by system triggers or application logic on CUD operations of the parent table.
Key Points:
- Ensures data integrity and provides a historical log for policy evolution.
- Every row is a snapshot of the full policy at the time of modification.
Business Impact: Essential for compliance audits and dispute resolution regarding policy changes.

Module: Communications & Engagement
Purpose: Stores master templates and configurations for automated milestone emails (birthdays, work anniversaries, etc.).
Data: One row per company (tenant), holding their unique branding, images, and text for all event mailers.
Process Usage: Queried by a daily background job using companyid when an employee event (e.g., birthday) is detected. The service fetches the correct subject, text, and image path to build and send the email.
Key Points: This is a configuration table (stores templates), not a log table (sent emails). It distinguishes between templates for the employee (e.g., birthdaytext) and templates for staff/manager notifications (e.g., birthdaystafftext).
Business Impact: Central to automating employee recognition. Misconfiguration (e.g., broken image path) directly impacts employee engagement and internal company brand.

Module: HRMS Employee Tracking
Purpose: Provides optimized data storage for historical tracking records by archiving month-wise data from the main tracking table to improve query performance and manage data growth.
Data: Each row represents archived tracking data from previous months, maintaining identical structure to main table but stored separately for performance optimization.
Process Usage:
- Stores historical tracking data (typically 2+ months old) in separate table for faster queries on recent data.
- Enables efficient data retrieval by reducing table size for current period queries.
- Supports compliance requirements for long-term data retention without impacting operational performance.
Key Points:
- Identical schema to main tbl_user_tracking table for seamless data access.
- Month-wise partitioning strategy for optimal query performance.<br-**Maintains data integrity while improving system responsiveness for recent data operations.
Business Impact: Significantly improves application performance for current period operations, maintains complete historical data for compliance and reporting, and enables efficient data management through archival strategies.

Module: HRMS Expense Management
Purpose: Provides configurable option values for custom expense fields, dropdown selections, and lookup lists across the expense management system.
Data: Each row represents a predefined option value that can be used in custom expense fields, dropdown menus, and selection lists with configurable status and company-specific scoping.
Process Usage:
- Defines available options for custom expense field dropdowns and selection lists.
- Manages option lifecycle (active/inactive/deleted) and company-specific customizations.
- Supports expense type level filtering for context-specific option availability.
Key Points:
- Reusable option repository for consistent dropdown values across expense forms.
- Company-level isolation for multi-tenant implementations.
- Flexible option management with deletable and default value flags.
Business Impact: Enables consistent data entry, reduces manual input errors, and provides flexible configuration for expense categorization and classification.

Module: Attendance - Shift Group Definition
Purpose: Stores the current mapping that defines the composition of a Shift Group by linking individual Shifts (e.g., Day Shift, Night Shift, Split Shift) to a master Shift Group (or Work Schedule).
Data: Captures the unique ID of an individual shift and the ID of the group it belongs to.
Process Usage:
- Group Definition: Used by the system to determine which set of shifts are included under one logical grouping for assignment to employees or policy application.
- Scheduling: Critical for systems that assign employees to a group, thereby assigning them to all associated shifts in that group.
- Master Linkage: Acts as the junction table for a many-to-many or one-to-many relationship between shifts and shift groups.
Key Points:
- Active Configuration: This table holds the live, current configuration of the shift groups.
- The naming convention suggests ShiftGroupId might link to a master schedule definition.
Business Impact: Enables flexible and efficient management of complex work schedules and attendance policies for various employee groups.

Module: HRMS Employee Engagement & Communication (Audit Log)
Purpose: Stores the historical, immutable audit log of all modifications, name changes, or deletions related to individual photos in the company albums.
Data: Contains a snapshot of the photo record at the time of the change, linking it back to the original photo and album.
Process Usage:
- Used for auditing and compliance to track who changed the name or removed a photo from an album and when.
- Provides a transparent history of media management within employee engagement features.
Key Points:
- Ensures accountability for media content management.
- The albumphotoid links the history record back to the current photo record.
Business Impact: Maintains a traceable record for all shared media content.

Module: Payroll/Compensation Management - Salary Structure Template History Log
Purpose: Stores an immutable, historical record of every change made to a master Salary Structure Template (from a related tbl_SalaryStructureTemplate table).
Data: Captures the unique ID of the original template, its status at the time of the change, and a complete JSON snapshot (HistoryObject) of the template’s details, including all associated pay elements and rules.
Process Usage:
- Auditing: Provides a complete audit trail of how salary structure rules have evolved over time for compliance and retrospective analysis.
- Rollback/Reference: Allows HR/Payroll to view the exact composition of a salary structure template as it existed on a past date.
- Compliance: Crucial for demonstrating adherence to compensation policies during audits.
Key Points:
- Snapshot Storage: The entire object of the template is serialized into the HistoryObject JSON column.
- Linked to the active template table via SalaryStructureTemplateId.
Business Impact: Ensures data integrity and accountability for all changes to employee compensation frameworks, which is critical for accurate payroll processing.

Module: HRMS General (Communications/Internal)
Purpose: Stores configuration for photo albums used in internal portals (e.g., employee intranet, news/gallery section).
Data: Each row defines a photo album, including its display criteria, photo limits, and cover image.
Process Usage: - Used by the front-end application to display image galleries to employees.
- Criteria control who sees the album (e.g., specific departments, locations).
Key Points: - Centralizes management of internal media and communications.
- Controls display duration and visibility.
Business Impact: Enhances internal communication and employee engagement through visual content.

Module: HRMS Branch Management
Purpose: Central repository for all company branch locations with comprehensive geographical, compliance, and operational configurations.
Data: Each row represents a physical branch location with complete address details, compliance settings, and regional configurations.
Process Usage:
- Defines organizational structure and geographical presence of the company.
- Configures branch-specific compliance rules for statutory deductions (PF, PT, ESIC, LWF).
- Manages regional settings like timezones and location-based services.
Key Points:
- Comprehensive branch profiling with both operational and compliance dimensions.
- Regional statutory configuration for automated payroll processing.
- Integration with geo-location services and timezone management.
Business Impact: Ensures accurate payroll processing, compliance with regional labor laws, and efficient multi-location operations management.

Module: HRMS Leave Management
Purpose: Stores pre-configured leave report definitions with layout, filtering, and access control settings.
Data: Contains report configurations including column layouts, pivot table settings, filters, and user access rules.
Process Usage:
- Used by reporting engine to generate standardized leave reports with consistent formatting.
- Enables role-based access control for different report types and user hierarchies.
Key Points:
- Supports multiple report types (Applied Leave, Balance Reports, Team Analytics).
- Uses JSON configuration for flexible report layout and data aggregation.
- Implements access control based on user roles and organizational hierarchy.
Business Impact: Provides consistent, secure, and customizable reporting capabilities for leave management analytics.

Module: HRMS System Administration & Reporting
Purpose: Stores the names, designations, and digital/scanned signature paths for key organizational stakeholders required to sign or authorize official company reports and documents (e.g., HR letters, final settlement).
Data: Configuration data detailing the signatory authority for various departments (HR, Admin, Director, IT, TDS/Finance).
Process Usage:
- Referenced by the reporting engine to dynamically populate the footer of generated PDF documents.
- Ensures consistency and accuracy of official report signatories across the system.
Key Points:
- Version 1 of the report footer reference, implying potential future versions.
- Directly ties signature blocks to Strategic Business Units (SBUs) for proper organizational context.
Business Impact: Ensures legal and organizational authenticity of system-generated official documents.

Module: Learning Management
Purpose: (Currently Unused)
Status: Table exists in schema but not referenced or used in current application code.
Data: No active data flow or CRUD operations from the application.
Business Impact: None at present — retained for backward compatibility or future use.

Module: Learning Management
Purpose: Contains progression details of users on a chapter-wise basis.
Data: One row is created for each user and each chapter to track completion and time spent.
Process Usage:
- Stores whether a chapter is completed by the user.
- Tracks how much time a user spent on a chapter or associated video.
- Helps determine overall course progression and engagement metrics.
Key Points:
- Maps to enrollment and chapter tables for accurate tracking.
- Supports both page-based and video-based time tracking.
Business Impact: Enables progress monitoring, course completion tracking, and analytics for Learning Management.

Module: Objectives and key results (OKR)
Purpose: Stores the detailed list of questions that compose a specific OKR Review Questionnaire Template, defining the content, expected response type, and scoring weight for each question.
Data: Captures the question text, its sequential order (index_number), its scoring weight, and the allowed answer format (e.g., RATING, TEXT).
Process Usage:
- Template Definition: Used by HR/Admin to define the structured content of the review form.
- Provides the source data for creating the active review forms when an OKR cycle is launched.
Key Points:
- Question Content: This table defines what is asked.
- Links to the master questionnaire header via master_id (likely tbl_okr_questionaries_master.id).
Business Impact: Ensures consistent and quantitative scoring during the OKR performance review process.

Module: Overtime
Purpose: Stores employee COFF (Compensatory Off) and extra working details.
Data: One row is created for each COFF record or extra working entry per employee.
Process Usage:
- Maintains details of COFF generated, its status, approval, and encashment.
- Tracks manual or system-generated extra working hours and related payments.
Key Points:
- Includes workflow status for reporting managers.
- Supports both leave and payment configurations.
- Tracks day type, working hours, and COFF balances.
Business Impact: Ensures accurate tracking, approval, and payment of extra working hours and compensatory leave.

Module: HRMS Document Module
Purpose: Central repository for all organizational documents, policies, and compliance materials with advanced targeting and access control.
Data: Each row represents a document or policy that can be targeted to specific employee groups based on organizational criteria.
Process Usage:
- Stores company policies, manuals, compliance documents, and HR materials.
- Enables targeted document distribution using JSON-based criteria rules.
- Controls document visibility and access through employee self-service portal.
Key Points:<br-**Advanced targeting system using JSON criteria for precise document distribution.
- Flexible access controls with download and acknowledgment requirements.
- Integrated with employee verification and assignment workflows.
Business Impact: Ensures right employees access relevant documents, maintains policy compliance, and provides centralized document management.

Module: Asset
Purpose: Stores information about company assets.
Data: One row per asset, including details on purchase, allocation, warranty, and status.
Process Usage:
- Tracks asset lifecycle: from purchase to allocation, return, and expiration.
- Supports multiple asset types and vendors.
- Includes allocation to individual or shared users.
Key Points:
- Stores attachments like warranty documents.
- Tracks asset depreciation and maintenance status.
Business Impact: Ensures proper asset management, compliance, and auditing.

Module: Employee Profile
Purpose: Stores employee address history, including both current and permanent addresses.
Data: Each record represents a submitted or approved address update for an employee.
Process Usage:
- When an employee updates their address, it is stored here with Pending status.
- Once the admin approves the address, the record is marked as Approved and the data is reflected in tbl_employeeaddress.
- If rejected, Rejected status is set with the reason stored in rejectreason.
Key Points:
- Maintains historical changes to employee addresses.
- Ensures data auditability and approval-based address management.

Module: Learning Management
Purpose: Stores question data for assessments.
Data: One row is created for each question associated with a specific assessment.
Process Usage:
- Used during the assessment process to present questions to users.
- Questions are mapped chapter-wise and connected to courses via assessments.
Key Points:
- Supports multiple question types (currently only MCQ is in use).
- Stores marks for each question for scoring purposes.
Business Impact: Enables structured assessment creation, scoring, and reporting in Learning Management.

Module: Learning Management
Purpose: Stores master information of all courses created in the Learning Management System (LMS).
Data: One row per course, containing title, description, category, and configuration details.
Process Usage:
- Courses are created and managed by administrators or instructors.
- Used as the parent table for chapters, assignments, and progress tracking.
- Provides metadata for displaying courses in the LMS library and during assignment workflows.
Key Points:
- Courses can be marked mandatory or optional.
- Supports JSON-based applicable criteria for flexible assignment.
- Stores metadata like tags, thumbnail, and duration for presentation and analytics.
Business Impact: Central repository for learning content. Enables structured training, compliance tracking, and self-paced learning for employees.

Module: HRMS Time & Attendance
Purpose: Defines a comprehensive set of rules and parameters governing employee attendance, including punch-in/out, late-coming, early-going, and penalty calculation logic.
Data: Stores the configuration for an attendance policy that can be assigned to one or more groups of employees.
Process Usage:
- Used by the daily attendance processor to validate punches against shift times.
- Determines the rules for regularization and correction requests.
Key Points:
- Critical for payroll accuracy and labor law compliance.
- Supports both fixed and flexible attendance models.
Business Impact: Ensures consistent and fair application of attendance rules across the organization.

Module: System/Database Management - Flyway Schema History Log
Purpose: This is a metadata table maintained by the Flyway database migration tool. It records every executed schema change (migration script) to ensure a controlled, versioned, and repeatable deployment process.
Data: Stores details about the migration, including its version number, description, the script file name, execution status, and timing.
Process Usage:
- Tracking: Flyway reads this table on startup to determine the current state of the database schema and identify which pending migrations need to be applied.
- Guarding: Prevents the same migration script from being executed multiple times.
- Auditing: Provides a complete audit trail of schema evolution.
Key Points:
- System Table: Should not be modified manually.
- installed_rank serves as the primary key and the order of execution.
Business Impact: Guarantees database consistency across all environments and supports reliable CI/CD pipelines for application updates.

**Module:**Employee Master Data / Organization Structure
Purpose: Stores the detailed organizational and structural data for an employee, effective from a specific date.
Data: Each row defines an employee’s designation, department, branch, reporting lines, and pay grade at a point in time.
Process Usage:
- A new historical record (row) is created for any organizational change (e.g., promotion, transfer, change of reporting manager).
- Used to retrieve the current and historical reporting/structural details of an employee.
Key Points:
- History Tracking: The erunning column manages the effective-dating: only one record per employee should have erunning = true (the current structure).
- Highly critical for payroll, approval workflows, and reporting structures.
Business Impact: Defines the employee’s place in the company, impacts security, and drives complex business logic.

Module: HRMS Employee Tracking
Purpose: Captures real-time employee location data, punch events, and device information for attendance tracking, geo-fencing, and movement analysis.
Data: Each row represents a raw tracking event captured from employee mobile devices, including GPS coordinates, timestamps, punch types, and device status information.
Process Usage:
- Records employee location data at regular intervals or on significant events.
- Captures punch-in/punch-out events with geographical context.
- Stores device and network information for data quality assessment.
Key Points:
- Primary source for raw location data and attendance events.
- Supports multiple punch types and tracking scenarios.
- Integrates with expense tracking and site-based attendance.
Business Impact: Provides foundational data for attendance calculation, movement pattern analysis, geo-fencing compliance, and expense validation.

Module: Onboarding & Confirmation Management
Purpose: Tracks the status, scores, and decisions related to an employee’s probation or employment confirmation review.
Data: Captures the employee, the form used, review statuses, effective dates of change, and final outcomes (confirmation, extension, termination).
Process Usage:
- Initiated upon the employee’s probation due date approaching.
- Used to track the rating submission status by the employee (EmpRat) and managers (Rep1Rat, Rep2Rat).
- Records the final confirmation/extension decision and details.
Key Points:
- Critical for managing the transition from probationer to permanent employee.
- Tracks the final rating and decision for audit purposes.
Business Impact: Directly affects employee status, benefits eligibility, and employment continuity.

Module: Asset Management - Vendor Contact Person Details
Purpose: Stores the contact information for key personnel (representatives) at the asset vendors listed in tbl_assets_vendor.
Data: Captures the person’s name, designation, mobile number, email, and any specific remarks, linking them to their master vendor record.
Process Usage:
- Vendor Communication: Provides direct contact details for ordering assets, following up on warranties, or scheduling maintenance/support.
- Relationship Management: Allows the HR/Admin team to maintain an organized list of who to contact at each vendor.
Key Points:
- Detail Record: Acts as a detail table for the master tbl_assets_vendor record.
- Essential for transactional efficiency in asset procurement and support.
Business Impact: Streamlines communication and follow-up with external asset providers, supporting efficient asset lifecycle management.

Module: HRMS Role Module
Purpose: Defines and maintains the master list of role type categories available in the system.
Data: Each row represents a distinct role type category that can be assigned to roles for classification and grouping.
Process Usage:
- Used as a reference table for validating and categorizing roles during role creation and management.
- Provides standardized role type options for consistent role classification across the organization.
Key Points:
- Serves as a lookup table for role type standardization.
- Ensures consistent role categorization and simplifies role management.
Business Impact: Enables organized role hierarchy, simplifies role administration, and supports standardized reporting on role types.

Module: Ticket Module
Purpose: Stores ticket category definitions used to classify and manage support or service tickets.
Data: One row per ticket category created by an administrator.
Process Usage:
- Defines categories under which tickets can be created by employees or system users.
- Configures SLA periods, reminder hours, and escalation workflows for each category.
- Maps SPOC (Single Point of Contact) and escalation users responsible for ticket resolution.
Key Points:
- Each category is company-specific and optionally department-specific.
- Supports multi-user SPOC and escalation configuration through comma-separated employee IDs.
Business Impact: Provides structured ticket categorization, ensuring efficient tracking, SLA monitoring, and escalation management within the Ticket Module.

Module: HRMS Helpdesk & Ticketing System (Audit Log)
Purpose: Records every change, update, comment, and attachment added to a master ticket record in public.tbl_ticket.
Data: Contains time-stamped snapshots of key fields and details about the action that occurred (e.g., status change, assignee change, comment added).
Process Usage:
- Used to generate the full communication and action history displayed within the support ticket interface.
- Provides an immutable audit trail for SLA compliance and service review.
Key Points:
- Critical for documenting the full resolution process and accountability.
- Records crucial events like escalations and reminders.
Business Impact: Enables transparent tracking of service requests and improves support team performance analysis.

Module: HRMS Leave Management
Purpose: Master table defining all types of leaves available in the organization with their fundamental characteristics.
Data: Stores leave type definitions including categorization, naming conventions, and status tracking.
Process Usage:
- Serves as the foundation for leave policy configuration and leave request processing.
- Used by leave application forms, balance calculations, and reporting systems.
Key Points:
- Defines hierarchical leave classification (Type → Sub-Type → Specific Categories).
- Establishes unique identifiers and naming conventions for all leave types.
Business Impact: Essential for standardized leave categorization, policy consistency, and regulatory compliance across the organization.

Module: HRMS Time & Attendance (Notification Configuration)
Purpose: Stores individual employee settings to control the types, frequency, and timing of automated notifications related to attendance (e.g., late-coming alerts, shift start reminders).
Data: Defines the user’s subscription to different notification categories.
Process Usage:
- Referenced by the notification engine to determine if and how to alert a specific employee about an attendance event.
- Allows employees or administrators to customize notification delivery.
Key Points:
- Essential for managing internal communication and proactive attendance compliance.
- Supports various types of alerts and delivery schedules.
Business Impact: Helps improve employee adherence to shift timings and reduces manual follow-up by HR.

Module: HRMS Expense Management
Purpose: Stores custom field values associated with expense claims, enabling flexible extension of expense data beyond standard fields while maintaining referential integrity.
Data: Each row represents a single custom field value linked to an expense claim, supporting both free-text values and predefined option selections.
Process Usage:
- Captures additional expense-related data through configurable custom fields.
- Supports both direct text input and dropdown selection from predefined options.
- Enables dynamic expense categorization, classification, and reporting beyond standard fields.
Key Points:
- Flexible key-value storage for expense claim extensions.
- Integration with both custom field definitions and predefined options.
- Supports audit trail and reporting on custom expense attributes.
Business Impact: Enables organizations to capture specialized expense data, supports complex approval workflows, and provides enhanced reporting capabilities for customized expense analysis.

Module: Learning Management
Purpose: Intended to store historical versions of assessment details for chapters.
Data: Each row would represent a previous version of an assessment record from tbl_assessment.
Process Usage:
- Designed to capture changes to assessments, titles, or passing criteria.
- Currently not used in code.

Module: Payroll/Compensation Management - Employee-Salary Structure Template Assignment
Purpose: Stores the current, active assignment of a master Salary Structure Template to an individual employee. This linkage determines the employee’s compensation framework and the set of earnings/deductions used in their payroll calculation.
Data: Captures the unique ID of the employee and the ID of the master salary structure template that governs their pay details.
Process Usage:
- Payroll Engine Input: The payroll process uses this mapping to fetch the correct rules, formulas, and pay elements when calculating an employee’s gross and net pay.
- Compensation Management: Ensures all employees are assigned a valid, defined salary structure.
Key Points:
- Many-to-One Relationship: Many employees can be mapped to one standard template.
- This table represents the operational assignment of a compensation policy to an individual.
Business Impact: Essential for the accurate and compliant processing of payroll for all employees.

Module: Objectives and Key results (OKR) Log
Purpose: Stores an immutable, historical snapshot of an Objective whenever its definition, ownership, status, or calculated progress changes in the main tbl_okr_objectives table.
Data: Captures the Objective name, period, target values, ownership, and key performance metrics (completion percentage, status) at the time of the change event.
Process Usage:
- A new record is created automatically when the parent Objective is updated, typically following a Key Result (KR) check-in or a manual Objective status change.
- Used for auditing goal modifications, analyzing progress trends over the cycle, and historical reporting.
Key Points:
- Immutability: Guarantees a time-stamped history of the Objective’s state.
- Objective Status Tracking: Tracks the Objective’s calculated progress based on its linked KRs over time.
Business Impact: Provides transparency and traceability for strategic goal management throughout the performance cycle.

Module: HRMS Task/General Management - Template Custom Field Assignment and Configuration
Purpose: Stores the specific configuration and assignment of master custom fields (from tbl_TemplateCustomfields) to an individual template (e.g., a Task Template).
Data: Captures the linkage between a template and a custom field, including template-specific properties like whether the field is mandatory and its default value.
Process Usage:
- Template Instantiation: Used when a user creates an item (like a task) based on a template, as it defines which fields appear and what their behavior is.
- Form Validation: The isRequired flag enforces mandatory data entry within the context of that template.
Key Points:
- Many-to-Many Linkage: This is the joining table that links a template (TemplateId) to a custom field definition (CustomFieldId).
- Instance Configuration: Allows the same custom field to have different labels or required status depending on the template it’s used in.
Business Impact: Enables flexible and context-specific data capture for tasks, forms, or other templated entities across the system.

Module: Full and Final (FnF)
Purpose: Stores the high-level details and configuration of an employee’s final Full and Final settlement calculation upon separation.
Data: Contains employee separation details, the payroll period for settlement, total gross earnings, final status, and summary amounts for encashment/recovery.
Process Usage:
- A single record is generated when the FnF process is initiated for a separating employee.
- Acts as the parent record for tbl_FndFLine which stores component-wise breakup.
- Used by payroll to process the final disbursement and by audit for verification.
Key Points:
- Centralizes the complex logic (formulas, days, amounts) for leave encashment and notice period shortfall.
- Ensures compliance and accurate final payouts.
Business Impact: Guarantees timely and accurate final settlements, minimizing disputes and legal risks.

Module: HRMS Geo-fencing Module
Purpose: Tracks real-time employee location data and geo-fencing events for attendance validation, movement monitoring, and location-based compliance.
Data: Each row represents a location tracking event captured from employee mobile devices or GPS systems, including coordinates, timestamps, and device status.
Process Usage:
- Captures employee location data for attendance marking and geo-fencing compliance.
- Monitors device status changes (GPS ON/OFF) for tracking reliability.
- Provides audit trail for employee movement and location-based validations.
Key Points:
- Real-time location tracking with GPS coordinates and timestamps.
- Device status monitoring including battery levels and GPS availability.
- Integration with geo-fencing rules and attendance validation workflows.
Business Impact: Enables accurate attendance tracking, ensures field employee accountability, and provides location-based compliance for remote workforce management.

Module: HRMS Helpdesk & Ticketing System
Purpose: Stores the master record for every support ticket or query raised by an employee or administrator regarding HR processes, system issues, or service requests.
Data: Contains ticket metadata, status, priority, resolution details, and organizational context.
Process Usage:
- Used by the support team to manage the assignment, tracking, and resolution of all incoming employee queries.
- Provides metrics for service level agreement (SLA) compliance and common issue reporting.
Key Points:
- Essential for managing internal service delivery and ensuring timely support for employees.
- Tracks the full lifecycle of a service request from creation to resolution.
Business Impact: Improves employee experience by centralizing and standardizing the process for getting assistance.

Module: Objectives and Key results (OKR)
Purpose: Stores the progress and performance review data for each individual Key Result (KR) within an OKR cycle.
Data: One row represents the review progress for one specific KR for a specific review period, including scores, comments, and attachments from all reviewers.
Process Usage:
- Populated with baseline KR data at the start of the review period.
- Updated incrementally by the employee and various managers as review steps are completed.
Key Points:
- Contains detailed review data for calculating final achievement scores.
- Multiple columns for each reviewer (_value, _percentage, _comment, etc.).
Business Impact: Provides the raw, auditable data used to assess performance against strategic objectives.

Module: Objectives and key results (OKR)
Purpose: Stores the specific configuration of custom fields that are actively assigned to a particular OKR template assignment or cycle.
Data: This table largely mirrors the okr_key_result_custom_fields master table but links the field definition to an assigned instance of an OKR cycle (assigned_template_id).
Process Usage:
- Runtime Configuration: Used by the application to determine exactly which custom fields should be displayed and validated when an employee is working on a Key Result belonging to the specified assigned template/cycle.
- Immutability: Ensures that even if the master custom field definition changes, the custom fields for an already-assigned OKR cycle remain consistent.
Key Points:
- Assignment Context: The key difference from the master table is the linkage via assigned_template_id.
- Defines the custom data capture for live, in-progress goals.
Business Impact: Provides version control for goal-setting forms, ensuring data integrity within active performance cycles.

Module: HRMS Expense Management
Purpose: Provides complete, immutable audit trail for all changes to expense policy configurations, preserving historical versions of policy rules, limits, and eligibility criteria.
Data: Each row represents a historical snapshot of an expense policy configuration at the time of modification, capturing only the changed fields to optimize storage while maintaining complete version history.
Process Usage:
- Automatically populated when expense policies are created, updated, or have configuration changes.
- Uses differential storage strategy to store only modified fields between versions.
- Used for compliance audits, policy evolution analysis, and historical expense validation.
Key Points:
- Differential change tracking minimizes storage while preserving complete history.
- Enables point-in-time reconstruction of policy configurations for expense validation.
- Essential for regulatory compliance and policy change impact analysis.
Business Impact: Critical for financial audits, expense dispute resolution, regulatory compliance, and maintaining complete policy evolution history.

Module: Task Management
Purpose: Stores details of recurring (automatically repeating) tasks created by employees.
Data: Each record defines one recurring task configuration for an employee.
Process Usage:
- When a user creates a daily task and enables the recurring option, the system stores configuration details here.
- Based on the configuration, new tasks are automatically generated periodically (daily, weekly, or monthly) until the recurring end date.
Key Points:
- Supports flexible recurring patterns (Daily, Weekly, Monthly).
- Enables task automation and reduces manual effort in creating repetitive tasks.
Business Impact:
- Ensures continuity of repeated activities such as daily reporting, routine checks, or status updates.
- Improves user productivity by automating task creation cycles.

Module: Objectives and Key results (OKR)
Purpose: Stores the current, active record for an OKR template assigned to a specific employee for a defined performance cycle.
Data: Contains the cycle dates, overall template details (name, weightage), the assignee, and the multi-step approval/review status.
Process Usage:
- Initiates an OKR cycle for an employee.
- Tracks the sequential sign-off status (Self, M1, M2, HR) of the assignment/review process.
Key Points:
- Represents a single, live OKR cycle for one employee.
- Crucial for managing the workflow and status of performance reviews.

Module: HRMS Leave Management
Purpose: Maintains monthly Data of leave balances, allocations, utilizations, and adjustments for each employee and leave type.
Data: Stores comprehensive monthly leave accounting including opening balances, allocations, applications, and year-end adjustments.
Process Usage:
- Serves as the primary source for monthly leave balance calculations and reporting.
- Tracks leave movements throughout the month and supports balance rollover to subsequent periods.
- Integrates with allocation engines, leave applications, and year-end processing systems.
Key Points:
- Provides granular monthly tracking of all leave balance components.
- Supports complex calculations involving carry forwards, encashments, and lapses.
Business Impact: Critical for accurate leave balance management, monthly reporting, and year-end processing workflows.

Module: HRMS Employee Tracking
Purpose: Provides complete, immutable audit trail for all changes to tracking policy configurations, preserving historical versions of policy rules, rates, and settings.
Data: Each row represents a historical snapshot of a tracking policy configuration at the time of modification, capturing all policy attributes for compliance and reconstruction.
Process Usage:
- Automatically populated when tracking policies are created, updated, or have rate changes.
- Used by administrators and auditors to review policy evolution and rate change history.
- Essential for expense dispute resolution and compliance reporting.
Key Points:
- Complete policy configuration preservation including all vehicle rates and rules.
- Maintains historical context for expense calculations and policy assignments.
- Enables point-in-time reconstruction of policy configurations for audit purposes.
Business Impact: Critical for financial audits, expense claim verification, regulatory compliance, and maintaining complete policy change history.

Module: HRMS Leave Management
Purpose: Serves as a complete audit ledger for all leave balance changes including allocations, utilizations, adjustments, and system operations.
Data: Stores every transaction that affects employee leave balances with before/after snapshots and detailed context.
Process Usage:
- Provides granular tracking of all leave balance movements for audit and reconciliation.
- Supports balance reconstruction at any point in time using transaction history.
- Enables detailed reporting on leave utilization patterns and policy enforcement.
Key Points:
- Acts as an immutable ledger following accounting principles (credit/debit entries).
- Captures complete context including policy references and business reasons.
Business Impact: Essential for financial auditing, compliance reporting, dispute resolution, and system transparency.

Module: HRMS Master Report Module
Purpose: Tracks and audits all report generation and download activities within the HRMS system.
Data: Each row represents a single instance of report generation, including search criteria and user actions for compliance tracking.
Process Usage:
- Automatically logged when users generate, preview, or download reports from any module.
- Used by administrators to monitor report usage patterns and ensure data access compliance.
Key Points:
- Captures complete context of report requests including filters and selection parameters.
- Supports audit requirements for sensitive HR data access and reporting.
Business Impact: Essential for data governance, compliance reporting, and monitoring access to sensitive employee information.

Module: HRMS Workflow & Approval Engine
Purpose: Stores the high-level configuration records for different approval workflows (e.g., Leave Approval, Expense Approval, Transfer Approval) used across the system.
Data: Defines the unique name, the organizational unit (SBU) it applies to, and the status of the overall configuration.
Process Usage:
- Referenced by transaction modules (e.g., Leave, Expense) to identify which specific approval chain should be used for a submission.
- The content of the approval steps (e.g., who approves, in what order) is typically stored in a related detail table.
Key Points:
- Critical for compliance and automating governance across organizational processes.
- Ensures consistency in how requests are routed for management review.
Business Impact: Defines the operational structure for all managerial and HR decision-making workflows.

Module: HRMS Leave Management (Balance Storage)
Purpose: Central repository storing current leave balances for each employee by leave type.
Data: Maintains real-time snapshot of available leave credits for all active employees.
Process Usage:
- Serves as the primary source for leave balance checks during application validation.
- Updated automatically by leave allocation engines and leave approval workflows.
Key Points:
- Provides quick lookup for available leave balances without complex calculations.
- Supports multiple leave types (PL, CL, SL, LWP, etc.) per employee.
Business Impact: Essential for real-time leave availability checks, application processing, and balance reporting.

Module: Separation/Off-boarding Management - Department Clearance Master Setup
Purpose: Defines the various clearance activities (e.g., Asset Return, Accounts Closure) required from different departments/functions when an employee leaves the organization.
Data: Captures the name of the clearance area, the department responsible, the specific employee(s) who are the Point of Contact (POC), and a flag indicating if the immediate reporting manager handles the clearance.
Process Usage:
- Off-boarding Workflow: When an employee resigns, this table is used to generate the list of clearance tasks that must be completed by the relevant POCs.
- Task Generation: Links to tbl_DepartmentClearanceTaskSetUp to define the specific sub-tasks required for this clearance area.
Key Points:
- Structured Exit: Ensures a standardized and complete checklist for every employee exit.
- The POC column stores the ID(s) of the employee(s) responsible for signing off on this clearance area.
Business Impact: Minimizes organizational risk by ensuring all company property, access, and accounts are properly recovered and closed during the separation process.

Module: System - Custom Field Configuration Master
Purpose: Stores the definitions and properties for dynamic, user-created fields that extend the core data structure of specific application modules (e.g., Expense Claims, Employee Profile).
Data: Captures the technical name, display label, field type (text, number, date), validation rules, component rendering type, and the operational stage of the field.
Process Usage:
- Form Generation: Used by the application UI layer to dynamically render input forms based on these definitions.
- Data Storage: Provides metadata necessary for validating and storing data collected via these custom fields.
Key Points:
- Extensibility: Crucial for allowing clients to tailor the HRIS without core code changes.
- Field properties like label and errorMessage support multi-tenant, user-friendly forms.
Business Impact: Enhances the flexibility and adaptability of the HRIS to meet varied organizational data requirements.

Module: HRMS Payroll & Full and Final (FnF) Settlement
Purpose: Stores the detailed line items—both earnings (additions) and deductions—that make up an employee’s final settlement calculation.
Data: Records element-specific amounts, days, and statutory contributions for the final month of employment.
Process Usage:
- Directly links to the FnF Header table (tbl_fndfheader) to form the complete final statement.
- Used by the payroll system to process the termination month’s salary and final dues.
Key Points:
- Critical for compliance and ensuring accurate settlement of all financial liabilities upon employee separation.
- Includes custom fields for complex or non-standard final payment elements.
Business Impact: Guarantees transparency and legal adherence in the employee separation process.

Module: Transfer - Team Transfer Employee Details
Purpose: Stores the individual employee records that are part of a larger, coordinated team transfer/restructuring request (defined in tbl_TeamTransfer).
Data: Captures the employee ID, their current reporting structure, current position, and links them back to the overall transfer request and company.
Process Usage:
- Transfer Execution: Used by the system to identify all employees whose records need to be updated upon approval of the parent TeamTransfer request.
- Pre-transfer Snapshot: Records the employee’s reporting line and position before the transfer takes effect (in the reportingPerson and fromPosition fields).
Key Points:
- Line-item Detail: Acts as a detail table for the header record in tbl_TeamTransfer.
- Crucial for managing the mass movement of employees during organizational changes.
Business Impact: Ensures that all affected employees are tracked and processed correctly during organizational restructuring and reporting line changes.

Module: HRMS Leave Management
Purpose: Maintains complete audit history of leave cancellation workflows including all approval stages and remarks.
Data: Stores multi-level approval status and comments when leaves are cancelled through the approval hierarchy.
Process Usage:
- Tracks the complete cancellation workflow from initiation to final HR approval.
- Preserves all stakeholder comments and decisions for compliance and reference.
Key Points:
- Captures the entire cancellation approval chain (Manager 1 → Manager 2 → HR Admin).
- Stores remarks from each approval level for transparency and dispute resolution.
Business Impact: Essential for audit compliance, process transparency, and resolving cancellation-related disputes.

• Module:* HRMS Leave Management
  Purpose: Tracks and manages leave encashment requests and payments for employees.
  Data: Stores encashment requests, calculations, approval status, and payment details for converted leave balances.
  Process Usage:
  - Handles both automatic system-generated and manual HR-initiated leave encashments.
  - Integrates with payroll system for encashment amount processing and payment.
  Key Points:
  - Supports multiple encashment scenarios (yearly, tenure-based, manual, cycle-based).
  - Calculates encashment amounts using various salary formulae and employee data.
  Business Impact: Essential for monetizing unused leave balances while maintaining audit trails and compliance.