Engine configuration

The Engine Configuration section of the Administration Portal holds instance-wide settings for the Querona engine — authentication, file export, logging, job history, job subsystems, logon tracking, the second factor, the Query Store, the security policy and low-level internals.

A saved change takes effect on the node it was saved on; the Requires restart? column of each page says whether that node has to be restarted first. The other nodes of a cluster keep the configuration they read when they started - the primary instance from the metabase, the others from the primary instance - so a change saved on the primary instance reaches the other nodes when they next start.

Setting group	What it covers
Entra Authentication settings	Microsoft Entra ID (Azure AD) integrated-login settings.
File export settings	Whether query results may be exported to files, and which engine writes Parquet.
Engine settings	Low-level engine settings, such as the server collation.
Job history settings	Retention and cleanup of job-execution history.
Job subsystems settings	What a job step’s subsystem may do, such as the folders KSeF synchronization may write into.
Logging settings	Engine logging levels and outputs.
Object usage settings	Which tables and views are read, written and have their statistics calculated.
Logon tracking settings	Which logins sign in, when they last did and how many attempts failed since.
Query Store settings	Query Store capture and retention settings.
Second factor settings	Whether a login that must have an authenticator is refused after a grace period, and how long the period is.
Security policy settings	Disabling accounts that have not signed in for a configured number of days.