Skip to main content
You connect Meraki once at the MSP level, with one Dashboard API key.

1. Generate the API key

1

Pick the admin

The key acts as the dashboard admin who generates it, in every organization that admin can see. Use an admin with access to your clients’ organizations. A key from a read-only admin lets Neo read only. An admin who signs in only through SAML cannot generate a key.
2

Generate the key

In Organization → API & Webhooks, open API keys and access and click Generate API key. Copy the key: Meraki shows it once. An admin can hold two keys.
Do not revoke the key in Meraki after you connect it. Neo loses access until you save a new key here.
If an organization accepts API calls only from approved IP addresses, add every address on IP Whitelisting to it. Otherwise Meraki refuses Neo’s calls to that organization with “not within an approved subnet”.

2. Add the key in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations → Cisco Meraki, under Networking.
2

Save the key

Enter the API key. Leave Region on Global unless you sign in to Meraki at a Canada, China, India or US FedRAMP address. Click Save settings. Neo checks the key against Meraki before saving, so a wrong key or region is rejected straight away.

3. Turn Meraki on per agent

Open the agent, go to its Tools & Settings tab, click Networking, and expand the Cisco Meraki block. Agents reach only the organizations the key’s admin can see.

Pick a preset

Read Only

Read every area. Nothing is changed.

Helpdesk

Read every area. Device, client and switch port actions (reboot, port cycle, cable test, block a client) wait on a technician.

IT Admin

Read and change every area. Security Appliance & VPN, Wireless and Administration changes wait on a technician.

Full Automation

Read and change every area without approval, apart from the changes below that always ask.

Or set each area by hand

Each area takes Disabled, Read Only or Read/Write, and has its own technician approval setting.

Changes that always ask a technician

Whatever the profile, a technician approves: deleting a network; wiping or unenrolling a Systems Manager device; and every creation or change of a Meraki Authentication user (802.1X, splash and client VPN accounts), even one that changes only a name or an authorization, because either call can set the account’s password. Every other change, including dashboard admins, SAML, login security, combining or splitting a network and removing or releasing a device, follows the approval setting of its area.

What Neo never sends

Neo refuses: deleting an organization, turning off an organization’s API access, action batches, creating or revoking API keys, vMX authentication tokens, packet captures and camera snapshots.