Modules extend the core functionality of the application. Disabling a module hides the relevant sections and features throughout the application.
Protection against password guessing. After the configured number of wrong passwords, the account is temporarily locked. The user sees a message with a countdown on the sign-in page showing when they can try again, and receives an e-mail about the lock. This setting is independent of the password policy - lockout can be enabled without enforcing password complexity. For a detailed description, see Lockout after failed sign-in attempts.
This feature is enabled by default. Lockout does not apply to users signing in via SSO, users in API roles (so an integration with an outdated password cannot lock its account), super administrators and system accounts. Administrators with the System settings permission can be locked.
This section controls the visibility of the My Company module in the application's left menu. If both options below are disabled, the My Company menu item will not appear.
Reduces the security risk of long-unused accounts. If a user does not sign in for the configured number of days, the system blocks their account automatically (sets access denied). The check runs once a day at night. For a detailed description, see Automatic blocking of inactive accounts.
This feature is disabled by default. Automatic blocking never applies to system administrators (users with the System settings permission), users signing in via SSO / external authentication and API/service accounts.
A blocked account is unblocked manually by an administrator on the user detail (by removing access denied). After unblocking, the account will not be blocked again until the full inactivity threshold has elapsed.