Gate access control
Which controllers are supported, setting one up, how codes are issued, suspended and removed, the sync queue, keypad entries, vendor codes, and the on-site agent for panels programmed on a PC.
Gate access is part of Enterprise. Once a controller is set up, every tenant with an active rental has one gate code that is pushed to every controller at the facilities where they rent, switched off when rent is past due, switched back on when it's paid, and removed at move-out. You never type codes into the panel again.
Access is per facility: each facility switches a tenant's code on or off for its own gates only. A tenant who rents at two of your facilities and falls behind at one is locked out there and keeps getting in at the other, where they're paid up. Each facility's controllers hold only the spaces the tenant rents at that facility.
Supported controllers
Settings → Gate systems → Add a gate controller, pick the make and model and the page tells you what it needs:
| Make | How it connects |
|---|---|
| PDK (ProdataKey) cloud nodes – Red series, Red Max, gate kits | pdk.io Web API client (ID + secret) and your system ID; your PDK dealer creates the client |
| PDK 1.0 panels (original cloud node) | the 1.0 API client and the panel ID |
| Brivo Access (ACS6000, ACS300, ACS100…) | a Brivo API app (client ID, secret, API key), an administrator login and the group tenants join |
| OpenTech, PTI StorLogix Cloud, Janus / Nokē, Kisi, Openpath, Verkada, LiftMaster myQ, Nice/Apollo… – anything with a web API | the generic HTTP connection: templated add/update/remove/test requests with placeholders for the code and name; optional open-gate call |
| DoorKing 1830 series, PTI Falcon XT, Sentinel, Linear, Apollo… – panels programmed from a PC on site | the on-site agent: a small program on that PC that rewrites the vendor's import file and reports back |
| Keypads with no interface | programming by hand: the Gate page lists codes to add, change and remove and staff tick them off |
Several controllers per facility are fine (a PDK node on the main gate and a DoorKing on the back lot); every code at that facility goes to all of them.
Setting one up
- Name it, choose make and model, fill in the connection fields, Test, Save. Keys are encrypted in your account.
- Cloud systems: Load devices and tick the gates/doors tenants may use. The 24/7 access rule and the tenants' group are created for you.
- On-site agent: the page shows a one-time token; install the agent on the gate PC with it (instructions on the page). It polls for work, rewrites the import file (DoorKing RAM, CSV or JSON), runs the vendor's import if you tell it the command, and tails the transaction log for keypad entries.
- Existing codes: tenants loaded by the migration with a gate code are pushed straight away; if the panel already has a holder with that PIN it's adopted rather than duplicated.
The life of a code
- Chosen at move-in – online or at the counter the tenant picks a code of the facility's length (not sequential, not repeated, not in use) or one is generated. Reservations don't ask; the code comes at move-in. It's stored switched off.
- Payment received → the code is switched on at that facility and pushed to its controllers. The welcome message carries it.
- Past due at the facility's gate access suspended step → disabled at that facility. Paid up there → enabled again. What the tenant owes at another facility, or a lock-out there, doesn't change access here.
- Move-out → when the tenant has no space left at a facility, the code is removed from that facility's controllers (even if they still rent elsewhere – it keeps working there). When they rent nowhere any more the code is given up; an undone move-out gets the same code back if nobody took it.
One code per tenant
A tenant has one code for all your facilities. It must be unique at every facility they're at – among everyone who uses that facility's gates (tenants of other facilities who rent there too) and its vendor codes. A code staff type in, or a tenant picks, is refused if it's taken at any facility the tenant rents at.
If a tenant moves into another facility and their code is already used by someone there, it isn't reused: a new code is issued, unique at every facility they rent at, and it replaces the old one at all of them. The facility's gate activity says so, the move-in shows the new code and the welcome message carries it – make sure the tenant knows.
By hand
From the tenant's Gate access tab staff can suspend or restore access at their own facility, re-send the code to the tenant, or type a new code under Change code (it replaces the old one at every facility); the reason is logged. Codes go to the gate systems on their own – the line On N of M gate systems opens the list per controller. The tab also shows the tenant's access at their other facilities, view only – a lock-out at another facility is lifted there, by its staff.
The Gate page
Facilities → Gate:
- Gate controls – Open, Hold open and Close for cloud controllers that support it.
- Sync queue – every change becomes one job per controller. Cloud jobs run at once and are retried with back-off (up to 12 tries, the nightly job at the latest); agent jobs wait for the agent; hand-programmed jobs wait for you to tick them. A tenant's Gate access tab shows their state per controller: synced, pending or error.
- Keypad entries – every code keyed at a gate as the controller reported it: when, which gate, the code, who it belongs to (tenant, vendor code, or unknown code), granted or denied and why. Pulled from cloud controllers every couple of minutes while the page is open and nightly; the agent posts them from the panel's log. Filter by result, gate, dates or search; each tenant's Gate access tab shows their last 10. One row per entry: a cloud controller that reports the keypad read, the credential match and the decision as separate events (PDK does) is shown once, with the decision.
- Vendor & visitor codes – codes that aren't a tenant's (lawn service, delivery, the inspector) with a label, on/off, and valid-until date. Loaded to every controller like tenant codes.
- App activity – what the app did with the gate, by whom.
In the tenant portal
Tenants see their code and whether it's active on the portal's overview. They can't open gates from the portal – only staff can open a gate remotely.
Reports
Reports → Occupancy → Gate Access: tenant codes by state and gate events by source. Keypad entries older than about 400 days are trimmed by the nightly job (and earlier if your retention setting says so).





