What is the Cisco Meraki Wi-Fi Integration?
The Cisco Meraki integration connects your workplace Wi-Fi network with Gable. When employees join your Meraki network, Gable can automatically recognize presence and mark check-ins, or set up a Gable booking if necessary. This creates a seamless experience without manual steps while also providing accurate usage insights.
Key Benefits:
✅ Automated check-ins when users connect to Wi-Fi
✅ Reduced manual errors and missed check-ins
✅ Stronger workplace usage reporting and analytics
📍 Before You Begin
Make sure you have:
Admin access in Gable
Admin access in Cisco Meraki
The Cisco Meraki add-on enabled in your Gable account (contact support@gable.to or your CSM if you don’t see it)
⚠️ Important: Disable MAC Address Randomization
To ensure accurate device identification and reliable network reporting, MAC address randomization must be turned off on employee devices.
When MAC randomization is enabled, devices generate temporary MAC addresses that change over time. This prevents Gable from consistently recognizing devices on the network.
👉 Please ensure MAC randomization (also called “Private Wi-Fi Address” on some devices) is disabled for your corporate Wi-Fi network before proceeding with the integration setup.
🛠️ How to Connect Cisco Meraki to Gable
Navigate to the Integration in Gable
Log in to your Gable account.
Go to your Profile drop-down > Company Admin > Settings.
Click Integrations on the left-hand menu.
Scroll down and locate the Cisco Meraki tile.
👉 If the tile shows a lock icon, the add-on isn’t enabled. Reach out to Gable Support or your CSM.
Authorize the Connection
Click Connect on the Cisco Meraki tile.
Select your Cisco Meraki Organization from the prompt.
Click Allow to grant access.
Configure Integration Settings
Slack Channel: Choose a Slack channel where Wi-Fi error notifications will be sent.
Hosting Region: Select your dashboard hosting region (Default or custom). You’ll see an error if the wrong one is chosen.
Device Management: Choose how to map employees to devices. Options include:
✅ RADIUS
✅ CSV Upload - download template, fill in, and upload
✅ iru (formerly Kandji) - enter API Key + API URL
✅ Jamf - enter Client ID, Client Secret and API URL
💡 You can use multiple options. Gable will check them in priority order: RADIUS → CSV → Kandji → Jamf.
Network Mapping
Map your Cisco Meraki Networks to your Gable Offices.
Offices appear on the left; Networks on the right.
If time zones don’t match, an error will appear until corrected.
You can only mapped published offices, NOT drafts.
Save Your Settings
Click Save when all fields are complete.
If the button is grayed out, confirm that all required information (like API keys) is entered.
🛠️ How Check-In Works
When a user connects to Wi-Fi, Gable follows this priority order to secure or check-in a booking:
✅ Existing Booking → auto-marked checked in.
🏢 Private Office (only user assigned) → booked.
🏢 Private Office (shared) → booked if user is assigned.
💺 Desk in common space (only user assigned) → booked.
💺 Desk in common space (shared) → booked if user is assigned.
👥 Department-assigned desk → booked.
🌐 Unassigned desk available → booked.
🔄 If onsite booking is enabled → creates onsite booking (unassigned).
🚨 Fallback → if none apply, Admin notified.
🎥 Video Walkthrough
❓ Additional Information & FAQs
🔐 How does the Meraki integration authenticate?
Gable integrates with Cisco Meraki using OAuth authentication.
✅ Admins grant access via a consent screen during setup
🔎 Access is read-only
🚫 Identity and access management permissions are explicitly excluded
🏢 Access is limited to the specific Meraki organization selected during authorization
📊 What data does Gable retrieve from Meraki?
Gable requires the following fields:
📡 Device MAC address
📍 Network or location identifier
🕒 Connection timestamp
Meraki’s API responses may include additional connection metadata, but Gable only utilizes the required fields listed above.
🔑 How does the Jamf integration authenticate?
Gable integrates with Jamf Pro using the Jamf Pro API.
🔐 Authentication is done using a Client ID and Client Secret provided by your team
📥 Access is limited to the scope granted by those credentials
Gable only accesses the fields required for the integration and does not expand beyond the permissions defined by your Jamf configuration.
❓ Need More Help?
If you need assistance with setup, reach out to us using the chat bubble in the bottom right corner or via email at support@gable.to.