How to read this page
This page is a full index: each capability group points to its canonical explanation page, where the complete details live with requirements and limits. Start with the group you care about and follow the link to its explanation page.
Attendance and methods
Record with phone families for every branch: location for open areas, branch code with location for single entrances (fixed printed or rotating on a screen), and the approved network for stable offices — plus your face with location or network within the target release: enroll once with the guided flow, then check in daily with verification plus location (Face + GPS) or with the branch network alone and no location needed (Face + Wi-Fi). The system applies each method's requirements and branch policies: it verifies the area for location methods and the approved networks for the network method, with location when branch policy requires it. A code alone is never enough.
For special cases: a supervisor records the crew from one phone, a shared branch point with a changing screen — triple scan from your phone or phone-free face recognition (1:N) within the target release — and biometric devices and import files per compatibility. Administrative corrections carry evidence and day statuses are documented.
Details and conditions on the attendance methods page.
Employees and branches
A profile per employee with status (pending, active, suspended) and a one-time invite code, and a branch with its area, methods, and networks. Categories are flexible labels, not a department structure.
Five admin roles with clear branch permissions, required documents with review and expiry alerts, and assigned assets with recorded returns. Every change appears in the activity log with its source.
Details on the employees and branches page.
Shifts
Shift work with a weekly schedule: cells are assigned as drafts, weeks copied, and published after review. Night work is dated to its correct night.
Breaks and short time-off requests inside the day with window request and approval, rejection, or postponement with employee acceptance, corrections justified with evidence, and mock-location rejection optional per company. The security log records what is detected.
Details on the shifts and attendance rules page.
Leaves
Paid and unpaid leaves with annual balances and policy-based carryover (seniority, cap, expiry) plus cash encashment on approval. Recurring requests and conversion to absence are supported.
Staff submit and the authorized role issues one documented decision — approval or rejection — and approved-leave conflicts with attendance are resolved before payout. Cancelling an approved request follows an authorized management path.
Details on the leaves and requests page.
Payroll
Generate the cycle as a live draft for review, then approve it to freeze the approved-cycle figures. Deduction ladders, allowances, and bulk bonuses stay inside the cycle, and advances carry installments created by approval.
Post-approval exceptions are documented with reversal controls, settlements and end-of-service are calculated, and the payslip goes to staff in detail. Mark-paid is an administrative record, not a bank transfer, and statutory values are settings, not a certificate.
Details on the payroll and advances page.
Reports
Attendance, staff, leave, document, payroll, and overtime reports with branch and period filters. Export in documented formats per device (details on the reports page).
Check the live board for who is in the branch now, and trace who changed what in the activity log. Support runs on tickets with attachments and tracked states.
Details on the reports and export page.
The three products
Me for staff: record, shift, requests, payslip, documents, assets, and notifications. One for managers: branches, shifts, approvals, payroll, reports, and devices — on phone and web.
Pulse for the branch: pairing, heartbeat, a changing code screen, and fleet policies — triple scan from the staff phone with the Me app, or phone-free face recognition (1:N) after a one-time enrollment within the target release. Details and compatibility on the point page.
Details on the employee app page, the manager app page, the branch point page, and the downloads page.
Examples by workplace
Illustrative example: a single-entrance store suits branch code with location, a stable office suits the approved network, a field team suits location, a mobile crew suits supervisor recording, and a busy branch suits the shared branch point. Choose the method that suits how each branch works.
Honest limits
- An unrecorded request is not counted — retry when the connection returns.
- Connection to the network alone never records, and a branch code alone is never enough.
- Approval freezes the approved-cycle figures; drafts are live estimates that change until approval.
- Mark-paid is an administrative record, not a bank transfer, and statutory values are settings, not a certificate.
- Face is within the approved target release, and actual availability is announced with the release.
Start from one record
Register your company from the portal, set each branch method, and invite your team with the activation code. Register your account now, or review the listed pricing, and the start steps on the getting-started page.