Atlas Knowledge Base
Dashboard
Access Control Service

Access Control Service


Overview

The Access Control Service connects SBN to a WinPak access-control system so that card and door activity can be managed from SBN. On a fixed timer it collects the access-control work waiting in SBN — adding, changing or removing a cardholder and their card, setting access levels, PIN and expiry — and applies each change to WinPak. It also carries out door and point commands issued from SBN, such as locking, unlocking, momentarily releasing a door, or asking a device for its current status.

Traffic runs in both directions: as WinPak reports events and status changes, the service records them back into SBN so they are visible alongside everything else on the account. A separate communications check watches for a gap in that incoming traffic; if nothing is heard from WinPak within the configured window, the service can raise a communication failure message so the loss of contact is noticed. The service runs on a Windows machine with the WinPak components installed, and needs both a working SBN data-server connection and valid WinPak credentials — if either sign-in fails at start-up the service logs the reason and stops.

Dashboard

Installing and managing this service is done from the SBN Services Dashboard &mdash; see <a href="/help/SBN-Services/Dashboard">here</a>.

Service Properties

Only properties specific to this service are listed here. Common service properties (SBN Server connection, Logging, SMTP) are found <a href="/help/SBN-Services/Common-Properties">here</a>.

Timer (In seconds)

How often the service checks SBN for access-control work waiting to be sent to WinPak.

Comms &mdash; Timer (In seconds)

How long the service will go without hearing from WinPak before it treats the connection as failed. Incoming activity resets this window.

Send Comm. Fail Message

When checked, the service reports a communication failure once the window above has elapsed with no contact from WinPak. Leave it unchecked if you do not want these alerts.

Comm. Fail Message

The text reported when a communication failure is raised. Use wording that makes it clear to an operator which access-control system has lost contact.

Comm. Fail CID

The account the communication failure is reported against, so the alert appears on the correct installation.

WinPak &mdash; Authentication: Database Domain

The domain used when signing in to the WinPak database.

WinPak &mdash; Authentication: User

The user name used to sign in to the WinPak database.

WinPak &mdash; Authentication: Pass

The password that goes with the database user name above.

WinPak &mdash; API Authentication: User

The user name the service signs in with to send commands to WinPak and receive its event traffic. This is a separate sign-in from the database one.

WinPak &mdash; API Authentication: Pass

The password that goes with the user name above.



Was this helpful?