> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectivity-management/ztna/network-mapping-routes.md).

# Network Mapping (Routes)

Learn how to view, create, edit, delete, and bulk-upload ZTNA routes on the Digibee Integration Platform.

A **Network Mapping** (route) connects a host and port on your network to a Digibee pipeline, through an Edge Router. Each route is linked to an **environment** (Test, Prod, or Prod & Test).

## **Adding routes**

### **Manually**

{% hint style="info" %}
Only users with the [connectivity-manager role](/documentation/platform-administration/administration/new-access-control/access-control-roles.md#connectivity-manager) can add routes.
{% endhint %}

1. Click the Digibee logo in the upper left corner, then **Connectivity**, and access the **Network Mapping** tab.
2. Click **Add Network Mapping** and select **Using form**.
3. Fill in the fields:
   * **Ports**: single port or a range (`xxxx-xxxx`).
   * **Host:** the DNS or IP address of the resource you're mapping.
   * **Host alias** (required if Host is an IP instead of a DNS — toggle this on to reveal the field).
   * **Environment**: Prod, Test, or Prod & Test.
   * **Edge Router group**: the group to associate with this Network Mapping.
4. Click **Save** to create the route, or **Cancel** to go back.

### **In batch**

1. Click **Add Network Mapping** and select **In batch (csv)**.
2. Download the CSV template file. 
3. Once you set up your file, click **Upload CSV** and select your CSV file.
4. Review the preview table before confirming.
5. If the CSV has invalid fields or formatting, an error is shown — fix and re-upload.
6. Click **Save**. 

{% hint style="info" %}
After uploading, redeploy any pipelines that will use the new routes. Pipelines in test mode redeploy automatically, which may cause temporary instability.
{% endhint %}

### **Inverse Flow**

An Inverse Flow route lets you call internal Digibee pipelines from your own infrastructure through ZTNA, reversing the usual direction of a Network Mapping.

1. Click **Add Network Mapping** and select **Inverse Flow Form**.
2. Fill in the fields:
   * **Protocol**: HTTP, HTTPS, or HL7.
   * **Port**
   * **Host**
   * **Environment**: Test or Prod.
3. Click **Save**. After you create the route, the Platform automatically creates and configures the corresponding Edge Router on the Digibee side, assigned to a dedicated **Inverse** group that you can't edit.

## **Filtering and searching routes**

Once the routes are created, you can view them all in a table. To quickly find a route, you can use the search bar and look for host, destination, or name. 

You can also filter by:

* Environment
* Edge Router Group
* Network Mapping Type (Standard or Inverse Flow) 

## **Editing routes**

1. To edit a route, click the **pencil** icon in the **Actions** column.
2. A sidesheet opens with the current route information (Port, Host, Environment, Group — plus Host alias if applicable).
3. Make the necessary changes.
4. Click **Save**, or **Cancel** to discard changes.

## **Deleting routes**

{% hint style="info" %}
Only users with the [connectivity-manager](/documentation/platform-administration/administration/new-access-control/access-control-roles.md#connectivity-manager) role can delete routes.
{% endhint %}

1. To delete a route, click the **trash** icon in the **Actions** column.
2. Confirm the action in the dialog that opens.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/connectivity-management/ztna/network-mapping-routes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.