Cisco Meraki is the leader in cloud controlled Wi-Fi, routing and security. Cisco Meraki provides devices and software to help businesses manage Wi-Fi network access for employees and guests.
How does this integration work?
Upon sign-in, visitors will receive an email or text message directing the visitor to visit an Envoy-hosted guest Wi-Fi splash page. This page will display Wi-Fi access instructions, along with network and password details. The unique credentials created for each visitor are valid for 24 hours or less as specified during configuration. The specified time chosen during set up is only to set the amount of time that the password is valid for, it does not control the ending of the visitors session. If they have signed into the network with their credentials, the only way to end the session on Envoy's side would be to sign the visitor out.
Note: For this integration to work, you must collect either visitor email addresses or phone numbers at sign-in. Learn more about how to configure your Envoy sign-in fields.
Enabling the Envoy + Meraki integration
Under Wi-Fi, find Cisco Meraki, and click “Install.”
Log into Cisco Meraki, navigate to Organization > Settings. Locate the section titled Dashboard API access and select Enable Access, then save your changes.
Choose your username at the top-right of the Meraki dashboard and select My profile. Locate the section titled Dashboard API access and click on Generate new API key. Store your key in a safe place.
• Note: If you do not see a button labeled “Generate new API key” then the API quota may be full. In this scenario it is necessary to remove an API key before a new API key can be generated or locate an already generated key for use in the Envoy config.
In Envoy, paste the Meraki API key and click “Save Configuration”.
• If your company uses combined networks you will need to click on the link provided in step one and paste what generates.
6. Select your desired Guest Network from the dropdown and click “Next Step”.
• If you do not see your Guest Network name go back to step one in the setup and follow the steps under Combined Networks Support.
7. Select your desired SSID from the dropdown.
8. Select Visitor types to optionally block from receiving Wi-Fi credentials.
9. Add your logo (optional).
• If you’d like your logo to appear on your splash page and in the email visitors receive, you’ll add a logo here.
• In the Custom logo field, provide the full URL for your hosted logo (including http://).
• In Cisco Meraki, list the domain where your logo is hosted in the Walled Garden section.
10. Add a custom message (optional.)
• You can showcase a custom message on your splash page.
11. In the Welcome message field, type your desired message. You can format the message using markdown.
12. Send guest Wi-Fi credentials to hosts (optional.)
• This is useful when visitors do not have easy access to email or text messages or if they are not required to enter their email address or phone number at sign in.
13. Click “Complete setup.”
Note: The settings on Meraki should automatically generate via the API. Please ensure that the Splash page is set to
What is the visitor experience with the Envoy + Cisco Meraki integration?
When a visitor signs in, they will provide their email address and/or phone number. The visitor will receive an email or SMS with instructions on how to access your Wi-Fi.
When they follow the instructions in the email or SMS, they will be directed to the Envoy-hosted splash page. There, they’ll enter the password and will connect to Wi-Fi.
To view all the active connections within your access point, you can do the following: Within Wireless > Access Points > on the Meraki dashboard, click into your access point and then scroll down to Clients. The numeric IDs listed under the Clients section will be the Entry IDs for your Envoy Visitors connected to your network.
Even though we ask the SSID to be set to “Open”, authorization goes through an Envoy hosted splash page in which the visitor inputs credentials created and provided by Envoy.
The default session timeout for passwords is 24 hours, which is not changeable in Meraki. We expire the user when the visitor is signed out, this is not configurable from the Envoy side, however, you have the option to update the "Splash Page" frequency within Meraki.
What is the difference between V1 and V2 of Meraki?V2 has more functionality to blocklist by visitor type from receiving credentials, and connects directly to the Meraki API, therefore when visitors sign out, their session ends automatically. The update also lets your Security team easily cross-reference internet activity to specific visitors.