Skip to main content

Integrate Kisi with Glofox

Glofox, part of the ABC Fitness Solutions brand, is a software platform designed for gym and fitness studio owners to manage their business operations, including scheduling classes, managing memberships, processing payments, and tracking performance.

Our integration allows Glofox admins to synchronize user memberships and bookings with their Kisi location and check users into Glofox whenever a relevant door is unlocked at that location.

info

This is a Kisi-built integration, maintained and supported by Kisi.

Prerequisites

  • Kisi organization administrator rights
  • 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

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. Open Settings and click on Integrations > Add Integration
  3. Define the name of your new Glofox integration.
  4. Open the Type dropdown and select Glofox Gym Management Software.
  5. Next, click Add Configuration and enter your Glofox Location ID (the Location ID for your Glofox setup).
  6. Select the Kisi Group to which users with active memberships will be imported.
  7. Select a Place to map with this Glofox location for check-in.
  8. Specificy Glofox Membership types to sync to the group.
  9. Enable Bookings Enabled if Credit Pack and Pay-As-You-Go users should also be imported.
  10. Enable the integration.
  11. Click Add.

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 will be updated in Kisi in real time, ensuring your data is always accurate.

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.

Common questions

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.

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.

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.

Kisi scans for upcoming bookings, by default granting access one hour prior to a scheduled class and revoking it immediately afterward. These settings can be adjusted on the integration page to specify the duration before or after the class that access should be granted or removed. Note that access will be granted at the start of this period and the member will receive the email notification.

With the latest update, the integration now supports instant bookings: if a class is booked during the specified access period, door access will be granted immediately.

Example: 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.

Check Kisi users in through Glofox

Glofox members will need to sign up with Kisi to unlock doors. When a user with access granted through the Glofox integration unlocks a door at a location, Kisi will check them in with Glofox at the location mapped to that place in the integration settings.