> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/system-administration/settings-overview.md).

# System Settings

Overview of VergeOS system settings, including general configuration, version information, license details, location settings, connection details, and how to modify settings.

The *System Settings* page provides access to various configuration options for your VergeOS environment. This guide will walk you through the different sections and their functionalities.

## Accessing System Settings

From the top menu, navigate to **System** > **Settings**.

## General Settings

The *General* section displays basic information about your VergeOS system:

* **Cloud Name**: The name of your VergeOS system.
* **Description**: A brief description of the system (if provided).
* **ID**: A unique identifier for your VergeOS system instance.
* **Tenant**: Indicates whether this is a tenant environment.

### Advanced Settings

Click the **Advanced Settings** link to access additional configuration options.

## Version Information

This section provides details about the software version:

* **Software Version**: The current version of VergeOS software.
* **OS Version**: The underlying operating system version.
* **Branch**: The software branch (e.g., develop, stable).

## License Details

The License section displays information about your VergeOS license:

* **Name**: The name of the license.
* **Description**: Any additional description provided for the license.
* **Valid From/Until**: The validity period of the license.
* **Issued On/Added On**: Dates related to license issuance and addition.
* **Auto-Renewal**: Shows if the license is set to auto-renew.

To view or copy the license key, click the **Copy** button next to the "Key" field.

## Location Information

This section shows the geographical details of your VergeOS instance:

* **Domain**: The domain associated with your instance.
* **City/Country**: The physical location of the server.
* **Timezone**: The configured timezone.
* **Latitude/Longitude**: Precise geographical coordinates.

A map is displayed to visually represent the location.

## Connection Details

The Connection section provides network information:

* **vSAN Host**: The IP address or hostname of the vSAN.
* **vSAN Port**: The port number used for vSAN communication.

## Modifying System Settings

To change system-wide settings:

1. Click **Edit** on the left menu under the Settings section.
2. Update the necessary fields in the system and Location sections.
3. Click **Submit** to save your changes.

## Requesting or Modifying Licenses

* To generate an offline (air-gap) license request, click **Request Offline License** on the left menu. See [Requesting an Airgap License for VergeOS](/knowledge-base/system-administration/requesting-an-airgap-license.md) for the full procedure.
* To install a license, click **Add License** on the left menu. If a license is already installed, the menu shows **Edit License** instead — click it to replace the installed key.
* To remove a license, use the **Delete License** option.

Remember to review any changes carefully before submitting, as these settings can impact your entire VergeOS environment.


---

# 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.verge.io/run-the-platform/system-administration/settings-overview.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.