What happens in the receiving station

In a receiving station, a user prototype must match the prototype name in the sending station.

The user prototype provides the Sync Strategy option and these local-override properties:

• Permissions (either a permissions matrix of local categories and rights or a Super User)

• Nav File (referencing a specific nav file under the local station's file structure)

• Web Profile (web-related properties)

When a network user is added or modified in a sending station, the receiving station uses its configuration of these two properties instead of those same properties in the source network user. You can configure prototypes for other local overrides.

This is what happens on the receiving side:

1. The subordinate station checks to see if Sync In Enabled of its proxy for the Supervisor station is set to true. If it is false, the subordinate station aborts the synchronization process.

2. The subordinate coordinates with the Supervisor to determine which users require synchronization.

3. The subordinate receives a list of out-of-sync user records from the Supervisor.

4. For each user, the subordinate station:

   • Finds a matching prototype among the User Prototypes. A prototype is either matched by name or, if Sync Strategy is set to Use Default Prototype, it uses the default prototype. If it finds no matching prototype, it ignores the user.

   • Overwrites the local override properties for the incoming user. These properties from the prototype include: Permissions, Nav File, and Web Profile.

   • Adds the new user or updates an existing user.

5. When complete, the station returns Sync Required to false and updates the synchronization timestamps.