Managed Service Providers (MSPs)

Creating an Organization

In order to create a new organization for a customer/company, that will then contain their various networks, perform the following steps:

If the Organization dropdown is already present: 

1. Click the Organization dropdown in the top left corner. 
   
   
    
2. Scroll to the top and select MSP Portal.
3. On the MSP Portal, expand the Organization list by selecting the arrow in the left corner of the list. 
4. Select the Add Organization button. 
   
   

If the Organization dropdown is not present:

1. Sign-out of Dashboard if already logged in
2. Click Create an account
3. Enter the same Email and Password that is currently used for the MSP admin account (the generic address mentioned above)
4. Enter Company as the name for the organization (best used to identify the company/customer)
   • This can be changed later if needed under Organization > Settings
5. Address is optional and not required
6. Click Create account
7. The organization has been created. If a network needs to be created at this time, that can be done from this page.
   • If a network is not created at this time, the organization will only be available from the MSP portal page, and not from the Organization dropdown
   • It is recommended to create a network, even if left empty. It can be deleted or renamed at a later time.

If an Organization dropdown is not presented at this time, the account password may need to be updated in order to sync across organizations.

1. Click My profile in the upper right corner of Dashboard
2. Go to Change your password
3. Enter the account's current password in all three fields
4. Click Change password
5. Click Sign out in the upper right corner of Dashboard
6. Proceed to login, and an organization dropdown should be displayed

Best Practices

When creating new networks and organizations as an MSP, there are some best practices that increase the ease of management and prevent scalability problems as the service grows.

• Clone new customer organizations from an existing organization to preserve SP specific features
  • Some settings, such as branding or EoGRE, must be enabled by Support. Cloning from an organization that already has these features will prevent an extra call to Support as the SP specific features are retained during the cloning process. 
  • Please see the linked article for information on what settings are carried over during the cloning process
• Create networks and organizations using a generic shared address, such as meraki@example.com
  • Multiple admins can easily access and share this account
  • As admins change, the account remains the same
  • This account can be tied to a mailer list to ensure that, in the event of an alert or licensing issue, multiple parties are notified 
  • Additional admins can still be added with their own e-mails, after creation is done using the generic account
• Create separate organizations for each customer/company, since each organization will share the following across its networks/devices:
  • User accounts
  • Cisco Meraki VPN peers
  • 3rd party VPN peers
  • Licensing co-termination and feature set