Solution
Attendance across every branch, in one workspace
A factory in one city, a head office in another, and outlets in between: traditionally each site keeps its own attendance software and someone collects the files. A cloud gateway removes that step, because every terminal reports directly to the same workspace.
How it works across sites
- 1
Install a terminal at each site
Any supported terminal works, and different branches can use different models. A face terminal at head office and fingerprint readers in the factory all report the same way.
- 2
Point each device at the gateway
Enter biobackend.asaanex.com in the device cloud settings. Each terminal connects outward over the site's own internet, so no VPN links the branches together.
- 3
Watch every site in one console
The dashboard shows each terminal with its location, last seen time and connection state, so head office notices a machine that stopped reporting.
- 4
Report across all branches
Attendance from every site sits in one workspace. Filter by device for a single branch, or take the whole company at once for payroll.
What head office gets
- One live view of which terminals are online, and when each last reported.
- Attendance for every site in one place, filterable per branch.
- One export or one API call at payroll time instead of chasing each location.
- No PC that must stay switched on at any branch.
What each branch keeps
Nothing changes for staff at the site. They scan as they always have, on the same machine, with the same enrolled finger or face. Branch managers keep their own terminal and can still check the day locally, while the records also reach head office instantly.
Adding a new location
Opening another branch is a five minute job: add the terminal in your workspace with its serial number, type the gateway address into its cloud menu, restart it. The setup guides cover the exact menu for the common models.
Start with one branch, add the rest when you are ready
Connect a single terminal, see how the data arrives, then roll out to the other sites. Free for 3 months.
Multi-branch questions
Do branches need to be on the same network?
No. Each terminal uses the internet connection at its own site. There is no VPN, no leased line and no static IP, so a new branch only needs a working broadband or 4G connection.
Can a branch manager see only their own site?
Attendance records carry the device they came from, so reports and API calls can be filtered per branch with the device_id parameter.
What if one branch loses internet for a day?
That terminal keeps its punches in memory and pushes them when the connection returns. Attendance for the other branches is unaffected, and the delayed records keep their original times.
How many terminals can one workspace hold?
There is no per-device charge, so you can register a terminal for every site, gate or shift entrance in the same workspace.