A solution shaped around your work.
Browser access is useful when HR and department managers need the same records. The implementation must distinguish employee self-service from administration and establish who maintains the application, database and hosting environment.
What this service covers
- Hosting environment and supported browser requirements
- Employee, supervisor and HR permission design
- Attendance imports and correction approval workflows
- Database backup and application handover arrangements
We confirm the selected equipment, responsibilities and deliverables in your project proposal before work begins.
How we deliver the work
- 01
Map people and permissions
Define employee groups, attendance rules, access zones and administrator responsibilities. Identify the enrollment method and the records that each role needs to view.
- 02
Configure the workflow
Configure the selected devices or application around approved schedules and permissions. Check connectivity and any interfaces with HR, payroll or existing door equipment.
- 03
Test real scenarios
Test agreed employee and administrator scenarios, including exceptions and access removal. Hand over the operating steps and clarify who maintains users and reports.
A clear handover
Agree the records your team needs to operate and maintain the solution. Depending on the selected scope, these can include:
- Device or application configuration summary
- User administration and exception-handling steps
- Agreed reporting and integration checks
What to prepare for your project
Describe your approval workflow, user roles and preferred hosting arrangement. Provide anonymised report examples and details of devices or files supplying attendance records.
Discuss this serviceYour questions, answered
Is a web attendance system always hosted in the cloud?
No. A browser interface can connect to an approved local server or hosted environment. The choice depends on software support, connectivity, administration responsibilities and your organisation’s requirements for data access.
How do we choose between face, fingerprint and card attendance?
Consider employee numbers, entrance conditions, shifts and how exceptions will be handled. We review the proposed device, software and enrolment method before confirming a suitable configuration.
What needs to be checked before attendance data reaches payroll?
Confirm the HR or payroll application, supported export or API, employee identifiers and approval rules. Test sample records and overnight shifts before using the integration for payroll.
What information should be shared at the enquiry stage?
Share approximate employee and door counts, shift patterns and existing device models. Use sample field names or anonymized examples to discuss integrations; actual biometric templates, employee files and passwords are not needed in the website form.