Overview
Kisi is an access control platform that enables secure, 24/7 entry to your facility using mobile credentials or key fobs. When connected to PushPress Core, member access is automatically granted or revoked based on plan membership status.
Who can do this: Admin
Where: Where: Core → Marketplace
Prerequisites
An active Kisi account with a Group created and associated with the doors you want to control (How to create a Group in Kisi)
Your Kisi credentials: Group ID and Kisi API Key
API Key: Kisi dashboard → main menu → My Account → API → Add API Key
Admin access to PushPress Core with permission to manage integrations
If you previously used Kisi with PushPress via Zapier or another custom workflow, disable those automations before connecting to avoid conflicts.
Connecting Kisi
In Core, go to Marketplace - Integrations - Kisi
Find Kisi and click Connect.
Review the data permissions and click Agree and Continue.
Enter your Kisi credentials:
Group ID
Kisi API Key
Click Connect.
After connecting, the Connection Status displays on the integration card. From this page you can:
See the status of your connection
Disconnect or reconnect Kisi
Update your stored Kisi IDs and API keys as needed
Once connected, Core syncs eligible members to Kisi to grant or revoke access based on plan status.
Enable 24/7 Access on a Plan
To determine which members receive Kisi access, either create a new plan or edit an existing one:
Go to Plans in Core and select the plan to edit (or click + New Plan).
Under Access → Advanced Access Settings, check the 24-hr access box.
Save the plan.
Members with an active subscription to this plan will be synced to Kisi and granted access to the selected doors. Members whose plan is paused, expired, or cancelled will have access removed automatically.
This may take a few seconds for larger gyms due to Kisi rate limits.
📸 Screenshot: Plan settings showing Access → Advanced Access Settings with 24-hr access checkbox
Member Experience
Members receive Kisi access by email after their plan becomes active
Members can unlock doors using whatever Kisi method is configured for your location
If a member changes their email in Core, see FAQs below
On the Kisi Side
Confirm the following in your Kisi dashboard:
Your Site and Doors are correctly configured
The Kisi Group linked to your PushPress plan is assigned the correct door permissions and schedules (24/7 or custom hours)
Sync Behavior and Data Fields
Sync direction: PushPress Core → Kisi
Data sent to Kisi per member: User and subscription data
Sync cadence: Recently updated subscriptions sync once per day; all subscriptions sync once per week. Syncs run in the background to catch any missed events or third-party API downtime.
Important: Changes made directly in Kisi for users who also exist in Core may be overwritten by the next sync from Core.
Migrating from Another Platform (e.g., Glofox)
If your gym is switching from a platform that's already connected to Kisi (such as Glofox), follow this order to avoid access disruption for your members.
Do not disconnect Glofox first. Members will lose door access during the gap if Kisi has nothing to sync from.
Migration Steps
Step 1 — Set up the PushPress-Kisi connection
Connect Kisi to PushPress Core using the steps above before making any changes to your existing platform connection. Both platforms can be connected to Kisi simultaneously during the transition window.
Step 2 — Enable 24-hr access on the relevant plan(s)
In Core, edit the plans that should have Kisi access and enable the 24-hr access setting. This prepares Core to sync members as soon as you're ready.
Step 3 — Test with a single user
Before cutting over fully, do a controlled test:
Pick one staff member or test account whose email exists in both Core and Kisi.
Confirm that member's plan in Core has 24-hr access enabled.
Verify the member appears in Kisi with the correct access after the next sync (allow up to 24 hours, or trigger a manual sync if available).
Test that the member can successfully unlock a door.
Step 4 — Cut over and disconnect Glofox
Once the test member's access is confirmed working through PushPress:
Confirm your full member list in Core is accurate and all relevant plans have 24-hr access enabled.
Disconnect Glofox from Kisi.
Core will become the sole source of truth for Kisi access going forward.
📸 Screenshot: Kisi dashboard showing connected platforms during transition window
Duplicate Email Question
If a member's email exists in Kisi because they were synced from Glofox, and PushPress then syncs the same email, you may have a user appearing in Kisi from two sources simultaneously during the transition window.
This is a Kisi-side concern. How Kisi handles users who exist across two connected platforms at the same time varies depending on Kisi's own deduplication logic. Check with Kisi Support directly to understand how they manage this before your cutover — especially if members have active unlock history or custom access rules you want to preserve.
FAQs
Will users be removed once their plan expires or is cancelled?
Yes. When a member's plan is paused, expires, or is cancelled in Core, their Kisi access will be removed. Their Kisi profile will also be removed and unlock history will be lost. This prevents gyms from hitting Kisi rate limits.
Which plan statuses trigger Kisi access?
Status | Access |
Active | Granted |
Pending Cancel | Granted until cancellation date |
Pending Active | Not granted until Active |
Paused / Expired / Cancelled | Revoked |
What happens if an admin adds someone manually in Kisi who doesn't exist in Core?
They remain in Kisi with whatever access is configured there. If you later create a matching profile in Core with the same email, Core may begin managing that user's access and could overwrite Kisi changes.
What if a member changes their email in Core?
The member's Kisi record is tied to their email. An email change in Core may result in a new Kisi record being created and the old one being removed. Confirm behavior with Kisi if this is a concern.
Are waivers or plan details synced to Kisi?
No. Kisi only receives access grant/revoke signals based on plan membership status. It does not know if a waiver is signed.
Do you support multiple Kisi Groups?
Not currently. Only one Group is supported per connection. Permissions are tied to a single Group determined by which plans have 24-hr access enabled.
Troubleshooting
Connection shows as failed or invalid credentials
Re-enter Kisi API Key and Group ID in the Integrations Hub
Confirm the API key has permissions for the correct Group
Member should have access but doesn't
Verify the member's plan is Active in Core and includes 24-hr access
Confirm the member's email matches exactly between Core and Kisi
Check that the assigned Kisi Group has permissions to the correct doors
Member was removed unexpectedly
Check for plan pause, cancellation, or failed payment events changing plan status
Confirm no duplicate profiles or emails are causing conflicts
Doors not unlocking
Confirm Kisi hardware is online and door schedules and permissions are correct in the Kisi dashboard
Review Kisi audit logs for the attempted unlock