Skip to main content
Cisco Meraki Documentation

Organization Settings

From the Organization > Configure > Settings page you can update the name of or delete an Organization, modify security settings for Administrator accounts, and configure API and SNMP access for the Organization. 

Organization Name 

Change the name of the Organization using the text box. The Organization name is simply an identifier for the Organization and can be changed at any time.

An organization name can have a maximum length of 255 characters

Security Settings

  • Password expiration: Configure password expiration timer in Days
  • Used passwords: Restrict the number of re-used passwords
  • Strong Passwords: Enforce strong password policy
    • Users will be forced to choose secure passwords of at least 8 characters that contain 3 of the following:
      • number
      • uppercase letter
      • lowercase letter
      • symbol ( ! @ # $ % ^ & *, etc )
    • Users will not be able to use a password containing common words or names
  • Account lockout: Configure how many times a user can enter the wrong password before being locked out
  • Idle timeout: Configure how long a user can be inactive for before they are logged out
  • Two-factor authentication: Force all users in the organization to configure and utilize two-factor authentication (2FA)
  • Login IP ranges: Specify IP ranges from which administrators can access the Dashboard as well as Dashboard API

Login IP ranges has two options to select from. Option one is to allow dashboard and API access to the specified IP ranges. Option 2 is to allow API access only. If both options are selected you need to specify the IP address range in the two options to be able to use the API. 

Security Settings do not apply to SAML Administrator accounts.
Exceptions: Idle timeout, SAML users are limited by the shortest idle timeout value in any of the organizations they are part of.

MSP accounts with multiple organizations having different idle timeouts configured, will follow idle timeout on a per-organization basis. Users are subjected to the minimum idle timeout across the organizations they are currently visiting.

RADIUS servers 

Define a RADIUS server at the organization level. These RADIUS servers can be selected and applied to any Switching access policy within the organization. This section shows the full list of RADIUS servers in the organization and the networks where the RADIUS servers have been applied. Expand "Actions -  see where it's applied" to see a full list of access policies where the RADIUS servers have been applied. 

When editing an existing RADIUS server, the update will be applied to all networks and access policies that utilize the RADIUS server. 

The RADIUS servers defined here are currently only applicable to MS and CS switching access policies. 



Use the dropdown to enable and configure SAML login information for Dashboard Administrators. For more information about configuring SAML logins please refer to the following documentation.

Configuring SAML Single Sign-on for Dashboard 

Configuring SAML SSO with ADFS

Configuring SAML SSO with OneLogin


image (3).png

Manage Alerts

  • Licensing - When "Licensing" is chosen, only Organization Admins will receive licensing alerts.
  • Licensing, hardware defects, maintenance - When "Licensing, hardware defects, maintenance" is chosen these types of alerts will be sent to the selective Dashboard Administrators in the text box located below "Send to selective Dashboard administrators".
    • Only Dashboard Administrators that are configured on the organization are a valid option for the text box.
    • The text box allows for multiple Dashboard Administrators to be input as long as they are separated by commas.
  • None of the Above - When "none of the above" is chosen, Organization Admins and all Network Admins in this organization will receive notifications.

Special Announcements

Special announcements are notifications that may not be network-specific. For example, Scheduled maintenance notifications for Meraki dashboard.

  • All organization admins with full access - All special notifications will be sent to all full organization administrators on the dashboard.
  • Send to a mailing list you manage - You can create a list of email addresses that will be the only recipients of the special announcements

All organization-wide alerts will be sourced from the same email address. To ensure that alerts are not being lost to a spam filter, please be sure to add, and as trusted email sources.

Manage visibility of Dashboard Banners

This feature allows you to control the types of banners displayed on your Meraki dashboard at the organization level. Banners are separated into two categories: Critical and Non-Critical.

  • Critical Banners - Critical banners include notifications of global server outages, emergency server maintenance, and large-scale incidents.
  • Non-Critical Banners - Non-Critical banners include notifications of system maintenance, firewall test warnings, firmware upgrades, cloud authentication certificate rotation notifications, any product-related announcements, cloud archive migrations, and invalid VLAN tags.

Configuration options include the following:

  • Display Critical and Non-critical dashboard banners - All Critical and Non-Critical banners are displayed.
  • Display only Critical dashboard banners - When chosen only Critical banners are displayed on the dashboard while hiding Non-Critical banners.
  • Hide Critical and Non-Critical dashboard banners - This option allows users to remove the visibility of both critical and non-critical banners on the dashboard. This means that any banners classified as critical or non-critical will no longer be visible on the dashboard once this option is selected.

When choosing the option to "Hide Critical and Non-Critical dashboard banners" it is important to note that security-related banners, such as those related to weak passwords or the need to enable two-factor authentication, will still be displayed. This is to ensure that users are aware of and take action on important security vulnerabilities.

Meraki Support Access

Checking the "Block Meraki Support" box will prevent Meraki Support from viewing any information about your Organization or any networks within that Organization.

For more information about controlling Support access please refer to this documentation.

This setting will need to be disabled to receive assistance from Meraki Support.


When enabled, new networks will be created with privacy-sensitive features disabled by default. You can turn these features on at any time. For example, location analytics will initially be disabled in the new network but you can turn it on at any time.


Use the appropriate dropdown menu to enable SNMP access for the Organization. This enables SNMP polling of the Organization through the Dashboard Cloud Controller. To enable SNMP polling directly to devices from a local NMS, you will need to go to Network-wide > General and enable SNMP access on a per-network basis. For more information about configuring SNMP please refer to our SNMP Overview and Configuration Guide.

Threat Grid

Use the dropdown menu to enable and configure Threat Grid integration. Threat Grid requires an Advanced Security license to integrate with the Dashboard in addition to a Threat Grid subscription. For more information about Threat Grid please refer to our documentation on Threat Grid Integration.

API Access 

Check the box to Enable API access to the Organization. The dashboard API can be used for many purposes including:

  • Add new Organizations, Administrators, Networks, Devices, VLANs, and more
  • Configure large numbers of networks in just a few minutes with API calls
  • Automatically on-board and off-board new employees' teleworker setup
  • Build your own dashboard for store managers, field techs, or unique use cases 

For more information on configuring and utilizing the Dashboard API, please refer to our API Documentation

MSP Identification

This ID field is for Service Providers to fill in with their ID if they're managing or assisting in the management of the Organization.

Delete an Organization

To delete an Organization, you must ensure that there are no non-Administrative Users listed under Network-wide > Users, there are no Networks listed under Organization > Overview, there are no active Licenses listed under Organization > License Info, there are no devices claimed in the Organization > Inventory, and that the currently logged in Administrator is the only remaining Administrator under Organization > Administrators. Only if all of the above requirements are met will you be able to delete the Organization.

Warning: Deleting an Organization is permanent. There is no way Meraki Support can recover an Organization once it has been deleted.

  • Was this article helpful?