System | SBC Online Help

Purpose and Overview

The System Settings page lets the System Administrator define parameters to customise the SBC instance.

The settings are organised into tabs, each covering a specific aspect.

General

This view provides some general settings to customise SBC, especially the language and the behaviour at the login page. Supported parameters are namely:

Parameter	Description
Agency	The agency name appears in SBC notifications and when exporting the dashboard to PDF. It should be the official name of the GNSS Reference Station network or the operating organisation. Default: Leica Geosystems AG
Default language	The SBC public page uses the browser's default language. If SBC does not support this language, it will search for the next supported language configured in the browser. If no supported language is found, SBC will use the default language set here. If a user manually selects another language on the SBC public page, SBC will remember this preference and use it on the next visit. This language applies to all public pages, including those without authentication, and to email notifications.
Support email	The recipient of any contact emails sent by end users through the Contact form in the User Portal. If it is not defined, the messages will not be delivered.
Forward incoming emails	Email addresses to which notifications must be forwarded. Addresses can be separated by pressing "Enter". Default: empty, i.e., no forwarding If this field is filled, additional recipients for the contact emails can be listed in the corresponding box. Any email address can be selected, e.g., support@somebody-else.com. If the “Support email” field is empty. Nothing will be forwarded.
Audit log retention	Maximum age of the Audit Log entries. The audit log retention is used to delete the logged entries older than the configured value. This affects also the dashboard charts. Default: 9 months
Enable site overview map on login page	Enable or disable the site overview on the login page. Default: enabled
Enable user sign up	Enable or disable self-registration of new users from the login page. When this setting is enabled, the option “Don't have an account? Create one” will be shown on the login dialogue. When disabled, only privileged administrative roles can create users. Default: enabled
Enable end user login	Enables the SBC User Portal. When this setting is enabled, users with the role “End User” are allowed to log in to the web portal. Otherwise, only administrative roles can log in. Default: enabled
Enable shop on login page	Enable or disable the subscription shop on the login page. Default: enabled
Enable automatic subscription activation	Automatically sets subscriptions to "active" when the subscription wizard in the shop is completed. When disabled, the subscription remains in “pending” mode after completing the subscription wizard in the shop. An administrator must then activate it explicitly. Default: disabled
Enable end user subscription renewal	Allows end users to renew subscriptions after expiry without interaction from an Administrator. When this setting is enabled, end users can renew their own expired subscriptions, without any need for the service operator to do so. This can be done via the User portal, through Account Details > Subscriptions.

Notifications

SMTP Server

This section contains all settings required to configure an outgoing email server used for Notifications. For outgoing email the SMTP protocol is used. Therefore it is called SMTP server.

The SMTP server is not part of the Leica Spider suite. An external solution has to be utilised and correctly configured.

Typically, your organisation will already have a SMTP server via which your business emails are sent. Check with your IT administrator if you can utilise this one. Alternatively, you can install a dedicated SMTP server application or use commercial SMTP services. The SMTP Server of Microsoft Windows Server operating systems has been phased out and removed with Windows Server 2025. Note that SBC supports only username-password authentication, which the SMTP server must also support.

Parameter	Description
Outgoing email server	The hostname, IP address or DNS name of the outgoing email server (SMTP).
SMTP Port	The port number on which the selected SMTP server is operating. The standard port number for SMTP is 25. The standard port numbers for SMTPS, i.e., with the option “Enable SSL/TLS” is used, are 587 or 465. Note that the SMTP server might not use the standard port. The setting here must match the server’s configuration.
Email address of sender	Email address of the sender (SBC) for all the system emails sent by SBC. These system emails are, e.g., notifications about subscription expiration, forgotten password requests, etc.
SMTP server authentication (optional)	For many SMTP servers an authentication is required to send emails via this server. Enter the necessary credentials here: User name: User name for authenticating on the SMTP server. Password. Password for authenticating this user on the SMTP server. Only authentication with user name and password is supported. SMTP server authentication via OAuth or other means is not supported. Please select a SMTP server that supports this method or configure it accordingly.
Enable SSL/TLS	Enable or disable secure communication using SSL/TLS. This setting depends on the SMTP server configuration. Consider adapting the SMTP Port to the standard SMTPS port 587 or 465.

Use the “Send test Email” button to verify the configuration. The email will be sent to the address set for the user who initiates the test, in the language configured in their profile.

Notification Behaviour

Parameter	Description
Enable auto-generated emails	Emails related to subscriptions will be sent automatically to end users. These emails include notifications about requested or expiring subscriptions and from post-processing service requests. Default: enabled
Enable Contact form on User Portal	Allow end users to contact SBC administrators using the Contact form in the user portal. Default: disabled
Enable redirect of contact email requests	All end user contact requests will be redirected to their corresponding Sales Organisations. When enabling this settings, user contact requests will not be received by the global support email (typically a System Root organisation inbox) but redirected to the support email address of the organisation where the advice-seeking user belongs to. See Organisations and Notifications Default: disabled

Parameter

Description

Enable auto-generated emails

Emails related to subscriptions will be sent automatically to end users.

These emails include notifications about requested or expiring subscriptions and from post-processing service requests.

Default: enabled

Enable Contact form on User Portal

Allow end users to contact SBC administrators using the Contact form in the user portal.

Default: disabled

Enable redirect of contact email requests

All end user contact requests will be redirected to their corresponding Sales Organisations.

When enabling this settings, user contact requests will not be received by the global support email (typically a System Root organisation inbox) but redirected to the support email address of the organisation where the advice-seeking user belongs to.

See Organisations and Notifications

Default: disabled

Check the Notifications section to learn more about this feature in general.

Infrastructure

This page contains settings related to the service infrastructure of SBC.

Services provided by SBC

Parameter	Description
Frontend URL	The frontend URL under which external users can access your SBC instance. External applications or workflows accessing SBC require the frontend URL of the SBC login page. GNSS Spider and Leica X-pos Integration use this URL. The automatic user registration process also depends on this setting. Example: http://hostname.domain.com/SBC/ Alternatively, you can use the public IP address, but it is not recommended. In case SSL/TLS is set up, preferably by using the Spider Suite SSL Configurator Tool, it is important to consider the domain for which the SSL certificate is valid, e.g., https://SBC.company.com/SBC/
Enable Mobile Device API	Enables smartphone App to access SBC mobile content. Configure this content through SBC 'Mobile Pages' menu Default: disabled This is a SmartNet only feature.

Parameter

Description

Frontend URL

The frontend URL under which external users can access your SBC instance.

External applications or workflows accessing SBC require the frontend URL of the SBC login page. GNSS Spider and Leica X-pos Integration use this URL. The automatic user registration process also depends on this setting.

Example: http://hostname.domain.com/SBC/

Alternatively, you can use the public IP address, but it is not recommended.

In case SSL/TLS is set up, preferably by using the Spider Suite SSL Configurator Tool, it is important to consider the domain for which the SSL certificate is valid, e.g., https://SBC.company.com/SBC/

Enable Mobile Device API

Enables smartphone App to access SBC mobile content. Configure this content through SBC 'Mobile Pages' menu

Default: disabled

This is a SmartNet only feature.

The “Check Connectivity” button lets you test if the configured values are plausible and a connection can be established.

Public Ntrip Caster access

The Public Ntrip Caster settings define the default caster connection details for the GNSS network service. These settings initialize the user's preferred Ntrip Caster details, displayed to guide correct entry on their rover device. Changing them updates the user's preferred values unless altered at the user level.

Parameter	Description
Ntrip Caster host name	Used to access a real-time data stream via Ntrip; can be overwritten by users in their personal profile Default: localhost The default value should be modified to match the public hostname, IP address or DNS name of the server hosting the Ntrip Caster. With Leica GNSS Spider the RTK Proxy Server component is providing the Ntrip Caster.
Ntrip Caster port	Used as standard Ntrip caster port; can be overwritten by users in their personal profile Default: 2101

Parameter

Description

Ntrip Caster host name

Used to access a real-time data stream via Ntrip; can be overwritten by users in their personal profile

Default: localhost

The default value should be modified to match the public hostname, IP address or DNS name of the server hosting the Ntrip Caster.

With Leica GNSS Spider the RTK Proxy Server component is providing the Ntrip Caster.

Ntrip Caster port

Used as standard Ntrip caster port; can be overwritten by users in their personal profile

Default: 2101

The “Check Connectivity” button lets you test if the configured values are plausible and a connection can be established.

Services where SBC connects to

Parameter	Description
Private hostname of X-pos Server	For connection to X-pos Server, user authentication on X-pos side, synchronization of settings and relevant data
Public hostname of X-pos Server	For public access to X-pos data and to the RINEX repository
Hostname of Spider Logging Server - Enables Reporting	The hostname of the machine where the Spider Logging Server is installed for reporting rover connection related information. Only required and supported in Hexagon SmartNet.

Parameter

Description

Private hostname of X-pos Server

For connection to X-pos Server, user authentication on X-pos side, synchronization of settings and relevant data

Public hostname of X-pos Server

For public access to X-pos data and to the RINEX repository

Hostname of Spider Logging Server - Enables Reporting

The hostname of the machine where the Spider Logging Server is installed for reporting rover connection related information.

Only required and supported in Hexagon SmartNet.

The hostname of the X-pos Server is required to be configured in case an X-pos Server is part of the Spider Suite installation. The correct hostname or IP address of the server where the X-pos service is running is expected. The TCP/IP port number is predefined to be 80 for http and 443 for https and cannot be changed. Setting the X-pos hostname is a prerequisite to receive the latest site properties from Spider Site server as well as to enable access to the X-pos file repository. Similar to the frontend URL, it is important to grant Internet access to the domain or IP address that is entered as the hostname. This includes the firewall settings for the TCP port mentioned above. The browser will directly contact the X-pos Server when visiting X-pos related pages within SBC. If the X-pos Server is operated on the same machine as the SBC Proxy Server it is recommended to set the hostname to the domain where the SBC website is accessible from the public. If the X-pos Server and the SBC Proxy Server are installed on different machines, then it is recommended to use the external IP address or URL of the machine where the X-pos Server is installed, as this must be universally recognizable.

After changing the X-pos Server (physical or name changes, such as "localhost" to "IP address"), clear all browsers' cache before continuing; otherwise, data downloads will fail.

In case SBC (proxy server) is configured to SSL/TLS, the corresponding security level is also required to be set up for the X-pos API. Mixed content of insecure HTTP X-pos resources and a secure HTTPS SBC page is not supported. Data exchange is impossible. If the X-pos Server is operated on the same machine as the SBC Proxy Server, no additional steps for configuring X-pos to support SSL are required.

Example: xpos.company.com

The certificate installed on xpos.company.com must be valid for this domain.

Find further details in paragraph “Making SBC and X-pos SSL-ready”.

Documents

Supports the separate upload of Privacy Notice and Terms of Use documents. Both documents are stored in database. Only supported format is PDF. The localization depends on the content of uploaded files. Once a file has been uploaded the file name shown in text box.

The Privacy Notice and Terms of Use document can be deleted with the effect that no document will be shown during user registration or subscription order process.

Document	Purpose
Privacy Notice	The document is displayed by clicking on the link Privacy Notice at the user sign up form.
Terms of Use	The document is displayed as one page of the subscription order wizard which is part of the shop.

UI Configuration

Thresholds

This section provides possibility to define limits of various indicators across the SBC user interface.

Ambiguity fixing status of reference sites

This option allows to define thresholds which affect the colour change of reference sites fixing status icon in the status bar. It allows to define limits for the transition between the 3 supported states.

States	Min Value	Max Value
Critical (Red)	0%	Configurable. Default: 10%
OK (Green)	Configurable. Default: 90%	100%
Warning (Yellow)	automatically calculated from above values	automatically calculated from above values

Corporate Design

This section gives the possibility to customise the design of the SBC web portal user interface (UI), by allowing the creation of one Customized theme in addition to the Default one. The theme defined here will be visible to all users of the system, except a Corporate Design has been defined for a Sales Organisation.

After selecting Theme to be “Customized”, you can select the following:

Parameter	Description
Primary logo (light mode)	Main corporate logo, used on wide screen windows (in light mode) at the top left area of the UI.
Primary logo (dark mode)	Main corporate logo, used on wide screen windows (in dark mode) at the top left area of the UI.
Submark logo (light mode)	Simplified version of the corporate logo - ideally square, used on narrow screen windows (in light mode) at the top left area of the UI.
Submark logo (dark mode)	Simplified version of the corporate logo - ideally square, used on narrow screen windows (in dark mode) at the top left area of the UI.
Favicon	Simple symbol of the corporate brand, used in browser to identify the tab.

Recommendations:

use a primary logo with maximum aspect ratio of 8:1 (e.g. 240x30 pixel, or 480x60 pixel)
use a submark logo with aspect ratio of 1:1 (square)

Maps

Purpose

This page section allows to configure the background map for all map views. It provides following configurations:

Background Map – contains customized settings for map servers
Support Satellite Imagery – allows to activate the satellite imagery layer based on the user rights

Background Map

The dropdown list Background Map lets you select from 4 major options:

Additional configuration fields will appear based on the selection and must be completed.

OpenStreetMap

This map service is enabled by default. No further configuration is needed. The OSM server is hosted by OpenStreetMap.org.

OpenStreetMap (hosted by Leica Geosystems)

No further configuration is needed. The OSM server is hosted by Leica Geosystems.

Custom WMS

The custom WMS server will work with SBC only if the following requirements are fulfilled:

The server must respond with WMS compliant XMLs. If the server does not return a compliant XML, SBC will show an error message. If this is the case, make sure the server returns compliant XML before connecting to SBC or use another server.
These headers are related to the CORS (Cross Origin Resource Sharing) policy of the custom WMS server you are trying to connect to SBC. If the server response does not contain these headers, SBC will show an error message.

The custom server’s AJAX responses must contain the following headers:
- Access-Control-Allow-Origin: * or http://{hostname}/sbc (with your Frontend URL)
- Access-Control-Allow-Headers: Authorization
- Access-Control-Expose-Headers: WWW-Authenticate - in case of using digest authentication
The WMS server must support the EPSG:3857 projected coordinate system (equivalent to EPSG:900913 and EPSG:3785), and it must return at least one layer with this projected coordinate system.

When the server is correctly configured, i.e., the given URL is responding, SBC will display the available layers and will update the preview map.

Parameter	Description
URL	Set the WMS URL, with the following structure https://{hostname}/{path}.
Layers	Automatically populated field. It will display the layers which support EPSG:3857 projected coordinate system. The layers which do not support it, are not displayed by SBC.
Map attribution	Contains a list of contributors, sources or the copyright text. Due to the “terms of use” it is mandatory to fill the map attribution field.
Map attribution link	Contains the link to the map attribution page, if it is needed.

Custom XYZ Tiles

The custom XYZ Tiles server will work with SBC only if the following requirements are fulfilled:

The server must response with PNG tiles.
These headers are related to the CORS (Cross Origin Resource Sharing) policy of the custom WMS server you are trying to connect to SBC. If the server response does not contain these headers, SBC will show an error message.

The custom server’s AJAX responses must contain the following headers:
- Access-Control-Allow-Origin: * or http://{hostname}/sbc (with your Frontend URL)
- Access-Control-Allow-Headers: Authorization
- Access-Control-Expose-Headers: WWW-Authenticate - in case of using digest authentication
The Tile server must support the EPSG:3857 projected coordinate system (equivalent to EPSG:900913 and EPSG:3785), and it should return a tile with this projected coordinate system.

When the server is correctly configured, SBC will display the available tile and will update the preview map.

Parameter	Description
URL	Set the Tile server URL, with the following structure https://example.com/{z}/{x}/{y}.png.
Map attribution	Contains a list of contributors, sources or the copyright text. Due to the “terms of use” it is mandatory to fill the map attribution field.
Map attribution link	Contains the link to the map attribution page, if it is needed.

Support Satellite Imagery

The satellite imagery can be selected as an alternative to the configured background map, depending on the user access level. It has three possible options:

Option	Description
Off	Disables the satellite imagery layer for all users.
Administrator roles	Only users with administrative roles can see and use the satellite imagery layer
Administrator and User roles	All users, regardless of role, can view and use the satellite imagery layer.