# Parsec (ParsecNET 3)

Parsec timesheets, lateness and passes right in the chat

Табель по проходам, пропуска и группы доступа

## How the agent works with Parsec (ParsecNET 3)

The agent works with the ParsecNET 3 integration service, which is installed on the access control server with the system. The connection takes the server address (port 10101 by default), the organisation and a ParsecNET operator. The service answers with that operator's rights: whatever the operator cannot see in Parsec, the agent cannot see either. The server usually sits on a local network, so requests go through your computer with the app running.

Timesheets and lateness are computed from the event archive: the agent opens a report for the period filtered by pass types, reads it in portions and closes it. For each employee and day it takes the first entry and the last exit and compares them with the intervals of the worktime schedule. A report without an explicit limit is cut by the server at five thousand events, so the agent sets the limit itself and checks the event count against the total.

Issuing a pass follows the same path as the Parsec application: the employee is created in a department, an editing session of their card is opened, and a card with an access group is issued in it. The agent shows every write in advance and performs it after your confirmation.

Opening a door, disarming and other hardware commands change physical access on site, so the agent sends them only on a separate explicit request for a specific door. The Parsec server can deliver event subscriptions only to an address on its own network, so the agent reads fresh events by polling the archive.

## 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 worktime schedule 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 code and shows their department, access group and latest passes.

### A pass for a new hire
The agent creates the employee in the right department, issues a card with an access group and shows every step before it writes.

### Visitor bureau requests
The agent collects visitor requests for a period, shows their statuses and helps file a new one.

### Doors and alarm state
The agent reads the state of locks, door contacts and alarm areas and tells you what is open or disarmed.

## How to connect

**Before you connect**

- ParsecNET 3 (PNSoft) or ParsecNET Office with the integration service installed
- A ParsecNET operator with the required rights and visibility scope
- Network access to the Parsec server from the computer running the app

### Check the Parsec integration service
The integration service comes with the ParsecNET 3 server on port 10101 and needs no separate licence. PNOffice lacks event subscriptions and hardware commands.

### Create an operator for the integration
In ParsecNET create an operator that can read personnel, identifiers and events. Grant writes only if the agent will issue passes.

### Check the server address
On the computer running the app open http://server-address:10101/IntegrationService/IntegrationService.asmx: if the service page opens, the agent reaches the server.

### Paste address, organisation, login, password
Enter the organisation if the operator does not belong to the system organisation. The operator's rights limit what the agent sees in Parsec.

## FAQ

### How do I connect Parsec?
Enter the ParsecNET server address with the integration service port (usually http://server-address:10101), the organisation (it may stay empty for the system one) and the operator's name and password. The integration service needs no separate licence, the base one is enough.

### What rights does the operator need?
Reading staff and timesheets needs rights on staff data, schedules and events. Issuing cards and editing employees needs rights to change staff and access groups, and hardware commands need a separate hardware control right.

### Does it work with ParsecNET Office?
Yes, with a smaller set of functions: Office has no visitor bureau, blacklist, schedule editing, live events or hardware commands. Timesheets from the event archive and card issuing are available.

### Will the agent open a door on its own?
No. The agent sends hardware commands only on your explicit request naming the door or alarm area, and after confirmation.

[Open Parsec (ParsecNET 3)](https://www.parsec.ru/support/integration/)