Check user rights module
If the rights of the users are to be checked, the Check User Rights module must be present in the workflow (without the module no rights check takes place).

The module may occur only once in the workflow.

The placement of the module is not restricted. However, different effects result depending on at which points the module is used.

The module can be connected to all modules (this can result in nonsensical workflows).

Passed: This is the module that is executed if the check of the user rights is successful, i.e. all required rights are available for the user.
Rejected: This is the module that is to be executed if the user's rights are not sufficient to execute the print job. If this connection is not set, End module is executed automatically in this case. A useful option would be to route the print job to The Print Job List Module at this point (print@me jobs remain in the queue and direct prints are added to the queue).


Users can be notified by e-mail when printing a print job fails due to insufficient user rights. This is especially useful for direct printing.
Field | Description |
---|---|
Notification active | Specify whether or not to send an e-mail for this event. If this setting is not available, the notification cannot be deactivated. |
Type of notification | The e-mails can be sent in HTML or text format. In some places a message can also be sent as a push notification with IQ4docs Messenger, see also IQ4docs Messenger. The length of push notifications may be limited depending on the operating system. |
Recipient | Specify one or more e-mail addresses (separated by semicolons) to which the e-mail should be sent. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Sender | Specify an e-mail address to be used as the sender of the e-mail. This is also the address that is used when the recipient of the e-mail clicks on Reply in the e-mail program. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables; this can be useful for some events, since the user who has encountered the problem can be contacted by e-mail. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Language | Select the language in which the e-mails should be sent. |
Subject | Specify the desired text to be used as the e-mail subject. |
Message | Enter the desired message here. Depending on the type of notification, use plain text or HTML code here. If this field is not displayed, the text will be supplied in full from the message template. |
Send Test Notification sends a test message with the selected settings. For the test, the user data of the user who is currently logged in to the WebAdmin are used (if you make changes to the data of this user, you must log out and log in again in order for this data to be loaded). It might not be possible to resolve variables at this point because the workflow was not actually executed. When testing, also note the settings for the recipient and sender.
Load Defaults fills the fields for Recipient, Sender, Language and Subject with default settings - any values that may have been entered are replaced.


The print service accepts and analyses print jobs. It also checks the user rights when printing. It also sends the print data to the device. Its log file is Logs\PrintService.log.