# Network Policies
For some WiFi vendors, you need to setup Network Policies before creating Tenants. The section Network Policies in the Integration page appears automatically based on the WiFi vendor you set up.
## Meraki
While creating an iPSKs, Meraki require to set a Group Policy. By creating Network Policies, Cusna automatically creates and keeps in sync the Group Policies in the Meraki account for all the network involved (one network per each Network)
Click **Add a new Policy**.
The New Network Policy dialog appears. Fill the form
* name: reference name for the policy (e.g. "Default")
* bandwidth downlink: max downlink spee in Kbps
* bandwidth uplink: max downlink spee in Kbps
* VLAN
Click **Save**.
The Network Policies create appears in the list.
### Using Network Policies
Once you have created network policies, you can use them in different ways.
First of all, whenever you create a Network, you'll be required to assign a "default" network policy. This is the policy that will be assigned by default to Accounts associated to that Network whenever the network policy is not specified on the Account during initialization.
When creating a new account manually, you can opt to use the Network default network policy, or you can manually pick one of those you have already initialized in setup.
You can also assign a Network Policy to a group. This will be assigned to all Accounts of type "*group member*" assigned to this group.
Finally, you can also assign Network Policies individually to each Accoutn when creating or managing them form the dashboard.
### Troubleshooting Network Policies
Network Policies sync with equivalent entities in the network management system. For example, each Network Policy is deployed as a Group Policy in each Meraki Network connected to a Cusna Network.
In order to check the matching Group Policies in the Meraki network, you can click the info icon on the Network Policy card. A dialog will show the list of the matching Group Policies in each Meraki Network.
{% hint style="info" %}
In case a Group Policy already exists in the Meraki Network with the same name assigned to the Network Policy in Cusna, Cusna will attempt to create it with a slightly different name, adding a numerical suffix to the name (e.g. \\_1)
{% endhint %}
{% hint style="info" %}
All policies initializd on the network are forced with the prefix "**CU-**" in front of the name you select.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cusna.io/service-management/network-policies.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.