Introduction

Purpose and audience

This guide describes the system administration of Docuflair Redact & Mask through the web interface. It is aimed at system administrators — the people who operate the installation as a whole: setting up tenants, applying licences, maintaining installation-wide settings, configuring PII detection and managing demo mode.

Docuflair Redact & Mask is an audit-proof document management system focused on redaction (Redact) and pseudonymisation (Mask). The installation is multi-tenant: every tenant (a law firm, a department or a customer, for instance) gets its own, completely separate database and its own data area.

Note

The system administrator manages the installation but has no direct insight into the content (documents, projects, files) of the individual tenants. Administration inside a tenant — users, permissions, redaction dictionaries, projects — is the job of the tenant administrator and is described in a guide of its own.

The role model at a glance

Role	Signs in with	Area of responsibility
System administrator	The tenant code system	Tenants, licences, system settings, PII word lists, API keys, proxy, demo mode, auditing
Tenant administrator (superadmin)	Their own tenant’s code	Users, groups, permissions, projects, the tenant’s redaction dictionaries
User	Their own tenant’s code	Day-to-day work with documents, redaction, search

Conventions in this guide

• Bold denotes visible elements of the interface (buttons, menu entries, field labels), for example “New tenant”.
• Monospace denotes technical identifiers: URLs, configuration keys, file names and example values, for example /system/tenants.
• Callout boxes (like the one above) contain important additional information, warnings or practical tips.
• The examples use the fictitious tenant “Muster GmbH” with the code muster-gmbh.

A note on technical identifiers

For historical reasons, some internal identifiers (database file names, configuration keys such as Velkaris:Jwt:Secret, the prefixes of API keys) carry a different internal product name. This guide reproduces those identifiers exactly as they appear in the system, so that you can find them again in configuration files and logs.