Description: Any global user can register a new company in the system, allowing for immediate access and setup of company profiles.
Example Scenario: A global user creates a new garment company, “Garments B,” in the system. This new company can now access the platform, allowing them to set up their operations and invite users.
2. Company Registration by Super Admin
Description: The super admin can register new companies into the system, ensuring each company has a unique profile.
Example Scenario: A super admin registers “Garments A,” enabling it to access the platform and set up its operational features.
3. User Registration and Initial Company Setup
Description: Any user can register in the system, either joining an existing company or creating their own company. Upon registration, the user becomes the company admin, similar to how the super admin creates a company admin.
Example Scenario: An employee registers for “Garments A” and awaits approval from the company admin to activate their account for attendance and other functionalities.
4. Social Login and User Linking
Description: Allow users to register and log in using social media accounts, linking them to their company profiles for easier access.
Example Scenario: An employee uses their Google account to sign up, and their profile is linked to “Garments A.” However, their account remains inactive until the company admin approves their registration.
5. User Profile Approval by Company Admin
Description: Company admins review and approve user registrations. Users remain inactive until they receive approval, at which point they can access all system functionalities.
Example Scenario: The company admin of “Garments A” reviews the new employee’s profile linked through social login. Once approved, the employee’s account is activated, allowing them to start transactions such as logging attendance.
6. Employee and Role Management
Description: Manage employees’ roles with different levels of permissions, ensuring secure access to data.
Model Level Permission: Define permissions at the model level for different user roles (e.g., HR Manager, Supervisor, Employee).
Object Level Permission: Control access to specific records based on user roles, allowing for more granular data security.
Field Level Permission: Restrict access to sensitive fields based on user roles (e.g., salary details).
Example Scenario: The HR manager can access all employee records, while regular employees can only view their own information, ensuring data privacy.
7. Subscription Management
Description: Manage subscription limits for companies and enforce transaction rules when limits are exceeded.
Example Scenario: If “Garments A” has a subscription for 100 users but tries to add a 101st, an alert is generated prompting an upgrade to accommodate additional users.
8. Company Admin’s Role in User Management
Description: Company admins oversee user management, including adding, updating, and removing employees from the system. They can also approve or reject user registrations.
Example Scenario: The admin of “Garments A” receives a registration request from a new user, reviews the application, and either approves or denies the request based on company policies.
9. Company Profile Management
Description: Allows for the re-registration or nullification of company profiles, including updating company details.
Example Scenario: If “Garments A” undergoes a name change, the admin can update their profile accordingly to reflect this change.
10. Attendance Data Collection
Description: Collect attendance data from various sources, including biometric machines and mobile applications.
Biometric Machines: Capture attendance data locally using fingerprint or facial recognition.
Mobile Attendance: Capture location-based attendance through a mobile app, allowing employees to clock in from remote locations.
Example Scenario: Employees clock in at the office using biometric machines, while others log their attendance via the mobile app when working offsite.
11. Data Transmission to Cloud
Description: Transmit local attendance data to the cloud server for centralized storage and processing.
Example Scenario: Daily attendance data collected from biometric machines is automatically uploaded to the cloud for backup and analysis.
12. Managing and Validating Attendance Data
Description: Admins review and validate attendance entries from both local and cloud systems, ensuring accuracy and legitimacy.
Example Scenario: The admin checks mobile attendance entries and flags those logged from unauthorized locations for review.
13. Data Synchronization
Description: Ensure consistency and synchronization of attendance data between local and cloud systems to avoid discrepancies.
Example Scenario: Any changes made to attendance records locally are reflected in real-time in the cloud database, ensuring data accuracy.
14. Handling Data Transactions Across Systems
Description: Manage transactions effectively between local and cloud systems to maintain data integrity and consistency.
Example Scenario: When an admin approves an attendance entry, it is marked as accepted in both systems, updating the records accordingly.
15. Ensuring Redundancy and Operational Continuity
Description: Implement strategies to ensure operational continuity in case of server crashes or failures.
Example Scenario: If the cloud server goes down, the local system continues to function, storing data locally until connectivity is restored.
16. Customization for Company Needs
Description: Tailor features and functionalities to meet specific company requirements, allowing for flexibility in operations.
Example Scenario: “Garments A” requests additional fields in the attendance form to capture specific data relevant to their operations, such as overtime hours.
17. Admin Management of Mobile Attendance Data
Description: Admins manage mobile attendance entries, including reviewing, approving, or deleting unwanted or incorrect data.
Example Scenario: The admin of “Garments A” reviews a mobile attendance entry from an employee marked from a location outside the office and deletes it after validation.
18. Performance and Reliability Management
Description: Ensure system performance during peak usage times and manage data loads efficiently to maintain responsiveness.
Example Scenario: Load balancing strategies are employed during peak clock-in hours to prevent system overload and maintain quick access for users.
19. Scenario: Mobile Attendance Validation
Description: Validate mobile attendance to ensure that entries are legitimate and made by authorized users.
Example Scenario: An employee logs their attendance from home, which is flagged by the system for review. The admin must confirm that the entry is legitimate before approval.
20. Reviewing and Deleting Unwanted Attendance
Description: Admins regularly review attendance data and can delete any unwanted entries, ensuring accurate records.
Example Scenario: The admin notices multiple attendance entries from the same employee from unauthorized locations and deletes them to maintain integrity.
21. Approving Attendance Entries
Description: After review, admins can approve valid attendance entries, updating the records in both local and cloud systems.
Example Scenario: The admin verifies that an employee’s mobile attendance entry is valid and approves it, ensuring it reflects in both systems.
22. Synchronizing Data Between Local and Cloud Systems
Description: Continuously synchronize data between local and cloud systems to maintain a unified database.
Example Scenario: Updates made to employee attendance in the local system are automatically synchronized with the cloud, keeping both databases consistent.