> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/enterprise-portal/allowed-networks.md). # Allowed networks A project's **allowed networks** list defines which mobile network operators (MNOs) your IDlayr verifications can route to. This is both a **technical** boundary (IDlayr needs connectivity to the MNO) and a **commercial** one (your organisation needs to be approved to use that MNO for the specific product). For background on why this list exists and how it interacts with the platform, see [Allowed networks (concept)](/get-started/concepts/allowed-networks.md). This page covers what you see and do in the Portal. ## What you see in the Portal From a project's detail page, the **Approved network traffic rules** section lists the MNOs the project is approved to use, the products each MNO is approved for, and any per-MNO context. If you've just created a project and the list is empty: > "There are no approved networks for this project." This is normal. New projects start without approved networks; they're added by IDlayr as part of the production-enablement flow. ## Adding networks to a project Networks are added by **IDlayr**, not by you. Adding a network involves verifying that IDlayr has connectivity to the MNO, that your organisation is approved by the carrier (or by IDlayr's commercial agreements with the carrier) for the relevant product, and that any operational and compliance requirements are in place. To request a new network: 1. Identify which MNO(s) you need, in which markets, for which products. 2. Contact your IDlayr account team — see [Support](/help-center/readme/support.md). 3. Provide the project name, the target MNO(s) and country / region, and the use case. 4. Once approved, your project's allowed networks list updates and the project can route traffic to the new MNO immediately. ## How the allowed-networks list is enforced The list is enforced at the platform layer. A verification call against an MNO that isn't on your project's allowed list returns an error (typically `mno_not_supported`) — regardless of whether the MNO is technically reachable from IDlayr's side. This is the same gate that [Eligibility](/products/eligibility.md) checks: a product reports as eligible only when (1) IDlayr has connectivity, (2) your project's allowed networks include the MNO, and (3) the MNO supports the IDlayr product in question. Running Eligibility before a verification is the cleanest way to know in advance whether a call will succeed. ## When the list changes When networks are added to or removed from your project, the change takes effect immediately. Existing in-flight verifications complete against the previous list; new verifications use the updated list. You'll see network additions reflected in the Portal as soon as they're approved on IDlayr's side. If you're expecting a network to appear and don't see it, contact your IDlayr account team. ## Per-project, not per-workspace Each project has its own allowed networks list. Two projects in the same workspace can have different lists — useful if you have different use cases approved for different MNO subsets. A sandbox project doesn't need approved networks for testing — sandbox traffic is simulated and never touches MNOs. The allowed-networks list mostly matters for production projects. ## What's next * [**Eligibility**](/products/eligibility.md) — pre-check whether a phone number or IP is supported under your project's allowed networks. * [**Allowed networks (concept)**](/get-started/concepts/allowed-networks.md) — the platform-level background. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.idlayr.com/enterprise-portal/allowed-networks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.