The importance of properties in an additional (non-default) User Prototypes vary among stations that are either sending or receiving network users:
-
In a user-sending station (e.g. Supervisor) non-default user prototypes are important only in “name”, where you can simply duplicate the “Default Prototype” and rename each duplicate uniquely. Property values in these replicated prototypes are not used in any users—whether a user is local only to the Supervisor, or specified as a network user with this “Prototype Name.”
-
In a user-receiving station (e.g. JACE) non-default user prototypes are important both in “name”, where matching prototype names in “user sending” stations provide sync strategy options, and also (by default) in two “local override” properties, described below.
-
-
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)
-
When a network user is added or modified in a “user sending” station, the two properties above are used in the “user receiving” station, instead of those same properties in the source network user. Note prototypes are configurable for other local overrides—see Specifying additional “local override” properties.
In a “network user receiving” station (e.g. JACE) you can specify other properties of User Prototypes to act as “local overrides” for network users created in its station. This applies both to the single Default Prototype, as well as any additional (non-default) User Prototypes.
Do this from the slot sheet of the User Prototype: right-click the property, and select , as shown being done for the web_WebProfileConfig slot (Default Web Profile) in Figure 302.
In the Config Flags dialog, click the “User Defined 1” flag and click . Notice that in the slot sheet view, the “Flags” column now includes a “1” for that property, similar to the permissions and navFile slots. When a network user sync occurs for a user referencing this prototype, all properties with this flag use the local values as overrides.
If creating additional User Prototypes (apart from the “Default Prototype”), it is recommended that you name them using descriptive text that can be logically associated with groups of station users, such as AdminHvac, GenOperations, LtgAndAlarms, and so on. You pick from these names when adding a new user and selecting a “Prototype Name.”
Keep in mind that in a multi-station job, if you choose a network “sync strategy” based upon the “Prototype Required” scheme, network users in the “user sending” station are replicated/sync'ed in the “user receiving” stations only if the UserService in each remote station has an identically named user prototype. Note there is also an alternative “Use Default Prototype” sync strategy you can use instead.
For related details, refer to the “About Users sync strategy” section in the Drivers Guide.