Creating Flight Manager Accounts in FOS

Creating Flight Manager Accounts in FOS

For Users who are on FOS version 3.11.4 or higher Flight Manager Accounts are able to created in FOS. The steps below will walk the user through how to create the Flight Manager accounts in FOS.  


1. To activate the sync between FOS and Flight Manager for the Flight Manager Account / Unified Sign-On Capabilities for the FOS Mobile application the “Activate Account Synchronization” button needs to be enabled. This is a one-time only setting so once it is turned on it does not need to be selected each time an account is created. 

When checked, users will receive a pop-up message highlighting the important details regarding this feature. 

Before enabling this feature, if a user has existing Flight Manager credentials, the username and password should be entered into the Interface tab of their FOS user profile. If this has been done, select “Yes” to the pop-up message. If not, select “No” and proceed to the User module to adjust all User profiles accordingly. 

If “Yes” is selected and existing users do not have their Flight Manager account credentials entered, this will cause the Unified Sign On abilities for the FOS Mobile application.


2. Create a User profile in FOS and ensure the Unique E-Mail field is populated as this will be the address used to log into Flight Manager and the FOS Mobile application. Password resets for mobile will also go to this address. 


3. Ensure the user has the Mobile Access box checked on the Mobile Tab of the user profile and the correct permissions are set. 
4. Click OK to save the record. This will generate an email that will be sent to the email address that was listed in the unique email field. 
5. Have the recipient follow the directions in the email to establish their password. The password requirements, as listed on the site are:
6. The user can now log into the FOS Mobile application; their email will be their username and the corresponding password that they just set.  


In step 4, if an email was not sent out to the user or the user is having issues accessing the new mobile application there could be an account sync error. All account sync errors can be displayed from the user module by checking the Account Sync Error check box as shown below. 
Detailed information regarding the error messages that are being displayed can be found in the article titled "Account Sync Error FOS Sync Error Messages". 


The accounts are able to be deactivated through the Mobile & Web Management module >  Account Management tab by selecting the green account status icon to the right of the corresponding user. Additional information on this feature can be found here

    • Related Articles

    • Account Sync Error - FOS Mobile

      Account Sync Error checkbox in the FOS Users Module A new checkbox has been added to the main screen of the FOS Users module for the viewing of Mobile account issues. This field has been added for FOS Version 3.11.4 and higher and corresponds to the ...
    • Mobile & Web Management - Account Management

      The Mobile & Web Management Module can be accessed from the Admin Tab of FOS. The Account Management will list all of the Flight Manager accounts associated with the company. If the Flight Manager login is linked with a FOS ID, it will display this ...
    • Installing FOS Mobile

      The below includes documentation for a Windows 2012 Server, some variations may be seen depending on your server. Initial Install Files and Updates to FOS Mobile are included in the FOS Installer. You will need to run the installer and install the ...
    • Installing or moving FOS to a new server

      If FOS has already been installed on a server and needs to be moved to a new server follow the steps below: 1. Make a Copy of the FOS and Data Folders. Ensure all users are logged out of FOS when this occurs. 2. Deauthorize the Pervasive key on the ...
    • Installing FOS on a new workstation

      First you will want to install the appropriate version of pervasive. Remember when installing pervasive on a client machine to use the 32-bit client version of Pervasive. The client machine needs to have the client version of pervasive that is ...