Restrict Meraki Dashboard Access: MFA & Roles
This guide shows you how to lock down your Cisco Meraki dashboard by enforcing multi-factor authentication (MFA) and assigning role-based permissions. You’ll learn to require a verification code for every admin login and to limit what each user can see and do, reducing the risk of unauthorized changes and data exposure. You’ll need Meraki dashboard access with Org-wide Admin privileges to complete these steps.
What You’ll Need
- Meraki dashboard login with Organization-wide Admin privileges (Full access).
- A supported authentication method for MFA: a smartphone with an authenticator app (e.g., Google Authenticator, Microsoft Authenticator) or a hardware token (e.g., YubiKey).
- If you use SAML SSO, you’ll need access to your identity provider (IdP) admin console to configure MFA there (optional but recommended).
Step-by-Step
Part 1: Enforce Multi-Factor Authentication
- Log in to the Meraki dashboard at
dashboard.meraki.comwith an account that has Org-wide Admin privileges. - Go to Organization > Settings (or Organization > Configure > Settings in older UI).
- Scroll to the Authentication section.
- Under Multi-factor authentication, select Enabled.
- If you have SAML SSO enabled, you’ll see an option to Require MFA for SAML logins as well. Enable this if your IdP supports MFA (recommended).
- Click Save Changes at the top right.
- Now, each admin must set up MFA on their next login. They’ll be prompted to scan a QR code with an authenticator app or enter a hardware token key.
- For existing admins, you can also force them to enroll immediately by clicking Organization > Admins, selecting the admin, and choosing Force MFA enrollment (if available in your UI version).
Part 2: Configure Role-Based Permissions
- In the Meraki dashboard, go to Organization > Admins (or Organization > Configure > Admins).
- Click Add Admin (or + New Admin).
- Enter the admin’s email address (this is their login ID) and a display name.
- Under Access, choose one of the following:
- Full access – grants all permissions across all networks. Use sparingly.
- Read-only – allows viewing but no changes.
- Network-specific – select specific networks and then assign a role (e.g., Network Admin, Help Desk).
- If you choose Network-specific, you’ll see a list of networks. Check the ones this admin should manage.
- Then, under Role, select a predefined role or create a custom one:
- Network Admin – full control over the selected networks.
- Help Desk – read-only plus limited troubleshooting tools (e.g., ping, reboot).
- Custom – click Create new role to define exactly which permissions (e.g., “Can modify SSID settings” but not “Can delete networks”).
- After setting the role, click Save.
- To modify an existing admin, click on their name, change the access level or role, and save.
Part 3: Review and Audit
- Go to Organization > Admins to see a list of all admins and their roles.
- Use the Audit log (Organization > Audit log) to review admin actions and ensure only authorized changes are made.
- Periodically review the list to remove inactive accounts or adjust roles as staff change.
Common Mistakes
- Not enabling MFA for SAML users – If you use SAML SSO, MFA must be enforced at the IdP level. Simply enabling MFA in Meraki won’t protect SAML logins unless you also require it there.
- Giving “Full access” too liberally – Even trusted employees should have only the permissions they need. Full access can lead to accidental or malicious changes across all networks.
- Ignoring the “Force MFA” option – Existing admins may not be prompted to enroll MFA until their next login, which could be weeks away. Force enrollment immediately after enabling.
- Using the same role for all networks – If you have networks with different sensitivity levels, assign different roles per network rather than a blanket role.
Tips
- Use custom roles to match your team’s responsibilities. For example, a “Junior Admin” role could have permission to reboot devices but not to change firewall rules.
- Enable MFA enforcement before announcing it to admins, so they aren’t locked out without knowing the process.
- For SAML SSO, configure MFA in your IdP (e.g., Azure AD, Okta) to enforce a second factor on every login, including Meraki.
- Set up a break-glass admin with full access and MFA, but store the recovery codes securely in case of emergencies.
- Regularly export the admin list and roles to a spreadsheet for documentation and review.
Troubleshooting
- Admin can’t log in after MFA is enabled – They may have lost their authenticator app. As an Org admin, you can reset their MFA by going to Organization > Admins, clicking the user, and selecting Reset MFA. They’ll need to re-enroll.
- MFA prompt not appearing – Ensure the admin is logging in via the correct URL (
dashboard.meraki.com) and not a cached page. Try a different browser or incognito window. - Role permissions not applying – Check that the admin is assigned to the correct network and role. Sometimes admins are added at the organization level, overriding network-specific roles.
- Can’t find the MFA setting – The setting is under Organization > Settings > Authentication. If you don’t see it, ensure you have Org-wide Admin privileges.
- SAML users not prompted for MFA – Confirm that your IdP has MFA enforced for the Meraki application. In Meraki, also enable the “Require MFA for SAML logins” checkbox.
Frequently Asked Questions
Can I require MFA only for certain admins?
No, MFA enforcement is organization-wide. Once enabled, all admin accounts (including SAML users if you check that box) must use MFA.
What happens to API-only admins?
API-only admins (created for scripts) do not log in to the dashboard, so MFA doesn’t apply to them. However, you should still restrict their permissions using roles and use API keys with limited scopes.
Can I use SMS for MFA?
Meraki’s built-in MFA uses authenticator apps or hardware tokens. SMS is not supported directly. If you use SAML, your IdP might offer SMS as an MFA method.
How do I create a custom role?
Go to Organization > Admins > Add Admin, choose Network-specific, then click “Create new role” next to the Role dropdown. Name the role and check the permissions you want to grant.
Will MFA lock out all admins if I enable it?
No, but each admin will need to enroll their MFA device on their next login. To avoid lockout, communicate the change and provide instructions before enabling.
Can I delegate role management to someone else?
Yes, if you create a custom role with the “Manage admins” permission, that admin can manage other admins’ roles, but they cannot change your organization’s MFA settings unless they have full access.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.