> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/network-diagram-beta.md).

# Network Diagram (Beta)

### **Network Diagram** <a href="#toc174553268" id="toc174553268"></a>

A network diagram is a pictorial representation of a network. It shows the various components that make up a network and how these components interact with each other. A network diagram typically consists of routers, devices, hubs, firewalls, etc.&#x20;

The Network Diagram module of Infraon is a diagram creator tool like MS Visio. It has drag-and-drop icons that can depict the complete network and assets. The module provides multiple options for mapping devices and components to specific icons.

The user will be able to access, add, edit, clone, and delete the Network Diagrams only if the administrator has granted them those privileges. The privileges will be defined under Roles and Privileges.


---

# 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.infraon.io/infinity/user-guide/network-diagram-beta.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.