Job subsystems settings

Job subsystems settings hold what a job step’s subsystem is allowed to do on this instance. Only the KSeF subsystem has settings today; see KSeF for what it does and how a step is written, and Jobs and Schedules for subsystems in general.

KSeF

Allowed folder roots lists the directories a KSeF step may synchronize into. A step naming a folder outside every root is refused when the step is created, and the message lists the roots that were allowed — so a job step cannot become the ability to write anywhere the Querona service account can reach.

Warning

At least one root is required. There is no built-in default: until an administrator adds a root here, no KSeF job step can be created or run, and both are refused with a message saying so. That is deliberate — a default would decide on your behalf where an external system’s invoices are written.

The first root in the list is where a step that names a company rather than a folder puts it.

Containment is checked on the resolved path rather than on the text, so a name that slips past the syntax checks still cannot escape, and a root is not a prefix match: D:\KsefDataOther is not inside D:\KsefData.

What Querona does and does not create

Querona creates neither the roots nor the company folders beneath them. Both hold an external system’s data under the retention, backup and access rules you arrange for it, and creating either automatically would silently accept a typo and start filling a directory nobody chose. A step whose root or company folder is missing fails with a message naming the path, so the fix is to create it rather than to guess.

Every node runs the same configuration, so each root — and each company folder — has to exist on every node, with write access for the Querona service account.