> For the complete documentation index, see [llms.txt](https://nso-docs.cisco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nso-docs.cisco.com/guides/nso-6.1/operation-and-usage/webui.md).

# Web UI

Operate NSO using the Web UI.

The NSO Web UI consists of a suite of web-based applications. Each application has its own distinct concern, for instance, handling configuration, transaction handling, managing devices, managing services, or monitoring the system. The different applications can be accessed from the application hub, which is shown directly after authentication.

The Web UI is a mix of custom-built applications and auto-rendering from the underlying device and service models. The latter gives the benefit that a Web UI is immediately updated when new devices or services are added to the system. So, say you add support for a new device vendor. Without any programming, is the NSO Web UI capable of configuring those devices?

All modern web browsers are supported and no plug-ins are required. The interface is a pure JavaScript Client.

## Using the Web UI <a href="#d5e5509" id="d5e5509"></a>

The Web UI is available on port 8080 on the NSO server. The port can be changed in the `ncs.conf` file. An NSO user must exist.

More help on how to use the Web UI is present in the Web UI applications. The help is located in the user menu, which can be found to the right in the application header.

## Transactions and Commit <a href="#d5e5514" id="d5e5514"></a>

Take special notice to the Commit Manager application, whenever a transaction has started, the active changes can be inspected and evaluated before they are committed and pushed to the network. The data is saved to the NSO datastore and pushed to the network when a user presses "Commit".

Any network-wide change can be picked up as a rollback file. That rollback can then be applied to undo whatever happened to the network.


---

# 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://nso-docs.cisco.com/guides/nso-6.1/operation-and-usage/webui.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.
