On request, the mobile app can also be provided as APK for distribution via MDM. Please reach out to your designated account manager who will guide you through the process and provide further details.
First Time Login
There are three options:
Via Account Email Address - Recommended: For persons with access to an email address, set an account email address (needs to be unique in the system). After having downloaded and opened the mobile app, persons should click on “Login with password” and then “forgot password”. They will receive an email to their account email address with a link to set a new password. This can then be used to log into the mobile app (as well as the web portal – see https://helpplus.fact24.com/l/en/article/y3u8bnlw90-web-login-for-persons)
Note that people configured as “users” in the web portal can automatically log into the mobile app via this way with their password. If 2-factor-authentication via SMS is enabled for their account, it will automatically also apply for the mobile app login.
Via PIN and Device Password: For persons without own email address use application ID, first time PIN login and device password: - Share application ID and PIN login with the person via another device (e.g., their phone number). You can use an ad-hoc alarm for this: https://helpplus.fact24.com/l/en/article/djzk6nmc9z-send-notification
The person should then select “first time login with PIN”. They will then be asked to set their device password. For any future login, “Login with password” should be used.
If in this setup, the person ever loses their password, an administrator can change their password manually in the web portal. For security reasons, however, we recommend to re-create the person to re-enable first-time login procedure via PIN.
Via Self-checkin: For a person to use this functionality, the according settings must be enabled for the entire account. Please check with an administrator, or if you are the administrator with your F24 account representative.
Click “check in yourself”
Enter requested details
Accept end user agreement
Check your email inbox
Set a password -> go to mobile app and login with password
You will get see all content that you have access to according to the organization’s default profile (see next page)
The same person can use the same login data to log into the web portal
Simply use the same credentials as for the mobile app
Person’s email address is used as account email address which makes this possible
Again rights are granted according to assigned profile
For self-registered persons, the account default profile will be auto-assigned
Simply use the same credentials as for the mobile app
Person’s email address is used as account email address which makes this possible
Again, rights are granted according to assigned profile
After 30 days of inactivity, any person or user will be automatically logged out from the mobile app. The person will still receive alarm notifications as push but will then be asked to re-login to view the full message and give a response.
First steps
When a person accesses the mobile app for the first time, she will be asked to grant specific permissions. At minimum, a person should accept to receive notifications since otherwise the mobile app cannot serve as a reliable notification channel.
Specific to iphones, we also recommend to enable the critical alert functionality:
These settings can be changed at any given time in the phone configuration:
Permissions on Android:
Why certain permissions are needed:
Personal data: usually an email address or telephone number is used for authentication in the mobile app. However, this could also be set up in the portal independent of a person.
Messages: Alerts and chat notifications.
Photos and videos, as well as audio, files and documents: if an alarm is triggered via the mobile app, photos, videos or audio recordings can also be sent along with the alarm. If authorization is not granted on the end device, this function is not available.
Location information: for both incoming and outgoing location-dependent alerting. If authorisation is not granted on the end device, this function is not available.
Note: When the mobile app gets distributed via MDM, these permissions can be pre-configured. Please note that the person can still decide to e.g., not share GPS data, or whether or not Do not Disturb should be overwritten, in the location settings of the mobile app. These settings cannot be centrally managed via MDM.
Finding your way around
In Settings, a person has the possibility to configure specific notification and trigger settings, as well as to access her account to configure devices and logout. Per default, nothing has to be changed here to get started. For further information click here: https://helpplus.fact24.com/l/en/article/pj08on2qoi-general-settings
,
When clicking on the top right person icon, the person can set herself to be offline (or vice versa). As soon as a person is offline, she will only receive alarm messages for alarms where “offline status” is overwritten. Persons should be informed about the consequence of this functionality to not miss out on any important information accidentally.
In addition, the person can access her account information or logout directly from here.
If no app profile has been assigned to a person (so no additional rights granted to the person), this is an exemplary display of the mobile app:
When you log in as a user – independent from any configuration, or if you have a connected person or not - you will see one more tile on your home screen – the portal access. If you click on it (and you have the according user role), you will be directly taken to the alarm cockpit like you know it from the web view to trigger, monitor alarms, and manage chats and conferences. Depending on your user role, you might also have access to the reports and statistics, and operating cockpit section.
Note on hardware
Our mobile app is designed to operate seamlessly across a wide range of devices. Generally, you can expect full functionality on most phones. However, for features specific to certain devices, these will be clearly outlined. Our testing process encompasses a curated list of devices representative of the broader spectrum, ensuring a reliable user experience.
Samsung Galaxy Xcover
Samsung Galaxy A54
Google Pixel
iPhone 11
iPhone 13
Ascom Myco 3
Ecom Smart Ex-02
We understand that clients may have specific devices not covered in our standard testing. For a 100% guarantee on compatibility, we offer a tailored testing service for an additional fee. If you are interested in this service or have specific device-related inquiries, please reach out to your designated account manager who will guide you through the process and provide further details.
Prerequisites
Preamble
In general, no manual configuration is required within the FACT24 ENS+ app on the mobile device of a person.
For a participant to be able to log in to the mobile app, an application device must be created for their person in the web portal. For more information, please refer to the article on person configuration.
If the person should not only receive alarm messages, but also trigger alarms or view emergency documents, a profile has to be assigned in the web portal.
Depending on the operating system version and smartphone manufacturer, the op-eration may vary slightly. It is recommended to test the respective devices used inadvance and after each major version update.
Note on Android
Android
The FACT24 ENS+ Android version offers in contrast to all other platforms (e.g., iOS) the most diverse possibilities since Android basically allows much more control over the hardware. The operation and configuration are identical on both platforms and is therefore not explained separately.
Emergency plans can be stored via the app profile. These serve as instructions for the users and can be provided categorized. Depending on the file type (TXT, DOC, etc.), the respective display program on the smartphone is required.
Installation
The FACT24 ENS+ App can be obtained free of charge via the Google Play Store
Permissions
Depending on the function used, individual authorizations may be necessary, these are queried when the function is initially activated and must be approved for operation. This includes location permissions. During the initial installation, these are queried, but can be issued later. Via APP info or settings, you get to the APP permissions.
Location: for both incoming and outgoing location-dependent alerting. If authorisation is not granted on the end device, this function is not available.
Personal data: usually an email address or telephone number is used for authentication in the mobile app. However, this could also be set up in the portal independent of a person.
Messages: Alerts and chat notifications.
Photos and videos, as well as audio, files and documents: if an alarm is triggered via the mobile app, photos, videos or audio recordings can also be sent along with the alarm. If authorization is not granted on the end device, this function is not available.
IMPORTANT: Please check the permissions after each update or set up your MDM so that they are set when distributing the APK.
APP Configuration
Specifies whether the FACT24 ENS+ Server or an alternative server is used. Standard: FACT24 ENS+ Server active
Enter the access data as in Configure Person. If you forgot all access data, you could either call your account admin and ask to set a new one in the portal, or you go to the portal login page (if you have an account email address) and request a new one. (we will make the “reset password” option available on the SSO screen as well in the near future)
In the settings, individual settings can be set about ringtones and notification options. In the standard, nothing must be changed here.
The user can put themselves in the online or offline state via the app. Although the app is still connected to the FACT24 ENS+, the user only receives alarms if they have been activated via a separate option within the alarm. For more information, please refer to the FACT24 ENS+ documentation.
Display a user who does not have an app profile assigned. This user may only receive alarms but may not trigger them
