---
sourceDocument: Brazil Telecommunications Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-service-ops

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Configure Cisco Meraki allowlists

# Configure Cisco Meraki allowlists {#ariaid-title1}

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure connector definitions to limit polling to specific Cisco Meraki organizations.

## Before you begin

Role required: tsom_visibility_admin

## About this task

Use multiple connector instances with disjoint allowlists to distribute collection across MID Servers and avoid polling interval overruns in large-scale deployments. Only listed entities are
included in the polling scope; all others are silently excluded.{#configuring-allowlist__configuring-allowlist-context-1}

## Procedure

1. Navigate to AllEvent ManagementIntegrationsConnector Definitions.
2. Search for <kbd class="ph userinput">Meraki</kbd> in the search field.
3. Select the connector from the list, then the connector instance.
4. In the organizationsToWhitelist field in the Connector Instance Values section, enter the organization names to be included in the polling scope, separated by commas.  
   For example, <kbd class="ph userinput">CompanyG,Corp,SoutheastRegion</kbd>.
5. Select Update.

## Result

The connector applies these values at each polling cycle.

*[\>]: and then