User prototypes under a station’s UserService have the same properties as User components (see the section User for User property descriptions). The importance of user prototypes can be divided between the frozen “Default Prototype”, and any Additional (non-default) User Prototypes you add, for example by duplicating and renaming. Currently, non-default user prototypes are only used when synchronizing network users between different stations. In this case, (identically-named) prototypes in both the source station and receiving station can be used in a “sync strategy” of “Prototype Required.”

Note the alternative LDAP user services, for example LdapV3ADUserService or ActiveDirectoryUserService, also leverage user prototypes. When using one of these other user services (in place of the standard UserService), you also create user prototypes. However, operation differs from the “network user” usage under the UserService. For details refer to “Mapping of permissions and other preferences to LDAP users” in the NiagaraAX LDAP / Active Directory Configuration Guide.