Set up Glofox integration

Follow the steps to integrate Glofox into your Kisi organization.

Prerequisites

• Kisi organization administrator rights (or delegated access, see FAQ)
• Glofox admin rights
• Your Glofox Location ID

Please ask the admin of the gym account in Glofox to email Glofox.Support@abcfitness.com to request the Kisi integration, their Glofox Location ID, and to have their Location ID allowlisted.

Prerequisites for Glofox members to be imported into Kisi

To be imported into Kisi, Glofox members must:

1. Have one of Glofox’s membership types assigned
2. Possess an active membership

Set up the Glofox integration

Once you have configured your location in Glofox get your branch ID, and follow this video guide to complete the integration setup from Kisi's dashboard.

info

Only one Glofox integration is allowed per organization. However, you can add multiple configurations within the integration to map several locations to groups.

1. Sign in to Kisi
2. Click the integrations icon (3x3 grid of dots) > Add Integration
3. Define the name of your new Glofox integration
4. Open the Type dropdown and select Glofox Gym Management Software
5. Click Add Configuration, enter your Branch Id (the Location ID for your Glofox setup), and click Next. Kisi checks the branch with Glofox at this point
6. Choose the Kisi group to which members with active memberships will be imported
7. Under Select Memberships, choose the Glofox memberships to sync to the group
8. Turn on Bookings Enabled if Credit Pack and Pay-As-You-Go users should also be imported
9. Click Save

New configurations are always saved as enabled. Saving a configuration starts a sync of that branch right away.

Edit a configuration

To change a configuration, open it from the Configurations tab, make your changes, and click Save. On this page you can:

• Turn Enable Configuration off or on
• Change the selected memberships
• Set the booking access window, if Bookings Enabled is on

The group and the branch Timezone are shown read-only. To change the group, delete the configuration and create a new one.

When you delete configurations, Kisi shows "Configuration deletion is in progress." It then runs a sync that removes the membership access granted by those configurations before removing them.

Kisi also changes configurations automatically in two cases:

• If Glofox reports the branch as not found, for example because the Location ID is no longer allowlisted, Kisi disables every configuration for that branch
• If you delete the Kisi group used by a configuration, Kisi deletes that configuration

Map the branch to a place for check-in

After adding a configuration for a new Glofox branch, map that branch to a Kisi place so that unlocks are posted as check-ins at the right branch in Glofox.

1. Click the Check-In Mapping tab
2. Click Add Mapping
3. Select the Glofox branch and the corresponding Kisi place
4. Click Save

Each Kisi place can be mapped to only one Glofox branch. Only branches that already have a configuration can be mapped, and Add Mapping is disabled once every branch is mapped. If a configured branch has no place mapping, the integration page shows an error banner listing it.

info

You only need to do this once per branch. If you add further configurations for the same branch later, check-ins will be posted automatically without any additional mapping.

Synchronizing Glofox active memberships with Kisi

Once the integration is set up, it will synchronize users with active memberships to Kisi and maintain consistency. New and terminated memberships are updated in Kisi in real time through Glofox webhooks. A full sync also runs once a day after midnight UTC, and right away for a branch whenever you save one of its configurations. The configuration page shows when the branch was last synced under Last synced at.

info

Access provisioning is usually instant, but during high-load periods like month-end, Glofox may take up to 20 minutes to send data to Kisi.

note

If a member's Glofox membership becomes locked, typically due to a missed flexible payment or a failed recurring payment, Kisi treats it as invalid and revokes access immediately. Kisi restores access as soon as Glofox reports the membership as active again, usually within minutes.

note

If the memberships list is empty, no membership access will be granted. This behavior differs from the previous implementation. During migration, integrations with empty membership lists were updated to include all appropriate memberships in Glofox. However, if a new membership is added in Glofox, it must be manually added to the integration configuration in Kisi.

To add a new membership type to an existing configuration:

1. Open the integration and click Configure Integration
2. Edit the relevant configuration
3. Add the new membership type under Select Memberships
4. Click Save

Grace period for locked memberships

By default, Kisi revokes access immediately when a member's Glofox membership becomes locked. If your organization prefers a delay, maintaining access for a set number of days after a membership is locked before revoking it, you can configure a grace period from the integration settings:

1. Click Settings on the integration page
2. In the Days until "LOCKED" memberships access is revoked field, enter the number of days access should be maintained after a membership is locked
3. Click Save

The grace period is counted in days from the start of the day Kisi first saw the membership as locked. The default is 0, which revokes access immediately, and the field doesn't accept negative values.

Once the grace period ends, Kisi removes access at the next daily sync or the next membership update from Glofox, if the membership is still locked. Access is restored immediately if the membership becomes active again within the grace period.

Synchronizing Glofox bookings and credit packs with Kisi

Credit Pack and Pay-As-You-Go (PAYG) users will only be synced with Kisi when they have an active booking in Glofox regardless of membership status or type. Access is granted solely for the booking duration and expires once the booking ends. After the booking period, users will no longer see shared access in the Kisi web dashboard, and typically won’t have access outside their booking time.

By default, access starts one hour before a booking and ends when the booking ends. To change this, open a configuration that has Bookings Enabled from the Configurations tab, set Booking access starts in (minutes) and Booking access ends in (minutes), and click Save. These fields aren't available in the Add Configuration dialog.

Kisi checks for upcoming bookings every 15 minutes and creates access for bookings whose access window starts within the next hour. The member receives the access email when access is created. A booking made after this point gets access right away. Cancelling a booking in Glofox removes its access right away.

Members who already have membership access in a configuration don't get a separate booking access entry for it.

info

Suppose the integration settings specify that access should be granted 30 minutes before the class and remain valid for 15 minutes after the class. If a member books a 1-hour class in advance starting at 3:00 PM, access will be granted at 2:30 PM and revoked at 4:15 PM. However, if the class is booked within those 30 minutes before it starts, access will be granted instantly and remain valid until 4:15 PM.

Additionally, booking-based access is time zone-sensitive, so always ensure you’re aware in what time zone you review the data.

Differentiating access for different facilities in Glofox

note

This feature is not enabled by default. Contact our support team to request enabling facility-based access differentiation for your organization.

Once enabled, you can map specific Glofox facilities to Kisi groups, allowing you to differentiate access based on which facility a member has booked. To set this up:

1. Navigate to your Glofox integration configuration
2. For each configuration with bookings enabled, select the corresponding facility in the Select Facilities dropdown
3. Complete all configuration mappings before proceeding to the next step
4. Click Settings on the integration page
5. Toggle Enable bookings for facilities only

When this setting is enabled:

• If a configuration is mapped to a facility, only bookings from that specific facility will grant access to the associated group
• If a facility is not mapped to any configuration, bookings from that facility will not grant access to any group
• To sync non-facility bookings to a group, enable bookings for that configuration but leave the facility list empty

This setting applies to all future bookings and does not affect the membership synchronization process.

Single-use access for facility bookings

note

This setting is not enabled by default. Contact our support team to request it.

Once enabled, you can restrict facility booking access to a single entry per booking. This setting requires Enable bookings for facilities only. Turning that setting off also turns off single-use access. To configure it:

1. Click Settings on the integration page
2. Make sure Enable bookings for facilities only is on
3. Toggle Enable single-use access for facility bookings

When enabled, a facility booking grants access only until the member successfully unlocks the door once. After the first unlock, access for that booking is immediately revoked for the remainder of the configured booking-based access period, preventing re-entry using the same booking.

Differentiating access for trainers in Glofox

note

This feature is not enabled by default. Contact our support team to request it.

Once enabled, you can map Glofox trainers to Kisi groups, so that classes and appointments with a trainer grant access only to that trainer's group. To set this up:

1. For each configuration with bookings enabled, select the trainers for that configuration
2. Click Settings on the integration page
3. Toggle Enable bookings for trainers only

When this setting is enabled:

• If a configuration has trainers selected, only appointments with those trainers grant access to its group
• If a configuration has no trainers selected, it grants access for classes and appointments with trainers that no other configuration selects

Check Kisi users in through Glofox

When a user with access granted through the Glofox integration unlocks a door at a location, Kisi checks them in with Glofox at the branch mapped to that place in the Check-In Mapping tab. If the place isn't mapped, the check-in is posted to the member's home branch. We recommend mapping every branch.

Denied unlocks and reader attempts are also sent to Glofox, as failed entries. Denials caused by Primary Device Restriction or geofence checks aren't sent.

You can also set up a dedicated check-in station using a standalone Kisi Reader configured with an Access Point. When members scan their credentials at the reader, they will be checked in with Glofox without needing a controller or unlocking a door. This is useful for attendance tracking at locations where you don't need physical door access control.

Unlock doors from the Glofox app

note

This feature is available upon request. Contact Glofox support to enable it for your organization.

Members can unlock Kisi doors directly from the Glofox app, or from a Glofox custom branded app, without installing the Kisi app. If enabled, members tap Unlock Door on the Home screen and hold their phone close to the Kisi Reader to unlock. Android devices use NFC, while iOS devices use Bluetooth and Location Services.

note

On iOS, Apple Wallet may appear when unlocking. This doesn't affect access. To hide it, request the Pass Presentation Suppression entitlement from Apple.

To unlock from the Glofox app:

• The member must already be synced into Kisi for that branch
• The branch must be configured in the Glofox integration in Kisi
• The integration must be enabled

Each phone sign-in creates a Kisi login named Glofox Login on the member's account.

Remote unlock isn't supported from the Glofox app. Family accounts sharing one email address are also not supported.

To prevent members from sharing access, enable Primary Device Restriction. When a member unlocks with a new device, they're prompted to register it as their primary device. Each member can register a new primary device up to 3 times, and staff can reset this limit.

info

If you use the Glofox app, Glofox can enable tap to unlock without an app update. If you use a custom branded app, Glofox needs to publish a new build to the App Store and Google Play.

Sync member profile pictures from Glofox

Kisi can copy each member's Glofox profile picture to their Kisi user, so staff can match the person at the door with the photo in Kisi.

1. Click Settings on the integration page
2. Toggle Sync profile pictures
3. Click Save

When you turn the setting on, Kisi syncs the profile pictures of all members right away. After that, pictures stay up to date whenever a member is created or updated in Glofox, during the daily sync, and when you click Sync User for a member.

• The Glofox profile picture replaces any profile picture the Kisi user already has
• If a member removes their profile picture in Glofox, the existing Kisi profile picture is kept
• Pictures are synced for members with a membership and for members with bookings

info

Sync profile pictures is on by default for new Glofox integrations. Integrations set up before this feature was released start with it off.

Require a profile picture for membership access

You can block membership access for members who don't have a profile picture in Glofox, for example to make sure staff can verify every member's identity.

1. Click Settings on the integration page
2. Make sure Sync profile pictures is on
3. Toggle Require profile picture
4. Click Save

When this setting is on, the daily sync removes membership access from members without a Glofox profile picture. Once a member adds a profile picture in Glofox, access is restored at the next daily sync, or right away when you click Sync User for that member.

• Only the Glofox profile picture counts. A profile picture added directly in Kisi does not restore access
• If a member removes their profile picture in Glofox, they lose membership access at the next daily sync
• Booking access for Credit Pack and Pay-As-You-Go members is not affected
• Credentials assigned to the member are kept; only the membership access is removed

note

Require profile picture can only be turned on while Sync profile pictures is on. Turning off Sync profile pictures also turns off Require profile picture.

Card credential transfer from Glofox

It is possible to transfer barcode credentials from Glofox to Kisi and assign them to users. However, due to the large variety of credential formats used across different Glofox implementations, this transfer requires custom configuration.

Contact our support team to request credential transfer and to verify compatibility with your specific Glofox credential format.

Frequently asked questions

How to phase out old membership types while maintaining Kisi access for users who are still tied to those plans?

When setting up or editing a configuration in the Glofox integration, you may notice a trash can icon with the tooltip Show deleted Memberships. This option displays all deleted or deactivated memberships that still exist in your Glofox account. In this kind of setup your organization has stopped offering or creating new memberships of a certain type, yet the old members who were already subscribed continue to use their existing access and benefits.

To view and set up deleted memberships:

1. Go to your Glofox integration configuration page.
2. Click on the Mapping you want to edit or click on Add Configuration to add a new one.
3. Click the trash can icon next to Select Memberships to also show the deleted memberships still present in your Glofox account. The field changes to Select Existing and Deleted Memberships.
4. Choose the deleted membership. Selected memberships show an Active or Deleted status.
5. Continue the setup in the same way as with other memberships.

Why are my Glofox clients listed as users in Kisi before their membership is active, or after their membership has ended?

The Glofox integration will include all your Glofox clients as users within Kisi. When their membership is active, they will have shared access through a Kisi Group. When their membership becomes inactive, they are removed from the group; however, their user account will remain in Kisi for future use. Although they have a user account in Kisi, they will not have access to any doors. Additionally, if access was initially shared manually and not provided by the integration, it will not be automatically removed. While we don’t recommend adding users manually in Kisi, if it is necessary to temporarily grant access, please ensure that the access is either granted with a finite validity period or manually deleted once the integration issue is resolved.

Why are my Glofox clients receiving emails about granted access even though they already have an active membership and haven’t updated it recently?

If multiple members in Glofox share the same email address within the same branch, it can cause integration issues. These may include access problems, such as multiple “Access Granted” emails or temporary removal of access. To resolve this, update the email addresses in Glofox to ensure each member has a unique email.

Why do I see users in Kisi with emails ending in .invalid that don’t exist in Glofox ?

To prevent access issues with family memberships, Kisi creates a technical user for child accounts using the format {parent_email}.{parent_user_id}.invalid. These technical accounts are designed to avoid receiving any emails from Kisi and cannot be used to gain access.

Will manually added access be removed automatically when the membership ends?

Yes, if it was added to a group managed by the integration without an end date, it's removed during the next daily sync after the membership expires, after midnight UTC. Access shared with an end date is kept until it expires.

Can I delegate managing Glofox integration without giving organization administrator rights?

Yes, organization administrators can delegate Glofox integration management to non-admin users through custom roles:

1. Create a custom role with the following permissions:

• View Integrations (integrations_read)
• Manage Integrations (integrations_write)
• View Marketplace Installations (marketplace_installations_read)
• Manage Marketplace Installations (marketplace_installations_write)
• View Marketplace App Shares (marketplace_app_shares_read)
• Manage Marketplace App Shares (marketplace_app_shares_write)

2. Assign this custom role to the user who will manage the Glofox integration

3. Grant access to the Glofox integration configuration:

• Inside the Glofox integration, click on your email in the top right corner
• Click Manage User Access
• Select the person with whom access to Glofox needs to be shared

This allows designated users to manage the Glofox integration without requiring full organization administrator rights.

Understanding the integration logic

The User Info page in Kisi provides a tool to visualize and understand the rules behind access being granted or removed. It displays the data Kisi received from Glofox during the last synchronization.

1. Open Settings and click on Integrations > Configure Integration
2. Navigate to the User Info tab
3. Enter the member’s email, select a branch in Glofox, and click Search
4. Review the provided information. First, verify that there’s only one member in Glofox that corresponds to the email
5. Then ensure that the membership status is ACTIVE
6. Review the list of Groups included in this configuration and confirm if the member should have access to those groups
7. Note that if the interface indicates that more than one member corresponds to the same email address in Glofox, it may result in access issues for both members (see the next section)

tip

If you need to contact Kisi or Glofox support, please include a screenshot of this page in your support request.

Family memberships and duplicated emails in Glofox

Using the same email address for multiple users within the same Glofox branch is not supported by the integration. The most common instance of duplicate emails in Glofox occurs with family memberships, where a child account is automatically created using the same email address as the parent's account.

To prevent access issues in such cases, Kisi generates a technical user for child accounts using the format {parent_email}.{parent_user_id}.invalid. These technical accounts will not receive any emails from Kisi and, therefore, cannot be used for access.

Child members sharing the same email as their parents should access the facility using their parent’s Kisi account or by providing a separate email address for their own account in Glofox.

info

Other instances of multiple accounts using the same email address are not supported by the integration. In such cases, the emails must be updated in Glofox to prevent access issues, such as multiple access granted emails or temporary access removal.

Changing customer emails in Glofox

When a member's email changes in Glofox, Kisi moves their integration access and card to a Kisi user with the new email, and deletes the Kisi user with the old email. You don't need to do anything.

Manual access and integration override

The Glofox integration will override manual access assignments given to users without memberships during synchronization. Only access without an end date is removed. Access shared with an end date is kept until it expires, so grant temporary manual access with a finite validity period.

If you manually add a user to a Kisi group that is managed by the integration, and that user has an account with the same email address in Glofox, the integration will check their membership status during the next sync. If the user does not have the corresponding Glofox membership needed for the specific access group, they will be removed from that group.

This behavior ensures access remains consistent with Glofox membership status.

Uninstall the integration

Removing the Glofox integration deletes its Glofox settings and sync data. It doesn't remove the Kisi users, group access, or cards the integration created. Remove them manually if you no longer need them.