On this page
01. Plan before you plug anything in02. Same building or same network03. Branches on other networks04. Keep the employee list clean05. Reports across branches06. A typical scenario07. Common mistakes08. Quick checklist09. Frequently asked questions
Create one area per site, give every terminal its own fixed IP, add them all under Device > Device, keep a single employee list, and use a VPN or cloud option for branches on different networks.
Key takeaways
- One area per branch keeps reports clean.
- Every terminal needs its own fixed IP.
- Keep one master employee list.
- Remote sites need a VPN, port forwarding or a cloud route.
01Plan before you plug anything in
- List each site and door that needs a terminal.
- Make an IP table: site, device name, IP, port, Comm Key.
- Decide who is allowed to punch where. Employees are linked to areas.
02Same building or same network
Add each terminal as a device (see add a device) and assign it to an area. Employees allowed in multiple areas can punch on any of them.
03Branches on other networks
A terminal in another town is not on your office LAN. Options:
- VPN between sites, so the PC sees the remote terminal like a local one. Usually the most secure.
- Port forwarding on the branch router to the terminal's port. It works but exposes a device to the internet, so use a strong Comm Key and a firewall rule.
- Cloud/ADMS style push if your terminal and software version support it, with the terminal reporting to a server. Confirm support before you rely on it.
- USB collection at the branch as a manual fallback.
04Keep the employee list clean
Use unique employee IDs across all sites. Assign shifts per department. Run Sync Data per area so changes reach the right terminals. See departments and areas.
05Reports across branches
Reports can filter by area, department or employee, so HR can see one branch or the whole company. Download punches from each terminal before you calculate.
06A typical scenario
A Nairobi retailer with a head office, a warehouse and a Mombasa shop used three areas. Head office and warehouse shared a VPN so the PC saw both terminals. Mombasa used USB downloads at month-end until the VPN was ready. Reports could be filtered by area for each manager.
Illustrative example based on common cases, not a named customer.
07Common mistakes
- Using the same IP on terminals in different offices that later join one network.
- Duplicate employee IDs across branches.
- Exposing a terminal to the internet with a default Comm Key.
- No master staff list, so each branch keeps its own.
- Not labelling devices by site.
08Quick checklist
- IP table for all terminals
- One area per site
- Unique employee IDs
- VPN or other remote plan
- Comm Keys set
- Branch reports tested
09Frequently asked questions
How many terminals can one software handle?
Many. The practical limit depends on your version and licence. Ask your supplier for the figure for your licence.
Can branches share employees?
Yes. Give them the same employee ID and allow them in each area.
Is a VPN necessary?
It is the safest way to reach remote terminals. Port forwarding is possible but riskier.
Does Qyvea set up multi-branch systems?
Yes, for Nairobi and across Kenya. Message us with your sites and we will quote.
This guide is part of our ZKTeco K40 and ZKBio Time.Net series. For the full start-to-finish walkthrough with screenshots, read How to Configure a ZKTeco K40 Pro with ZKBio Time.Net.
ZKTeco and ZKBio are trademarks of ZKTeco Inc. Menu names on the K40 Pro and in the software vary slightly by firmware and software version; where yours differ, look for the nearest match. Qyvea is a ZKTeco reseller and installer in Kenya.
