User settings

User status

The current status of the user. Possible values:

Active - User can login and receive notifications

Inactive - User cannot login and will not receive any notifications

Protected from modifications

If activated, the user cannot be modified.

This applies both to modifications done in EMS and modifcations done by user synchronisation.

System role

The role defines the rights which are assigned to the user:

User – Standard user with possible rights to activate episodes, receive notifications and send reactions.

Responsible user - Administration rights for entities which belong to the same Auth Group as the responsbile user.

Admin - Administration rights for all entities which belong to the tenant. An admin user cannot modify or delete other admins.

Tenant - Has the same rights as an admin user, but can additionally modify and delete admin users.

Business role

Allows to define the role of the user within the company or institution.

This value can e.g. be used to filter for users or for definition of conditional user groups.

Private security code

If a private security code is defined, and the setting "Protect activity by code" is enabled in the event configuration, the user will be asked to enter the code when reacting to an episode.

This feature can be used to add an extra layer of security when reacting to episodes, ensuring the users identity and preventing unintentional reactions.

Auth Groups

Each user can be assigned to one or multiple Auth Groups, see also configuration of Auth Groups for more information.

Access to EMS

If enabled, the user is allowed to log in to EMS.

Allow Digital Signage

If enabled, the user will see the screen as defined in the Digital Signage settings after logging into the desktop client or web application.

Infinite Push

This setting affects the number of push notification that a user will receive for an episode.

If disabled, the user will receive push notifications until he opens the episode in the app or until the max. number of pushes which is defined in the event settings is reached.

If enabled, the user will receive push notifications until the max. number of pushes from the event settings is reached or until he sends a reaction to the episode. Opening the episode in the app will not stop the reception of push notifications.

Note:

This setting only applies to the mobile apps.

Allow disarm user

If enabled, the user has the rights to disarm himself from specific events.

While being disarmed, the user will not receive any notifications for the events.

The notifications are not queued, i.e. the user will not receive them after stopping the disarm status.

Allow disarm user – max. time (hours)

The maximum duration in hours for which a user can disarm himself.

If the "No end date" checkbox is selected, no limitation is applied to the maximum duration. The user can disarm himself for an indefinite timespan.

Allow disarm event

If enabled, the user has rights to disarm events.

Events cannot be activated while they are disarmed. Also, at the moment in time when an event is set to disarmed, all active episodes for that event will be closed.

Note: also in the event configuration, it must be enabled that the event can be disarmed.

Event when disarm

Select an event which shall be triggered when this user disarms any event.

Allow device mute

If enabled, the user can mute the event sound in the applications' settings menu.

Note: Only applicable for Android and desktop client.

LIVE LOG access

If enabled, the user has the rights to see the live logs, i.e. the logs of a running episode, in case he is either activator or recipient of that episode.

LIVE LOG access if activator

If enabled, the user has the rights to see the live logs, i.e. the logs of a running episode, in case he is the activator of that episode.

POST LOG access if activator

If enabled, the user has the rights to see the post logs, i.e. the log of closed episodes, in case he is the activator of that episode.

POST LOG access

If enabled, the user has the rights to see the post logs, i.e. the logs of closed episodes, in case he is either activator or recipient of that episode.

Allow Episode Activation by URL

If enabled, the user can activate an episode by clicking on a URL. The URL can be set e.g. as a shortcut on desktop or a bookmark in a browser.

The URLs are unique for each user and can be copied from Users -> User -> Events List.

Allow Calendar

Allow usage of the feature "Calendar" for this user.

Allow Asset Management

Allow usage of the feature "Asset Management" for this user.

Allow Work Orders

Allow usage of the feature "Work Orders" for this user.

Allow Presence

Allow the user to access presence reports

Note: this is only available on mobile applications

Allow Lone Worker Viewer

Allow the user to see the overview of active lone workers.

Note: this is only available in the desktop client and in the Android application.

Permission for monitoring service

User is allowed to use the monitoring service.

Note: This setting is mandatory for using the lone worker feature.

MBO status

If the user has enabled the MBO feature in the application, the status will be displayed as Enabled.

Track location

If enabled, the current position of the user will be stored on s.GUARD.

Note:

• The position will only be accessed in case of an alert for this user
• The setting is only available if the feature is activated by Swissphone support for that tenant.

Track perimeter

If enabled, it will be tracked if the user is within a defined perimeter.

Note:

• The perimeter information will only be accessed in case of an alert for this user
• The setting is only available if the feature is activated by Swissphone support for that tenant.

Alert after

The timespan in seconds after which an MBO alert will be triggered, if no pings are received from the application for this user.

Note:

The app will send 3 pings during this timeframe.

E.g., if this configuration is set to 60s, the app shall send a ping every 20s.

Alert group

The event which shall be triggered for an MBO alert, i.e. if no ping has been received during the timeframe which is configured for the setting "Alert after".

Status information

Info event which shall be triggered upon start and stop of the MBO monitoring for this user.

Note:

Within the event message of the info event, use the placeholder ~message~ to access the information about which user has changed the monitoring status.

Max extend monitoring service (sec.)

The max. time which a user can define as absence from the MBO monitoring.

Enable keep alive pings

If enabled, the desktop client will send regular ping messages to the s.GUARD backend.

This is required in some network environments to prevent the network from interrupting the connection between desktop client and backend.

Interval time (sec.)

Time between ping messages in seconds.

Permission to Offline Warning

If enabled, offline warnings can be used on the mobile apps.

Offline Warning Status

If the user activates offline warnings in the mobile app, the status will be set to Enabled.

Warning after (sec.)

Defines the timeframe for how long the device can be offline before a warning is displayed on device.

A device is considered to be offline when it has no active internet connection.

Example: if this value is set to 30, the application will start to display offline warnings 30 seconds after the device has lost its internet connection.

Warning time (sec.)

Defines the timeframe for how long the device is displaying offline warnings.

Example: if this value is set to 60, the device will display offline warnings during 60s. After this time is elapsed, it will stop notifying the user about the offline status.

Interval time (sec.)

Define the time between the offline warning push notifications which are displayed on the device.

Example: if this value is set to 10, the device will display every 10s a push notification with the offline warning, until the warning time is reached.

Warning message

The text which is displayed to the user in case he goes offline.

Use default

If enabled, the default text is used to inform the user about his offline status.