Security-classification on physical output

[paulvandenbraken]

Could have for Kennisnet phase: Epic-3

Detailed description

Physical output (ie. printed reports/documentation) is labeled with a visible printed security-class.

Feature benefit / User story

As an employee, I want to directly see the physical report's classification so that I can follow my company's policies and take appropriate measures.

Refinement input:
Kennisnet uses classifications "Geheim" (Secret) or "Vertrouwelijk" (Confidential). We suggest to have (by the administrator) selectable classes for flexibility-reasons so that individual businesses can select and print their own defined class, amongst others "Vertrouwelijk' and "Geheim" for Kennisnet.

[underdarknl]

I think this is reasonable, however, we should as @paulvandenbraken suggests make this class configurable (per report possibly), and maybe also make the leading added page configurable (it could just be an html file the user can host somewhere).

[underdarknl]

as discussed:
Two env vars,
One pointing to an optional html file.
One containing an optional footer text to be added to each page.

Combine this with the also open issue about the env-var to include (or not) the report url pointing to the openkat install that generated this report.

[underdarknl]

use @media:print css styling to show these blocks, hide them in the online view.

[underdarknl]

Edward suggests storing these settings in the organisation settings table instead of in env-vars, this would allow for separate messages and choices per orga.