The Meraki dashboard explained

What the Meraki dashboard is

The Meraki dashboard is a single web console, hosted by Cisco Meraki, for every Meraki product family: wireless access points, switches, security and SD-WAN appliances, teleworker gateways, cellular gateways, cameras and (for existing users) sensors and Systems Manager. It is also where select Catalyst switches and Cisco's Wi-Fi 7 access points are managed when they run in cloud mode.

There is no dashboard to install and no separate dashboard product to buy. Each device needs a valid licence to operate, and licensed devices are managed in the dashboard. You sign in from a browser (see Meraki dashboard login) or from Meraki's mobile app.

Because devices only send management data to the cloud, the dashboard is how you run the network, not the path your traffic takes. Our what is cloud networking guide explains that split.

Organisations, networks and tags

The dashboard has a simple structure, and getting it right at the start saves work later.

• Organisation: the top level, usually one per company. Licensing, inventory, administrators and organisation-wide settings live here. The licensing model (subscription, co-term or per-device) applies to the whole organisation.
• Network: usually one per site. A network can hold several device types, for example access points, switches and a security appliance, which the dashboard shows as one combined network.
• Configuration templates: a template is a network whose settings are pushed to many bound networks, so a chain of branches can share the same SSIDs, VLANs, firewall rules and policies while keeping local differences where allowed.
• Tags: labels on devices and networks used to apply settings, filter views and limit what some administrators can see.

If you operate in more than one hosting region, Meraki advises a separate organisation for each region. We can help design this structure before anything is claimed.

What you can do in the dashboard

• Monitor clients and devices: see every connected device, its usage, the access point or switch port it is on, and its connection history.
• Topology: view a diagram of how switches, appliances and access points connect, including switch stacks.
• Alerts and webhooks: send alerts by email or to other systems through webhooks when devices go offline, settings change or thresholds are crossed.
• Firmware scheduling: schedule upgrades per device type for each network, or in bulk across the organisation, with rollback of a recent upgrade within 14 days.
• Administrators and roles: organisation-level and network-level admins with full, read-only and more limited roles, plus two-factor authentication and SAML single sign-on.
• Inventory and licensing: claim orders and devices, see licence status and expiry, and see end-of-sale and end-of-support dates for your devices.
• Change log: see who changed what, and when, across the organisation.
• Mobile app: check status and make common changes from a phone.

The Meraki Dashboard API

Everything you can see in the dashboard can also be reached programmatically through the Meraki Dashboard API, an HTTPS API used for automation, reporting and integration with other tools: bulk changes, inventory and licence reports, provisioning new sites from a script, or feeding data to a monitoring or ticketing system.

How access works, according to Cisco's developer documentation:

• API keys are generated by each dashboard administrator under Organization > API & Webhooks.
• A key carries the same permissions as the administrator who created it, in each organisation that admin can access.
• Each identity can hold up to two valid API keys at a time, which makes it possible to rotate keys without downtime.
• Administrators who sign in through SAML single sign-on cannot use the Dashboard API, so key-based automation usually runs under a dedicated, well-protected admin account.
• For third-party applications and organisation-wide automation, Meraki also offers app-scoped access through OAuth 2.0 grants instead of personal API keys.

Treat API keys like passwords: store them in a secrets manager, give the owning account the least access it needs, and revoke keys that are no longer used.

Catalyst, Wi-Fi 7 and Cisco Cloud Control

The dashboard is no longer just for Meraki-branded hardware.

• Cloud-managed Catalyst switches: select Catalyst switches can be onboarded and fully configured in the Meraki dashboard. Meraki's earlier monitoring-only option, Cloud Monitoring for Catalyst, is no longer available for new devices, and Meraki recommends cloud management instead. See Catalyst in the Meraki dashboard.
• Wi-Fi 7 and Smart Switches: Cisco's newest access points and Smart Switches can run in Meraki cloud mode, or in a mixed mode where licences and inventory sit in the dashboard while devices are managed on premises. See Meraki Wi-Fi 7.
• Catalyst Center visibility: Meraki's Global Overview can show Catalyst Center-managed networks alongside Meraki organisations.
• Cisco Cloud Control: Cisco's new single management plane across networking, security and more links to your Meraki organisations for alerts, topology and workflows. Cisco's release notes record general availability on 25 August 2026 for customers and partners managing US-based infrastructure, and say it works without replacing individual product dashboards, so the Meraki dashboard continues as the console for Meraki devices. See Cisco Cloud Control.

Meraki dashboard setup, in outline

1. Create the organisation and choose the hosting region, then add at least two full organisation administrators with two-factor authentication.
2. Claim your order or licence keys, which adds devices and licences to the organisation inventory.
3. Create networks for each site, or a configuration template for sites that should share settings.
4. Add devices from inventory to their networks, and name them clearly.
5. Set up addressing and VLANs, SSIDs, switch port profiles, firewall and VPN settings.
6. Set alert recipients, firmware upgrade windows and administrator roles.
7. Connect devices on site; they contact the dashboard and download their configuration.

That is the dashboard side only. A good deployment also includes a survey, a design and a cutover plan; our Meraki setup page covers the full process, from survey to go-live.

Common dashboard mistakes to avoid

• One administrator only: if that person leaves or loses their phone, you can be locked out. Keep at least two full organisation administrators with two-factor authentication.
• Shared logins: every person, including suppliers, should have their own admin account so the change log shows who did what.
• No naming scheme: devices left with default names make alerts and topology hard to read. Name by site, floor and role from day one.
• Templates added too late: binding existing networks to a template later means reworking them. Decide early which sites should share settings.
• Unread alerts: alerts sent to one person's inbox get missed. Send them to a shared mailbox or another system through webhooks.
• Firmware left to chance: set upgrade windows that suit each site, and test new versions on a small network first.
• Licences forgotten: under co-term, one expiry date covers the whole organisation. Put it in the diary well ahead, and see what happens when a Meraki licence expires.

How Forever Systems helps

Forever Systems is a Cisco Partner. We can design your organisation and network structure, build templates and policies, migrate an existing network into the dashboard, tidy up admin access and licensing, and help your team find their way around. If you already run Meraki, we can review your dashboard against good practice and suggest improvements.

For supply and installation of Meraki hardware, see our main Cisco Meraki service pages, or contact us to talk it through.