---
title: "Advanced Settings"
slug: "environment-advanced-settings"
updated: 2026-07-30T09:44:36Z
published: 2026-07-30T09:44:36Z
canonical: "learn.servitly.com/environment-advanced-settings"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.servitly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Advanced Settings

On this page, you can view and manage environment settings. The page is organized into sections, each one covering a specific aspect.

> [!WARNING]
> Settings with **Read-only** access are pre-configured according to the [environment type](/v1/docs/console-main-concepts#environment-types) or as defined in the commercial offer. Ask your Customer Success Manager or write to [support@servitly.com](https://support@servitly.com/) if you need to change these settings.

## DPS Limits

In this section, you can find the environment limits, including the maximum number of objects you can create in the DPS for each type and the limits for IoT data publishing and REST API invocations.

| Setting | Description |
| --- | --- |
| *Max Publish Count* | The maximum number of raw metric values that can be pushed every hour by a single thing. **Access**: Read-only **Default Value**: refer to the [Console Main Concepts](/v1/docs/console-main-concepts#environment-limits) article. |
| *Max API Key Request Count* | The maximum number of API requests allowed every minute for the entire tenant. **Access**: Read-only **Default Value**: refer to the [Console Main Concepts](/v1/docs/console-main-concepts#environment-limits) article. |
| *Max Thing Count* | The maximum number of things that can be created in the DPS. **Access**: Read-only **Default Value**: refer to the [Console Main Concepts](/v1/docs/console-main-concepts#environment-limits) article. |
| *Max Customer Count* | The maximum number of customers that can be created in the DPS. **Access**: Read-only **Default Value**: refer to the [Console Main Concepts](/v1/docs/console-main-concepts#environment-limits) article. |
| *Max Partner Count* | The maximum number of partners that can be created in the DPS. **Access**: Read-only **Default Value**: refer to the [Console Main Concepts](/v1/docs/console-main-concepts#environment-limits) article. |
| *Max Organization Count* | The maximum number of organizations that can be created in the DPS. **Access**: Read-only **Default Value**: refer to the [Console Main Concepts](/v1/docs/console-main-concepts#environment-limits) article. |
| *Max User Count* | The maximum number of users that can be created in the DPS. **Access**: Read-only **Default Value**: refer to the [Console Main Concepts](/v1/docs/console-main-concepts#environment-limits) article. |
| *Max Historical Alerts Age* | The maximum number of days historical alerts remain visible to the user. **Access**: Read-only **Default Value**: 30 days |

## Configuration

| Setting | Description |
| --- | --- |
| *Max Variables per Computed Metric* | The maximum number of variables you can use in a computed metric. **Access**: Read-only **Default Value**: 3 |
| *Max Virtual Thing Count* | The maximum number of virtual things that can run in parallel. **Access**: Read-only **Default Value**: 10 |
| *Max Events With Continuous Computation* | The maximum number of events with continuous computation that can be defined across all thing definitions. **Access**: Read-only **Default Value**: 50 |

## Data

In the *Data* section, you can have an overview of the settings related to data management.

| Setting | Description |
| --- | --- |
| *Raw Data Retention* | The maximum number of months after which raw metrics data is deleted. **Access**: Read-only **Default Value**: refer to the [Data Retention](/v1/docs/data-retention) article. |
| *Out-of-retention data deletion reminder enabled* | If selected, customers are notified in advance before data deletion becomes effective. **Access**: Read/Write **Default Value**: No |
| *Work Sessions Retention* | The maximum number of months after which historical work sessions are deleted. **Access**: Read-only **Default Value**: refer to the [Data Retention](/v1/docs/data-retention) article. |
| *Other Events Retention* | The maximum number of months after which historical events (Failures, Anomalies, Operations) are deleted. **Access**: Read-only **Default Value**: refer to the [Data Retention](/v1/docs/data-retention) article. |
| *Max Length of String Property Value* | The maximum number of characters that can be stored in a STRING metric value. **Access**: Read-only **Default Value**: 512 characters |
| *Max Size of BLOB Metric* | The maximum number of bytes that can be stored in a BLOB metric value. **Access**: Read-only **Default Value**: 10240 bytes |

## Periodic Computations

To manage the high input data flow generated by connected products and processes, Servitly uses a distributed pipeline of periodic evaluations to process such data streams without losing any data points. Periodic evaluation refers to the execution of tasks or computations at regular intervals to process data to create new data points (e.g., Computed Metrics, Insights), detect events (e.g., Failures, Anomalies, Work Sessions), or perform automations.

| Setting | Description |
| --- | --- |
| *Property Evaluation Interval* | The time interval in milliseconds between each periodic property with data binding evaluation. **Access**: Read-only **Default Value**: 90 seconds (metrics), 10 minutes (statistics), 1 day (insights) **Evaluation Policy**: `SAMPLED` |
| *Connectivity Evaluation Interval* | The time interval in milliseconds between each periodic connection status evaluation. **Access**: Read-only **Default Value**: 30 seconds **Evaluation Policy**: `SAMPLED` |
| *Computed Data Evaluation Interval* | The time interval in milliseconds between each periodic computed data evaluation. On each computed metric, you can define the evaluation policy. **Access**: Read-only **Default Value**: 60 seconds **Evaluation Policy**: `SAMPLED` , `CONTINUOUS` |
| *Insights Evaluation Interval* | The time interval in milliseconds between each periodic insight evaluation. **Access**: Read-only **Default Value**: 1 day **Evaluation Policy**: `SAMPLED` |
| *Sampled Events Evaluation Interval* | The time interval in milliseconds between each periodic evaluation of events. **Access**: Read-only **Default Value**: 60 seconds **Evaluation Policy**: `SAMPLED` |
| *Continuous Events Evaluation Interval* | The time interval in milliseconds between each periodic evaluation of events. **Access**: Read-only **Default Value**: 60 seconds **Evaluation Policy**: `CONTINUOUS` |
| *Work Session Evaluation Interval* | The time interval in milliseconds between each periodic work session evaluation. In addition, the `Work Session Evaluation Delay` defines the offset relative to the evaluation instant (default 60 seconds). This allows the system to handle start/stop conditions and monitored metrics by processing data received between T0 and T1. - T0: NOW - Work_Session_Evaluation_Interval - Work Session_Evaluation_Delay - T1: NOW - Work Session_Evaluation_Delay **Access**: Read-only **Default Value**: 60 seconds **Evaluation Policy**: `CONTINUOUS` |
| *Automation Evaluation Interval* | The time interval in milliseconds between each periodic automation evaluation. **Access**: Read-only **Default Value**: 60 seconds **Evaluation Policy**: `SAMPLED` |

Each periodic evaluation may support different evaluation policies:

- `CONTINUOUS`: Periodically, all the data points since the last evaluation are considered in the computation.
- `SAMPLED`: Periodically, only the last data point received since the last evaluation is considered in the computation.

Insights are calculated daily at a fixed time (taking into account the time zone), and although they require all data points in the evaluation period, no [DPH](/docs/dph-computation) is charged for the computation, so they are considered as `SAMPLED`. Note that the `CONTINUOUS` evaluation affects the number of [DPH](/docs/dph-computation) consumed.

## Remote Control

Here you can change options related to the product's remote control:

| Setting | Description |
| --- | --- |
| *Omit timestamp in control payloads* | If selected, any payload related to command execution or parameter update will not include the timestamp. This reduces the size of the message. **Access**: Read/Write **Default Value**: No |
| *Max Parameter Count per Message* | In case you are sending multiple parameters into the same message related to command execution or parameter update, here you can specify the maximum number of parameters before splitting the payload into multiple messages sent separately. **Access**: Read/Write **Default Value**: unlimited |

## Audit

Here, you can configure the application log, which contains any operation performed by the users in the DPS.

| Setting | Description |
| --- | --- |
| *Enable audit of user actions in the DPS* | If selected, any action performed by the users in the DPS is logged in an audit log. **Access**: Read/Write **Default Value**: Yes |
| *Enable user navigation event logging* | If selected, each time a user changes page in the DPS, a new log is registered. **Access**: Read-only **Default Value**: No |
| *Audit Retention* | The maximum number of days after which audit logs are deleted. **Access**: Read-only **Default Value**: 90 days |

In this section, you can also export audit logs through a CSV file by selecting a period of interest.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(773).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A35%3A56Z&se=2026-10-16T18%3A35%3A56Z&sr=c&sp=r&sig=L7T%2FWewlwzKN2TT2KalExB9H9EwSK%2B2Mca3nXLD7UY8%3D)

## UI Options

Here you can find options related to the DPS UI.

| Setting | Description |
| --- | --- |
| *Enable language selector on pages in the DPS* | If selected, in the DPS, users will find the language selector aside the user menu. **Access**: Read/Write **Default Value**: No |
| *Enable timezone button on pages in the DPS* | If selected, in the DPS, the [Timezone Button](/v1/docs/dps-timezone-management) appears when the user enters a context with a different time zone. **Access**: Read/Write **Default Value**: Yes |
| *Enable feedback link on page* | If selected in the DPS, at the bottom of each page, there is a link allowing DPS users to report feedback. Feedback is sent via email to the `Feedback Recipients`. **Access**: Read/Write **Default Value**: No |
| *List Range selection mode* | Allows changing the style of the page scroller present under the list-based widgets in the DPS. **Access**: Read/write **Values**: `ITEMS`, `PAGES` **Default Value**: `ITEMS` |
| *Enable Null Value* | When selected, in case a metric value is null, `N/A` is printed out. Optionally, you can redefine the `Default Null Value` to be displayed. **Access**: Read/Write **Default Value**: No |
| *Limit the visibility of customer data by ownership* | When selected, customers can access historical data of their things with a limit corresponding to the last activation timestamp. In this way, in case the thing changes the owner, the previous owner’s data is not accessible; instead, organization and partner users can always access all the data, discarding the current owner. **Access**: Read/Write **Default Value**: No |
| *Default Periods* | Allows specifying the default periods that users can select in the DPS to filter data, unless the list of selectable periods has been redefined directly in the template. These are the selectable periods: - *Today, Yesterday* - *Last 1 Hour, Last 2 Hours, Last 6 Hours, Last 12 Hours, Last 24 Hours* - *Last 7 Days, Last 30 Days* - *This Month, Last Month, Last 6 Months, Last 12 Months* - *This Week, Last Week* - *Last Full 7 Days, Last Full 30 Days* - *Last Full 3 Months, Last Full 6 Months, Last Full 12 Months* - *Last Year, This Year* - *This Quarter, Last Quarter, This Semester, Last Semester* - *Custom* Periods marked as “Full” begin and end at midnight, while other periods also include daylight hours, minutes, and seconds. |

## Notifications

Here is configured the email address used by the DPS to send any email notification, including:

- account management notifications (e.g., creation, password reset).
- alerts notification (e.g., failure event activation)
- subscription and payment notifications
- PDF periodic reports

> [!WARNING]
> Alternative email address
> 
> You cannot change your e-mail address by yourself, but we ask that you let us know by writing to [support@servitly.com](mailto:support@servitly.com). We will be happy to help you with the configuration by providing DNS records to add to your domain's DNS settings. This is mandatory for security and anti-spam reasons. For more details about what we have to do to use your email address, you can refer to this [AWS article](https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html#just-verify-domain-proc).

## Things

Here you can change settings related to how things are managed in the DPS.

| Setting | Description |
| --- | --- |
| *Make the token required during the activation of the thing* | If selected, in DPS, other than the *Serial Number,* the user must also provide the *Activation Token* when a thing is activated. **Access**: Read/Write **Default Value**: No |
| *Force one tag per thing* | If selected, in the DPS, when using the tagging features, it is possible to add at most one tag per thing. **Access**: Read/Write **Default Value**: No |
| *Enable automatic deactivation of long-time offline things* | Fleets accumulate products/machines that stop communicating because they are decommissioned, put in storage, or replaced but never removed from the DPS. Left as they are, these things keep occupying the fleet views, distort KPIs and fleet-level aggregations, and keep being counted in the monthly billing even though they no longer send any data. To avoid this, the DPS can deactivate them for you. When a thing does not send any data for longer than a configured period of time (e.g., 6 months), its *Cloud Status* is automatically set to `INACTIVE`. From that moment on: - Incoming IoT data is discarded. - Events and other periodic computations are stopped. - The thing is no longer counted in the billing. As with any other status change, the transition is recorded in the Cloud Status metric, and the `cloudStatus` and `cloudStatusLastUpdateTimestamp` properties of the thing are updated accordingly. The history collected before the deactivation is preserved, so the thing can still be inspected, and reactivating it later restores normal data processing. Keep in mind, however, that historical data remains subject to the configured data retention period. Data older than the retention window is purged as usual. If you need to preserve that information beyond the retention period, export it before it is purged. **Access**: Read/write **Default Value**: No |
| *Things Inventory Management* | You can define how the Things in the DPS are associated with Thing Definitions or Product Models. The default is `By Product Model`, but to allow old projects to be migrated from `By Thing Definition`, you can select the intermediate phase `By Thing Definition And Model`. For more details, refer to the [Migrating to Product Models](/v1/docs/migrating-to-product-models) article. **Access**: Read/write **Default Value**: `By Product Model` |