Default Prototype

Among User Prototypes, the “Default Prototype” is important in any station with any user service, as it is always the default source of User property values whenever you use the service’s User Manager view to add a New user to the station.

Figure 301. Default Prototype of the UserService’s Default Prototypes is source of default user properties


Default Prototype of the UserService’s Default Prototypes is source of default user properties

In this regard, all of the Default Prototype properties can be considered important—with one exception: password—which is not copied up to a new user created in the User Manager.

However, all other property values (except password) in the Default Prototype are used as “defaults” when you create any new user in the User Manager. This can be useful, for example, if you have some (minimum) collection of permissions for all users, or a typical Nav file, and so on.

NoteStarting in AX-3.7, User Prototypes have a child “Password Configuration” container, just like User components. Inside are two properties as follows:

For more details on the operation and configuration of these two properties, see About password expiration and reset.

Default Prototype importance in Network users scenario

Additionally, in a multi-station job where you are using “Network users”, the user “sync strategy” of “Use Default Prototype,” the default prototype (in each station receiving network users) specifies the “local properties” that override the received properties of any network user. Note that by default only 2 properties are “local override” types: Permissions, and Nav File.

However, by going to the slot sheet of the Default Prototype (in each station receiving network users), and setting the “user defined 1” config flag, you can specify additional properties as “local override” types. You can also use this same technique with other (non-default) User Prototypes in stations that receive network users. For details, see Specifying additional “local override” properties.