Storeganise now integrates directly with Paxton Net2, so unit access automatically follows rental status. When a customer moves in, their access is granted. When they move out, it’s revoked. When a payment fails, it’s suspended, and when the balance clears, it comes back. All of it happens without anyone updating a second system.
For operators running Paxton on-site, this closes a gap that’s been costing staff hours and creating security exposure for years.
The two-system problem
Until now, Paxton and Storeganise ran in parallel. Rental lifecycle events happened in Storeganise. Door permissions lived in Paxton Net2. Every move-in, move-out, payment failure, and unit transfer became two jobs — and the Paxton side was the one that got missed.
A customer moves out on Tuesday. Their unit is cleared, the rental is closed in Storeganise, your team moves on. By Friday, no one has revoked their PIN in Paxton. For three days, a non-customer had working access to your facility.
A customer pays off their overdue balance at 11pm on a Sunday. Storeganise marks the rental current. But Paxton still has them locked out until someone gets to a desk on Monday morning — and you’ll likely get a frustrated call before then.
A customer transfers from a 5x5 to a 10x10. That’s two manual updates in Paxton, with a window in between where they either hold access to both units or neither.
This is the standard flow when access control and management software run independently.
What the Add-On does
Four lifecycle events now drive Paxton access changes, with no one touching Paxton.
Move-ins. When a customer completes their move-in, a Paxton user is created from their Storeganise profile, a unique PIN is generated, and they’re granted access to their unit door plus any shared access points you’ve configured (main gate, elevator, lobby). The PIN appears in their Customer Portal. If they already have another unit at the site, their existing Paxton account is reused.
Move-outs. Access to the unit door is revoked the moment the move-out is processed. If it was their last active unit at the site, shared facility access is removed and their Paxton user record is deleted.
Overdue payments. When a rental goes overdue, every door permission for that customer at the site is suspended, including shared access. When the balance clears, permissions are restored in full.
Unit transfers. Moving a customer between units grants access to the new door and revokes the old one in a single operation, so there’s no point in the transfer where their access is wrong.
The tools you still need
Automation covers the standard flow. For situations that fall outside it, three operator tools handle the rest.
Manual overlock on every unit rental lets you revoke and restore access on demand, outside the automated workflows — useful for operational edge cases that don’t fit a standard rental status.
Resync handles the situation where you enable the Add-on after customers have already moved in. Existing rentals won’t have Paxton data attached by default; resync imports their current access state so lifecycle management works for them going forward.
Operator tasks surface failures the moment they happen. If a unit isn’t mapped to a Paxton door, credentials expire, or a shared access point name is wrong, a task appears in Storeganise with a plain-language description and the action needed to fix it. Failures show up as tasks rather than disappearing into a log somewhere.
Setting it up
The Add-on connects Storeganise to your on-premise Paxton Net2 server through an ngrok tunnel — the standard way to expose a local service securely over the internet. You’ll need:
- An active Paxton Net2 installation with doors and timezones already configured
- Your Paxton API credentials (username, password, client ID)
- An ngrok account with the agent running on the same Windows machine hosting Net2
From there: install the Add-on, enter your Paxton credentials, list your shared access points, and map each unit to a Paxton door using the new custom field. Door mapping can be done individually on each unit, or in bulk through the unit export and import.
For production use, a paid ngrok plan with a reserved domain is strongly recommended. The free tier has two limitations worth knowing about: the tunnel URL changes every time the agent restarts (requiring a manual update in the Add-on settings each time), and requests are capped at 20,000/month - every move-in, move-out, and sync counts toward this limit, so an active multi-unit site can exhaust the free tier quickly. Paid plans start at $8/month for a single site or $20/month for multiple sites.
What’s coming next
A few things are on the roadmap for future releases:
Cross-site customer records. Today the Add-on manages one Paxton Net2 instance per site, so customers with units at multiple facilities have separate Paxton records at each. Unified records across sites are planned.
Bulk resync. Existing rentals are currently resynced individually. A bulk option is coming.
Mobile and Bluetooth credentials. v1 supports PIN-based access via keypad readers. Paxton mobile app and Bluetooth support will follow.
Advanced access schedules. Beyond Net2’s standard timezone configuration, custom schedules need to be set up directly in Paxton for now.
Enabling it
The Paxton Net2 Add-on is installed by request. Contact support@storeganise.com to get it set up on your account, and the team will walk you through configuration.
If you’re not yet using Storeganise and you’re evaluating access control workflows, Paxton is one of 30+ integrations in our Add-ons marketplace. Book a demo to see how it fits with the rest of your operations.