The users menu provides the following sub menus:
The level of access to SBC is mainly affected by the privilege which is assigned to each user.
All users contained in SBC are displayed in a paginated grid view. The overview page supports basic functionality like create, edit, view or delete user entries as well as create new subscriptions just by clicking on the respective icons. Search is related to all columns displayed in the overview page, which are:
The users search box supports all kinds of characters. All columns except counting number are sortable.
The checkbox "Filtered by" predefines the users search box content with a dropdown list containing the three filter values
Default field is Subscribers. Select one value from the dropdown and click on reading-glass symbol to view filtered results.
User Registration States
Three different states are supported.
ACTIVE, indicated by
User can access and modify his profile and subscribe to articles from shop.
PENDING, indicated by
User cannot access his profiles until admin activates or he activates through the activation link sent to his E-mail.
INACTIVE, indicated by
User cannot access his profile. Only admin can activate his profile.
The three keywords are also supported by the users search box. Searching e.g. for value pending would display all users with the related state indicated by.
SBC supports SSO authentication through OpenID connect compliant Identity Providers (IdPs).
The following SSO User statuses are supported:
Linked to SSO, can access Spider Software Suite services - indicated by
→ User is created and active in the Identity Provider for SSO authentication, and is able to login into SBC.
Linked to SSO, cannot access Spider Software Suite services - indicated by
→ User is created in the IdP for SSO authentication, but is not allowed to access any of the Spider Software Suite services, including but not limited to:
The three keywords are also supported by the users search box. Searching e.g. for value UNLINKED TO SSO (full text to be used) would display all users with the related state indicated by
Once a user is linked to the SSO login system, then the only way the access would be granted to the SBC web interface (Admin Portal and User Portal) is via SSO login.
When a user has been marked as inactive in the IdP for a certain period of time (e.g.: resigned), then marked back as active (e.g.: returning to the company), then the user can access Spider Software Suite services again, meaning that account will be reactivated in IdP.
The detail view provides the credentials, the personal data, the subscription details and particular GNSS Spider settings of an individual user. Each section is separated by a tab view.
Details“Details” contains the user credentials as well as all personal data. It also supports the setting of user privileges, preferred user languages and the upload of a user pictures. “Details” is the default page that opens if one of the basic actions Create new record, Modify existing record or View existing record is executed on the overview page.
SubscriptionsDisplays details about all subscriptions and articles assigned to the selected user.
GNSS RoverIt contains special settings that have direct effect on the user authentication and connection logging within GNSS Spider.
| Parameter | Description |
|---|---|
| Maximum simultaneous access |
Set the number of maximum simultaneous accesses for the user. Connections trying to access the RT product when the maximum number of connections is reached will be denied. This setting does not affect the X-pos services. In case of using limited SBC User Licenses, article no. 812426 to 812428, this value counts as number of SBC users and reduces the user license quota. For the RT Product Type Single Rover (NMEA Redirect), multiple simultaneous access must be set to 1. Multiple simultaneous accesses greater than 1 are not allowed. Rover communication messages The maximum simultaneous access settings can have an effect on rover connections and communication. See the GNSS Spider online topic "Watch view messages: Rover user communication" for more detailed information. |
| Rover inactivity validation [s] |
Set the number of seconds Spider should hold the connection, after the last heartbeat is received from the user. The setting is used only, if the Spider RT-Product is of “Type” Automatic cell, Single cell or Nearest site. Enter a multiple of the NMEA-GGA message output rate of the rover equipment used by the user. Enter 0 to disable the heartbeat check for this user for all connections to any RT-Product. Default: 30 s Example: Leica Viva NMEA-GGA rate is 10 s. With a tolerable loss of one message, a good setting would be 20 s. If the automatic closing of rover connections is used by a RT-Product in GNSS Spider, the connection of the user will be closed, if Spider does not receive a NMEA-GGA message for more than 20 s. This means if the user’s mobile network connection is interrupted, but the mobile network provider does not close the connection to Spider, Spider will close it after 20 s. The rover will be able to re-connect to Spider at the latest of 21 s after interruption, even with “Maximum simultaneous access” set to 1. See also GNSS Spider online help Glossary on “Heartbeat”. |
| Include in general connection log |
Activate to include information of connect/disconnect for this user in the general connection log. General connection log must also be enabled on the Network server / Tools / Configuration... / Connection logs tab. |
| Generate detailed connection logs |
Activate to have GNSS Spider generate a detailed connection log for this specific user. Detailed connection log must also be enabled on the Network server / Tools / Configuration... / Connection logs tab. |
| Transfer detailed connection logs via FTP push |
Activate to have GNSS Spider push all detailed connection log files to a pre-set FTP location. FTP location for detailed connection log must also be selected on the Network server / Tools / Configuration... / Connection logs tab. |
| Generate NMEA data logs |
Activate to have GNSS Spider generate a NMEA log for this specific user. NMEA log must also be enabled on the Network server / Tools / Configuration / Connection logs tab. |
| Display rover position in Live View |
This option controls whether received NMEA positions of a user are displayed in the Live View or if the user stays incognito. Default value is marked. it takes 1 hour until changes are considered by the Rover Live View. |
| Output rover position to reports | This option controls whether stored NMEA positions of a user are outputted to the Usage Reports or if the user stays incognito. Default value is marked. |
Preferences contain user specific settings for receiving notifications and the favored NTRIP Caster.
The Preferred Notification Method specifies the media by which the user will receive notifications from the service operator. By enabling the E-mail option user will receive the notifications as E-mails to the E-mail address configured in the profile. E-mail is enabled by default.
The Preferred NTRIP Caster is used to inform SBC users about Caster connection details. It is shown to users who are logged in to SBC when they navigate to User Profile. The data is initially derived from the global NTRIP Caster Settings but can also be changed by user to record any preferred NTRIP Caster connection data.
| Parameter | Description |
|---|---|
| NTRIP Caster host name | This host name (e.g. MyCaster) is usually used by the user account to access a real time data stream via NTRIP. |
| NTRIP Caster port | This port is used and shown as standard NTRIP caster port (e.g. 2101). |
| Check Connectivity | Verify the connection to the configured NTRIP caster. According to the result the status is Connection Passed or Connection Failed. |
This tab allows extracting rover user connection details from the Logging Server database. At this page all requests are related to the particular user whose properties have been opened in order to display further details.
Further information about rover usage requests and their results can be found in Usage Reports.
The Error Logs page displays rover error messages coming from the GNSS Spider Network Server. Rover Error messages are divided per day, where the user can expand a drop-down menu listing all items in a table of information. For each entry, the table contains the time of message; by clicking the icon in the last column, users are able to visualize the Detailed Connection Log.
The following connection events are supported to be displayed:
| Connection Events |
|---|
| User is not authorized. Access denied.- No display – requires proper user login |
| Authentication mode is not supported. Access denied.- No display – requires proper user login |
| No GPUID message received for authentication. Access denied.- No display – requires proper user login |
| Incorrect password of user. Access denied. |
| Invalid coordinate. Access denied. |
| No GPGGA message received. Access denied. |
| No or empty host information received. Access denied. |
| No host and no user information received. Access denied |
| Ntrip authentication or mount point not received. |
| Ntrip mount point not received. |
| No or empty phone number received. Access denied. |
| User outside of the authorized region. Access denied. |
| Access denied due to SBC fall back 'Always denied'. |
| Too many concurrent authorization requests. |
| Too many concurrent connection requests for rover user. |
| Too many concurrent connections. |
| Rejected unknown user. Access denied. |
| User is not authorized. User expired. |
| Empty user name received. Access denied. |
| Fallback to single site activated - below minimum distance from master. |
| Fallback to single site activated - network fixing. |
| Fallback to single site activated - rover outside network. |
| Fall forward to network solution activated for Rover user. |
| Currently no data available. |
| Rover user rejected. No heartbeat received. |
| No data available at location - rover outside of the network. |
| No data available at location - rover left network boundaries. |
Messages older than 5 days are not displayed.
Following buttons are provided to complete the modification of user details:
The Credentials overview displays all users contained in SBC but focuses on the four different RTK authentication methods that are supported by SBC.
| RTK Authentication | Description |
|---|---|
| NTRIP | RT data streams that are configured in GNSS Spider to authentication type Ntrip require the Ntrip User name and Ntrip password. The Ntrip authentication is no longer valid for logging on to the SBC Web frontend. |
| GPUID | RT data streams that are configured in GNSS Spider to authentication type GPUID require the GPUID1 and GPUID2 credentials. |
| Dial-in |
This option is used when real time data streams are provided by access router and the GNSS Spider authentication type is set to telephone number. The rover user telephone number for dial-in authentication is expected here. Please consider that any change may result in refused rover user authentication. Corresponding action is required on the rover side as well. The telephone number format is dependent on the country and telephone provider and may not require leading zero and/or country codes. |
| TCP/IP |
The rover users host name or IP-address needs to be entered, when the GNSS Spider authentication type is set to TCP/IP. Consider that any change may result in refused rover user authentication. Corresponding action is required on the rover side as well. |
The credentials overview page supports basic functionality like create, edit, view or delete user entries as well as create new subscriptions just by clicking on the respective icons.
Search is related to all columns displayed in the overview page, which are:
The users search box supports all kinds of characters. All columns except counting number are sortable.
The checkbox “Filtered by” predefines the users search box content with a dropdown list containing the four filter values
Default field is NTRIP. Select one value from the dropdown and click on reading-glass symbol to view filtered results.
Show PasswordThe SBC User password is encrypted, and therefore not visible for any type of SBC user, including the Administrator, Support Viewer and Operator. Only the new typed password can be visualised, by pressing the Show button. Once the form is saved, the password will not be shown in clear text anymore, but a placeholder will be shown.
The NTRIP password is stored in an encrypted way and masked by default (crossed eye). Click on the Show password icon to decode the password and display it as clear text. The state of this icon can be changed only by users with privilege Administrator and Support Viewer.
The Devices view displays information about successfully connected and authorized rover connections using GNSS Spider. The main intention is to give an overview about the distribution of GNSS Rover types utilized in the real-time GNSS network. The content of this view is automatically updated depending on NTRIP rover connections. The displayed rover type is sent within the NTRIP message, along with the rover firmware version for some rovers.
Search is related to all columns displayed in the overview page, which are:
The search supports all kinds of characters. All columns except counting number are sortable.
The checkbox "Filtered by" predefines the devices search box content with a dropdown list containing the two values iOS and Android. Filter results are returned only if mobile app users were connected.
The Top 5 used GNSS Rover types are also displayed in a chart at Tools – Dashboard
is used to export the selected records in the Devices table to CSV.
is displayed next to the button in the Device table.
Users can be combined to user groups. All groups contained in SBC are displayed in a paginated grid view.
The user group, everyone is a default group and it always includes all registered users. This group cannot be deleted and it cannot be selected as a subscription owner.
Overview PageThe overview page supports basic functionality like create, edit, view or delete user group entries as well as create new group subscriptions just by clicking on the respective icons.
Search is related to all columns displayed in the groups overview page, which are:
The user group search box supports all kinds of characters. All columns except counting number are sortable.
Deleting a group which is owner of a group subscription, automatically deletes the related group subscription and all related member subscriptions.
Creating a new group or editing an existing opens the group details. Supported details are:
Click on icon on top right of the members overview “Contained Individuals” to open the list of all users. Select one single or multiple user and press “Close” to finish the selection. Press “Save & Close” or “Save” to store all entries to the database.
Adding individuals to a group which is owner of a group subscription, automatically creates the related member subscriptions.
Move the slider in column Assigned from Yes to No to delete a member from the selected group. Press “Save & Close” or “Save” to store the changes to the database.
Deleting individuals from a group which is owner of a group subscription, automatically deletes the related member subscriptions.
This section outlines various levels of privilege that can be assigned to a user account.
The level of information and allowed procedures within SBC for any specific user is defined by the privilege level assigned to the particular user account.
| Privileges | Description |
|---|---|
| Administrator | Master Administrator, with unlimited rights. |
| Support | Can view all pages of the Administrator portal, but cannot edit. |
| Operator | Can view all pages of the Administrator portal, can create/edit/delete new Users, Regions and Dealers, can create new Subscriptions but cannot edit existing ones, and cannot modify most of the Settings. |
| Sales Organisation Administrator | Sales Organisation Administrator is able to manage all data associated to his sales organisation. |
| Dealer Administrator | Dealer Administrator is able to manage users associated to his Dealer Organisation. Cannot create another Dealer Administrator user. Dealer Administrator is able to manage users associated to his Dealer Organisation. Cannot create another Dealer Administrator user. |
| User | No access to the administrator portal. |
The table below summarizes all the actions available for each user level.
| Functionality | Administrator | Operator | Support | Sales Organisation Administrator | Dealer Administrator | User |
|---|---|---|---|---|---|---|
| User Management | ||||||
| Enter own profile | ||||||
| Edit own profile | ||||||
| Edit various profiles | ||||||
| View all profiles | ||||||
| View user access status | ||||||
| View user privileges | ||||||
| Edit all users | ||||||
| Create / delete users | ||||||
| Group users | ||||||
| Change user access status | ||||||
| Change user privileges | ||||||
| Article Management | ||||||
|
View list of published articles |
||||||
| Subscribe to articles | ||||||
|
View own subscribed articles |
||||||
|
View subscribed articles for groups |
||||||
|
View subscribed articles for all users |
||||||
|
View public and private articles |
||||||
| Assign articles to users | ||||||
|
Change article status (private / public) |
||||||
| Create articles | ||||||
| Regional Policy Management | ||||||
| View assigned regions | ||||||
| View list of defined regions | ||||||
| Assign regions to articles | ||||||
| Define regions | ||||||
| SBC Configuration | ||||||
| Edit user sign up template | ||||||
|
System (e.g. Default language,
E-mail server, terms and regulations). |