Users with developer permission have many different options available to configure operator mode, which are described in this section and the following ones. They can be accessed by going to any of the Settings tabs in operator mode, except for the session name, which is always visible.


When options are disabled, it is possible to hover over the option which will then show a tooltip with information about which other options are required, or which option is controlling the option.

Session name


The session name can be defined using the same template format as used for naming scans. With a template, users with operator or kiosk permissions will only be able to increment the sections. Otherwise, they will need to write the session name manually.


In addition to the standard template section types, there is also an extra section type available:

  • Field: These sections make it possible to use the value of a Field as part of the session name. They can be referred to by using $(<name>), where <name> is the exact name of an existing field. Note that if a field name contains closing parentheses, they need to be escaped using a backslash (\).
  • Environment: These sections make it possible to use system environment variables as part of the session name. They can be referred to by using $[<name>], where <name> is the exact name of an environment variable.


Session names need to be unique if any data is saved, but the user can get the option to overwrite existing sessions (always with operator and developer permissions, configurable for kiosk permissions). Overwriting will delete any data related to the session from the database and move any data on disk to trash.


If a session name has modifiable sections and a date time section, then the session may be unique because of the date time stamp, but the modifiable sections could be the same. In this case a warning will be shown in the output widget to point out that there are sessions with similar names.