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 can automatically be granted or revoked based on plan membership status.
Prerequisites
An active Kisi account with the a group created, associated with the doors that you want to control (How to create a Group in Kisi)
Your Kisi identifiers and credentials: Group ID and Kisi API Key
Kisi API Key can be found in Kisi under the main menu → My Account → API → Add API key
Admin access to PushPress Core and permission to manage integrations.
Note: If you previously used Kisi with PushPress via Zapier or another custom workflow, disable those automations to avoid conflicts.
Connecting Kisi
In Core, go to Integrations in Core
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 will display on the integration card. From this page you can:
See the status of your connection
Disconnect/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 plan:
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 canceled will have access removed automatically. This may take up to a few second for larger gyms due to Kisi rate limits.
Member Experience
Members receive access in Kisi by email after their plan becomes active.
Members can unlock doors using whatever Kisi method you have made available
If a member changes email or phone number in Core, see FAQs below for how this affects Kisi records.
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 & Data Fields
Sync Direction: PushPress Core → Kisi
Data sent to Kisi (per member):
User and subscription data
Sync cadence: We sync recently updated subscriptions once per day and all subscriptions once per week. Syncs happen in the background in case events are missed or third party APIs are down.
Important: Changes made directly in Kisi for users that also exist in Core may be overwritten by the next sync from Core.
FAQs
Will users be removed once their plan expires or is canceled?
Yes. When a member’s plan is paused, expires, or is canceled in Core, their Kisi access will be removed.
Note that when a member’s access is removed, their Kisi profile will be removed and their unlock history will be lost. This is done to avoid gyms hitting their Kisi rate limits, which would cause issues with Kisi functionality.
Which plan statuses trigger Kisi access?
Active: Access granted
Pending Cancel: Access granted until plan cancellation date
Pending Active: Access not granted until status becomes Active
Paused/Expired/Canceled: Access revoked
What happens if an admin adds someone manually in Kisi that does not exist in Core?
They will remain in Kisi and can keep access as configured there. However, if you later create a matching person in Core with the same email, Core may begin managing that user’s access going forward and could overwrite changes from Kisi.
What if a member changes their email in Core?
Are waivers or plan details synced to Kisi?
No, Kisi will grant or not grant information based on sync from Core from plan membership status. It will not know if a waiver is signed.
Do you support multiple Groups on Kisi?
Not at the moment, we only support one group. Permissions are tied to a single group and are determined by the plans that you have enabled 24-hr access to.
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 right group
Member should have access but doesn’t
Verify the member’s plan is Active in Core and includes 24‑hr access
Ensure the member’s email matches between Core and Kisi
Check that the assigned Kisi Group actually has permissions to the correct Door(s)
Member was removed unexpectedly
Check for plan pause/cancel events or failed payments changing status
Confirm no duplicate profiles/emails exist causing conflicts
Doors not unlocking
Confirm Kisi hardware is online and door schedules/permissions are correct
Review Kisi audit logs for the attempted unlock.