In this settings section the administrator specifies various settings affecting users, specifically:
Default settings for new users
Newly created user’s account will have the following default settings:
User permissions
Default permissions, that will be granted to newly created users. For descriptions of the permissions, see User permissions.
Appearance
User name display
Changes the display of the user's name on the main application bar (on the top right). Available options:
Username (default) - this is what was shown before this setting was introduced
E-mail
First-name Last-name
Last-name First-name
Disable inactive users
Sets the automatic inactive user account disable function. The action is performed once a day. Disabling an account means revoking user’s login permissionremoving the active account setting, see Add user. The administrator can enable the user’s account again by granting him the login permission backediting the account and setting it as active. But if such user will not log in and therefore will stay inactivenot perform any acitivity, his account will likely be automatically locked again.
...
The number of days, after which a user account is considered inactive and will have login permission revokedactive account setting disabled.
(1-36500, default: 180)
Simulation
The SIMULATION button allows for a dry run of the operation without executing the actual action, displaying a preview of the list of accounts that would be affected by the actual execution of the operation.
Below the list displayed in the simulation, there is also a button available that allows for the immediate execution of the actual action, thus locking the accounts mentioned.
Delete inactive users
Sets the automatic inactive user account delete function. The action is performed once a day. Deleted accounts cannot be restored, but can be created as new again.
...
The number of days, after which a user account is considered inactive and will be deleted.
(1-36500, default: 365)
Simulation
The SIMULATION button allows for a dry run of the operation without executing the actual action, displaying a preview of the list of accounts that would be affected by the actual execution of the operation.
Below the list displayed in the simulation, there is also a button available that allows for the immediate execution of the actual action, thus deleting the accounts mentioned.
Multifactor authentication
...
If enabled, it will be forbidden to send a package without login (anonymously) from the the specified IP address ranges.
(default: disabled)
Settings for sent packages
Users can send packages without approval
...
Access detailed results of file checks
Logged in users
Specifies whether logged-in registered users have access to detailed file check results, including sandbox reports. (just like the administrator)
In the case when "only selected" is set, the permission of each user comes into account.
(default: YESNO)
Allow access to packages being approved without requiring their password
If enabled, the auditor (user with permission to approve packages to be sent) does not need to know and enter the download password for the package being approved to access the package's detail and contents. Does not apply to packages encrypted with the package password, because these cannot be decrypted without it
Anonymous users
Specifies whether anonymous users have access to detailed file check results, including sandbox reports. (just like the administrator)
(default: disabled)
User Login
Allow direct user login
Allows users to log in using a form directly in the SOFiE application. If disabled, the login form with username and password is hidden, and login is only possible via an external portal (ADFS or OIDC).
(default: disabledenabled)