# General Settings

The **General Settings** tab in Platform Settings provides administrators with control over fundamental system-wide defaults that impact how Nexus operates. These settings define limits on data streaming and deployment behavior across the platform.

Access to General Settings is restricted to users with the [Administrator Role](/platform-architecture/security-architecture/user-roles-and-permissions.md), ensuring that only authorized users can configure global parameters.

***

## Key Configurations

<figure><img src="/files/wNfalJEIOsWcPm8cKhOT" alt=""><figcaption><p>General Configuration of Platform Settings</p></figcaption></figure>

### Maximum Number of Real-Time Measurement Streams

This setting defines the **maximum number of concurrent real-time data streams** that can be sent to the **Time Series Explorer**.

* By default, this value is set to **3**.
* Increasing this limit allows more measurement streams to be visualized simultaneously but may increase system resource usage.
* Lowering the number can help optimize performance for smaller-scale environments.

### Default Deployment Method

This setting controls how asset hierarchies, modules and applications are deployed to devices by default. Nexus supports two deployment strategies:

**Direct Deployment (Default)**

* Nexus communicates directly with the **IoT Hub endpoint** to perform deployments.
* The full device configuration is sent **as a single, complete manifest** directly to the device. The deployment is applied immediately, but there are no subsequent checks for configuration drift (if the deployment is altered).
* This is the **fastest deployment method**, as there is no intermediate orchestration layer.
* Best suited for **installations with fewer than 100 devices**, where speed and simplicity are prioritized.

**Managed Deployment**

* Nexus creates a **deployment manifest** and uses **iothub automatic deployments** that are sent to the IoT Hub endpoint.
* Deployments are sent to the device as one or more layered configurations. This means that the deployment is set as a desired state, and the Management Endpoint (Iot Hub) will continuously **ensure** that the **desired configuration remains intact**.
* The IoT Hub is responsible for performing the deployment, but it may not occur immediatly.
* This approach is **slower than Direct Deployment**, but it provides **better scalability**.
* Recommended for **installations with more than 100 devices**, or where centralized management and rules enforcement are critical.
* You can read more about [Automatic deployments in Microsofts documentation](https://learn.microsoft.com/en-us/azure/iot-edge/module-deployment-monitoring).

Users can still override the deployment method of each device in the [settings of the device configuration](/management-portal/management/device-configuration/settings.md).

***

### When to Adjust Settings

* **Increase Real-Time Streams** if users need to monitor multiple measurement channels simultaneously in Time Series Explorer.
* **Switch the default Deployment method** for environments that has grown to hundreds of devices and where reliability, auditing, and orchestration of updates are more critical than speed.


---

# Agent Instructions: 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:

```
GET https://docs.tricloudnexus.io/management-portal/platform-settings/general-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.