--- title: "Differences in Configure for On-Premises" slug: "onpremises-configure-differences-from-cloud" description: "What works differently in Configure when you run SysTrack On-Premises, with a link to the main article for each topic." updated: 2026-10-16T14:21:01Z published: 2026-10-16T14:21:01Z canonical: "documentation.lakesidesoftware.com/onpremises-configure-differences-from-cloud" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt > Use this file to discover all available pages before exploring further. # Differences in Configure for On-Premises Configure in SysTrack On-Premises provides a single web-based interface for managing the SysTrack Agent including Roles, Profiles, Configurations, Tools Access Security, Privilege Sets, and Groups. Push or Pull SysTrack Agent deployment is done through the client-based SysTrack Deploy. For SysTrack On-Premises, review the differences for your topic below before following the linked Configure article. Each section describes the on-premises differences and links to the main article for that topic. ## Webhooks for Sensor Notifications In SysTrack On-Premises, when you select the **Webhook** connection, SysTrack shows the message "Webhooks to external services require that the master server is connected to the internet." The webhook setup in SysTrack On-Premises has no **Notification Type** row. Cloud has one. The cloud article [Webhook Support for Sensor Notifications](/documentation/docs/sensor-notifications-webhook-support-for-sensor-notifications) describes how to set up webhooks for sensor notifications. ## Sensor Notification Recipients In SysTrack On-Premises, a **User** recipient is not a SysTrack user, and SysTrack does not send an invitation when you add one. You can edit the name and email of **User** recipients. In cloud, you cannot. The cloud article [Sensor Notification Recipients](/documentation/docs/sensor-notification-recipients) describes how to manage recipients of sensor notifications. For the **Recipients** field in a notification, see [Configure Sensor Notifications](/documentation/docs/configure-sensor-notifications). ## Operations in Administration The **Command Dashboard** in SysTrack On-Premises also has two commands that are not in cloud: **Recondense All** and **Refresh Visualizers**. The layout is the same in SysTrack On-Premises. The cloud article [Operations: Command Dashboard](/documentation/docs/operations-command-dashboard) describes **Operations** in **Configure** > **SysTrack Settings** > **Administration**. - **Recondense All**: All child systems run a full condense and resend their data to the master the next time they read their configuration. This can take a while, so SysTrack asks you to confirm. - **Refresh Visualizers**: Refreshes the Visualizer data on the master right away, instead of at the next scheduled update. While it runs, the **Command Dashboard** shows (Running Refresh). You do not select systems for these two commands. They run on the master system that Configure is connected to. Each run is listed in **Command Report**. ## Settings in Administration In SysTrack On-Premises, **Settings** also has **Host name** and **Use FQDN for systems added to the tree**. **Auto Remove Non-Connecting Systems**, with **Remove after** *n* **days**, appears in SysTrack On-Premises only on the Global Master. The cloud article [Settings](/documentation/docs/settings) describes **Settings** in **Configure** > **SysTrack Settings** > **Administration**. - **Host name**: The name of the master system. When SysTrack deploys the agent from this master, it sets up the agent to connect to the master by this name. - **Use FQDN for systems added to the tree**: Selected by default. SysTrack adds systems to the tree by their fully qualified domain name (FQDN), such as pc01.example.com. If you clear the check box, SysTrack adds systems by their short name, such as pc01. ## Delete User Data (Privacy) In SysTrack On-Premises, the **Privacy** section in **Configure** > **SysTrack Settings** > **Administration** appears only on the Global Master. The cloud article [Delete User Data for GDPR Requests](/documentation/docs/privacy) describes how to remove data for a specific user. After you redact user data, the changes become visible within the next data cycle. To refresh master systems right away in SysTrack On-Premises: 1. Go to **Configure** > **SysTrack Settings** > **Administration** > **Operations**. 2. Under **Command Dashboard**, select **Refresh Visualizers** and click **Run**. 3. In SysTrack Deploy, right-click each master system in the tree and select **Run Bulk Uplink Now**. This command is available only when the master is uplinked in Bulk transfer mode. ## Unit Settings and Productivity Impact Cost In SysTrack On-Premises, you can change **Productivity Impact Cost** and the **Currency** in **Unit Settings** only on the Global Master. You can change the other **Unit Settings** on a regional master too. The cloud articles [Unit Settings](/documentation/docs/unit-settings) and [Productivity Impact Cost](/documentation/docs/productivity-impact-cost) describe these settings. ## Roles Page Tabs In SysTrack On-Premises, the **Roles** page also has a **Policies** tab. The cloud article [Roles Overview](/documentation/docs/roles-overview) describes the **Roles** page in **Configure** > **System Configuration** > **Roles**. See [Configure Policies](/documentation/docs/configure-policies). ## Surveys In SysTrack On-Premises, the **Surveys** menu is only available on the Global Master. The cloud articles under the [Surveys](/documentation/docs/tools-surveys) category describe how to create surveys.