Master and child instances

Flying Fleet support a master / child relation between instances. To set this up, on the master instance a user with administrator right must be created and this account must be used to link the child instance to the master.

Once the link is created, if a member tries to log on a child instance while his/her information is not known, the child instance will try to pull the data from the master based on the email address provided. An administrator can also retrieve a member profile by simply providing a valid email address in a new member entry, save and then use the buttom "Get from master".

Members linked to a master instance will have an additional "Linked to master" read only field in the admin member detail page.

If the member or an admin edit profile details in the child instance, the data will be pushed back to the master immediately. Password updates on the child instance will also be passed to the master instance.

An update on the master instance will however updated only once per day (during the daily early morning scheduled task).

The password of a member will be checked against the master instance during the login, however changing the password from a child instance pushes the password to the master.

By design, Flying Fleet doesn't pass other data that the base profile data. PPR, Customs or others cannot be handled from a child instance.