Which security features are available in the new mobile app version?

• If you have the App with In-App Branding:
  • Screen lock: This feature requires the user to log in with a pin, pattern, face ID or fingerprint again immediately after leaving the application. Even if the application was open in the background. Every user can decide in their individual settings if they want to use screen lock or not. More details how to use it can be found here.
  • Root Detection Users are notified that their device is rooted when they first open the app.

• If you have the App with an own App Icon and In-App Branding:
  • Screenshot blocking: Customers can now increase security by preventing screenshots and screen recordings within the app. If you activate screenshot blocking, users are no longer able to do screenshots or screen recordings in their employee app.
  • Screen lock: This feature requires the user to log in with a pin, pattern, face ID or fingerprint again immediately after leaving the application. Even if the application was open in the background. You can decide if you want to enforce this functionality for all users, then everyone has this functionality, or if you don't want to enforce it, users have this functionality in their settings and can decide if they want to enable App Lock or not. The user guide can be found here.
  • Root Detection Root detection enables the user to be notified that their device is rooted when they open the app for the first time. You can decide if users either should be notified that their device is rooted when they first open the app but still can continue using the app, or the notice can also be set so that it is no longer possible to use the app with a rooted device.

Can I go back to the transition-code, if I forgot/it expired?

• Yes, you can go back to the page where the code is generated
  

• After a successful migration, it is still possible to get a new code via the old app for one week, for the case where the user accidentally deletes the new app. After that week, we'll lock the user out and they won't be able to get a new code.

After downloading the new app version - Will the old app be deleted?

• No, but Push-Notifications for the old app will be deactivated, so that you don’t get duplicated Push-Notifications. Also if you open the old App, there is a full screen which informs you that this is the old app. After a week, the user get logged out in the old app.
  

If users download the app for the first time, e.g. new employees, do they also see the migration stuff?

• Yes, new users will see the same screen for the migration period after downloading the new app as users who had the old app before. They must click on ‘Use my credentials’ and can then log in for the first time. After the defined migration period, the login-screen is back to normal again, and new employees don’t see any migration stuff.
  

What are the differences in the migration process between iOS and Android?

It depends on what version of the app the employees are using.

• iOS users:
  • Employees need to follow the instructions in the employee app and download the new version of the app. No relogin needed
• Android users - downloaded App over the Browser (Progressive Web App)
  • Employees need to follow the instructions in the employee app and download the new version of the app in the Google Playstore. No relogin needed
• Android users - downloaded custom App over the Google Playstore
  • Employees need to follow the instructions in the employee app and update to the new version of the app in the Google Playstore. No relogin needed

What is the deadline for updating to the new version as a user?

• There is currently no deadline. The Customer Success Managers at Flip can activate the migration for the customer whenever the customer is ready. Best case, this is done before November 2024.
• When activating the migration, the customer can decide whether users must migrate, i.e. whether they can no longer use the previous app version, or whether users can still use the previous app version for the time being. The customer can first decide in favour of the voluntary path and after a certain time set the setting via the CSM so that users must now migrate and can no longer use the previous app
• The customer can track the migration success over a dashboard.
• If most of the users are migrated, the customer can also decide to disable the migration. The users than will not be able to migrate via code, but will be able to download the new app via a banner in the settings, but will have to log in with credentials.

Approximately how time-consuming in minutes is the upgrade for the users?

• The upgrade to the new version is easy and fast. It takes around 1-2 minutes depending on the internet connection of the user from starting the migration, downloading the new app version and being logged in (without relogin) in the new app version.

How does the migration work technically?

• Transitioning to our new mobile application is designed to be seamless and secure, ensuring that your session continues without interruption.
• Here’s a straightforward look at how it works:
  
  • Code Generation: Initially, when you are logged into our old application, we generate a unique code linked to your authenticated session. This code acts as a temporary key for transitioning to the new app.
  • Code Entry: Upon opening the new application, you will be prompted to enter the code you received from the old app. This is a simple step to connect both applications without sharing sensitive data.
  • Session Link: After entering the code, the new app communicates with our backend system to exchange the code for an action link. This link is crucial as it carries the information needed to establish a new session in the new app.
  • Authentication and Tokenization: Using the action link, the new app initiates a session and performs a secure authentication process. This results in the new app receiving a valid token, enabling full functionality.
  • Normal Operation: With the authentication complete and the token received, the app transitions into a normal operational state. You can now use the new app as you would have used the old one, with all features fully accessible.
• This transition process is designed with your security in mind, ensuring that no personal data is transferred openly and that each step is verified for authenticity.

How is the data collected for the new migration analytics dashboard?

• When the user opens the old app, a banner appears telling them that there is a new mobile app and that they need to copy the transition code.
• When they click on the button to copy the transition code, a 'transition code' is created in the background.
• The user copies this and then pastes it into the new app. As soon as this code is created, we write down this code together with the user_id in the backend and track whether the code is actually redeemed, and the user then successfully logs into the app.
• No user data is read out here, only data on the successful redemption of the code is analyzed.

What security measures are in place during migration?

In addition to the code, there are the following security measures:

• The code only works if the login using the code originates from the same IP address that was previously used in the old app
• The code has a maximum validity period of half an hour
• The code can only be used once

Do I need to schedule time to test the new app version?

• No, you don't need to plan any time for this.
• As your data and settings are saved in the Flip Cloud, all data such as posts, chats, events and employees are also available in the new app version.
• Even logging in with SSO does not require a new configuration, as the configuration is also saved and loaded via the cloud.
• We offer you the option of installing our test app “Artemis employee app” and logging in with your system if you would like to test the app and the SSO login in advance.
  
  • Android: https://play.google.com/store/apps/details?id=com.artemis.employeeapp
  • iOS: https://apps.apple.com/au/app/artemis-employee-app/id6484270936