RusGuard timesheets, lateness and passes right in the chat
Connect RusGuard access control to the AI agent: event log, late staff, timesheets, employees, keys and access levels. Passes are issued only after you confirm.
How the agent works with RusGuard
The agent works with the network service of the RusGuard Soft server (LNetworkService), the same one the system's workstations connect to. The connection takes the server address and a RusGuard operator's login and password. The service answers with that operator's rights: whatever the operator cannot see in RusGuard, the agent cannot see either. The server usually sits on a local network, so requests go through your computer running the app.
Timesheets and lateness are computed from the event log: the agent reads key passes for the period day by day and page by page, takes each employee's first entry and last exit per day and compares them with the shift start and end of the employee's work timetable.
Issuing a pass follows the same path as the RusGuard application: the employee is created in a group, a card is issued and an access level is assigned. The agent shows every write in advance and performs it after your confirmation.
Opening a door, blocking and arming change physical access on site, so the agent sends such commands only on a separate explicit request for a specific door, and only after you confirm the command in the chat.
Integration scenarios
A timesheet from the pass log
The agent pulls the month's passes, finds each employee's first entry and last exit of every day and puts the hours into a table.
Lateness against the schedule
The agent compares the first entry with the shift start of the employee's work timetable and names who came late or left early and by how much.
Whose card is this
The agent finds the card holder by the card number and shows their group, access levels and latest passes.
A pass for a new hire
The agent creates the employee in the right group, issues a card and assigns an access level, showing every step before it writes.
Locking out leavers
The agent finds employees by a list of personnel numbers and blocks their passage after your confirmation.
RusGuard examples
15 нарушений у 8 сотрудников: 11 опозданий и 4 ранних ухода.
- 5 нарушений у одного сотрудника, все в первую неделю
- 2 ранних ухода совпали с командировкой, их отметил отдельно
Данные взял из отчёта RusGuard по нарушителям графика, без пересчёта по журналу.
How to connect
Before you connect
- RusGuard Soft with the LNetworkServer network service reachable over HTTPS
- A RusGuard operator with the required rights
- A trusted server certificate and the address by the name on it
- Network access to the RusGuard server from the computer running the app
- 1
Check the RusGuard integration service
The integration service is part of the RusGuard Soft server and answers at https://server-name/LNetworkServer/LNetworkService.svc. It works over HTTPS only.
- 2
Trust the server certificate
Install the RusGuard server certificate as trusted on the computer running the app, and address the server by the name on its certificate, not by IP address.
- 3
Create an operator for the integration
In RusGuard Soft create an operator that can read employees, keys and the event log. Grant writes only if the agent will issue passes.
- 4
Paste the address, login and password
Make sure the computer and server clocks agree: if they differ by more than a few minutes the server rejects the operator sign-in.
FAQ
Enter the RusGuard server address (for example https://rusguard.company.local, the app adds the service path itself) and a RusGuard operator's login and password.
The RusGuard service works over HTTPS only, and the app verifies the server certificate. If the certificate is self-signed, add it to the trusted ones on the computer running the app and address the server by the name the certificate is issued for, not by IP address.
The server rejects a request when its clock is more than five minutes off the real time. Check the time on the RusGuard server.
No. The agent sends device commands only on your explicit request naming the door, and after confirmation.