As the name implies, UserActions describe the actions an administrator (the project manager of a customer site) is allowed to do. Most of the time a site will have more administrators, who will have been assigned different responsibilities and therefore different administrators will be allowed to do different actions.


For a description of the several UserActions see below. Every user action has a label. The developer is free to fill in his or her own text.
Many 'UserActions' have a field 'DisallowedFor'. This field determines whether a specified administrator has the right to execute the action. If disallowed, the action will not be displayed when the specified administrator is logged on to the system. (More administrators may be added.) If relevant, 'EnabledWhen' specifies a logical condition for when this action can be executed. A point in case would be a logical expression to prevent an e-mail to be sent twice.

AdminHomeWhen clicked upon, the screen jumps to the first screen of the manager site.
UserAddTo add a new user. When clicked upon, a questionnaire is opened to define the new user.
UserCopySometimes many new users have to be added who have a number of properties in common. If so, it is useful to first add a 'dummy user' with all the common properties filled in. This dummy user can be used as the source for UserCopy to create new users. These new users will have all their properties already filled in, and the only thing left to do is to fill in the identifying properties like name and so on.
UserRemoveTo delete a checked user.
UserMailTo send a predefined mail to the user. Can be used to send an invitation to fill in questionnaires. The mail can be personalized by the use of properties. For an explanation of ParameterSubstitution follow the link. When useful more UserMails can be added.
UserReportTo create a user report from the contents of the user profile. More user reports may be added. (E.g. a score report for the professional and an explanatory report for the user (client).
UserGroupReportTo produce a report on the data of a collection of users. E.g. used for presenting mean scores, etc.
UserProcessorThe actions specified in the referenced ContentComponents (respectively 'Header' and 'Processor') will be excuted on the checked users.
UserListFilterDetermines which users will be displayed. E.g. as the label would be 'Female', the expression might be 'sex == 2', when property 'sex' has value 2 for females. When clicked upon this filter button, only female users would be shown.