1 The concept: registers instead of rigid forms
A register is a freely definable table. You decide the fields — Floriti automatically builds entry forms, list views, exports, reports and interfaces from them.
The core of Floriti is deliberately not preconfigured: there are no hard-wired screens. Instead you create registers (e.g. “Processing activities”, “Assets”, “Risks”, “Customers”) and define each register's fields with type, mandatory flag, order and logic. Everything else — form, table, search, export, report — emerges automatically.
Any number of registers, any fields — extendable at any time, no programming required.
Registers reference each other (link fields, matrices, VLOOKUP formulas).
Roles, areas, approvals and the audit log keep data clean and traceable.
Even registers with several 100,000 entries stay fast — lists, import and export are built for it.
2 Creating & managing registers
Under Administration → Registers you create registers and maintain their fields in the register editor.
The register editor
At the top, the register name is shown in large type, with four tabs below it: Fields (count), Settings, Links (count) and Workflows (count). Existing registers open on the fields – so you can concentrate on the questionnaire and bring in extra features only when you need them. Everything is saved together via the bar at the bottom of the window (workflows save themselves). A new register starts under Settings › Basics, because name and area are mandatory; then carry on with “Continue to fields”.
“Fields” tab
- Field cards: label, type and explanatory text (rich text, shown as guidance under the field) are always visible; change the order with the arrows and add new fields with “+ Insert field here”.
- Expand as needed: Input hint (grey text in the empty field that disappears when typing) and Default value expand via ▸; if a value is stored, “set” appears next to it.
- “▸ Field settings”: required field, primary key (for import matching), “Field must be answered”, visibility on public pages, “Hide in form” (for silent formulas), read only, field buttons, deadline traffic light, colour coding and ✨ AI hint. When collapsed, the bar shows which of these are active (e.g. “· Required field · Primary key”). Information texts and dividers have no field settings.
- Condition: “Show only when condition is met” stays directly visible – see chapter 9.
- “▸ Fields from linked registers”: shows values from linked entries (e.g. the address of the selected customer). Without a link, the box explains how to get to the “Links” tab.
- Deleted fields (archive) are at the very bottom – see chapter 27.
“Settings” tab
A menu on the left, the selected category on the right. The menu shows the status at a glance (e.g. “on”, “off”, “5/5”); active extra features also appear as green hints next to the tabs and take you to the setting with one click.
- Basics: name, description, section (groups registers in the sidebar), display field (which value represents an entry, e.g. in link lists) and default editor (user or 👥 group).
- Visibility: “Who should see this register?” (areas), “Reachable via links only (not in menu)” and “Master data: maintained by admins only” – details below.
- Form: “Number chapters and fields” (1.1), Field in header and the features in the form.
- AI: “✨ Offer AI form assistant in the questionnaire” and the AI provider for this register.
- Approval: approval workflow and approvers – see chapter 10.
- Sharing and public: invitations by link (with protection), public form, public list view and design – see chapter 7.
- PDF templates: see chapter 25.
- Features in the form (Settings › Form): review reminders and four more switches, all on by default — 💬 entry comment section (general comments at the top of the questionnaire) and the buttons next to each field: 💬 comment, 🕐 change history and 📎 attachment. When off, the register no longer offers the feature; comments, attachments and history already saved are kept. With the register switch on, each field button can also be turned off for individual fields in the field card under “Field settings › Field buttons”.
- Invitations with master data: The following settings appear under Settings › Sharing and public once “Invitations by link” is ticked there. Under “Secure invitation links” you protect invitations with an access code or a security question (compared with a field of the prefilled entry, e.g. the postcode). Inviting from an existing entry updates exactly that entry: reviewed answers flow back into the entry the invitation was sent from after approval (without approval: immediately) – no second entry is created. The approval view shows “Current” and “New” for each field; under “Then set” a field can optionally be set (e.g. Status = Done). In the approval view, “Query to submitter” sends a new link with the previous answers and your question. An email sending field can send the link itself with the placeholder
{{#einladung}}, and the database sync fetches the master data for existing entries only with “Only enrich existing entries” – if desired, right when an entry is saved. - Access code in the entry: With an access code, the email sending field also sends the invitation automatically. The mail contains only the link and a note that the code follows separately, never the code itself. In the entry, the “Invitation” box shows recipient, status (open, completed, expired) and date. Anyone who may edit the register or send invitations retrieves the code for 60 seconds via “🔑 Show code”, e.g. to pass it on by letter or phone; every retrieval is recorded with name and time in the entry history. Readers see the box without the code. Only the code of the latest invitation is valid: sending again or a query back creates a new code and the old one expires. When typing, the invitation page inserts the hyphen automatically.
“Links” tab
- Existing links: all linked registers, back-links and fields from linked registers, with target register and direction (“↔ both directions” or “→ this direction only”); “Go to field” jumps to the field card. Links not yet saved are marked “new”.
- Add links: tick several registers at once and set the field name, multiple selection and “both directions” for each. The “Add … link(s)” button sits in the save bar; if you ticked registers but did not add them, you are reminded when saving.
“Workflows” tab
The register’s workflows – right in the editor, without changing pages. Structure and operation: chapter 11.
Illustration: register editor with tabs, green hint on active features and collapsed field sections.
Handy management features
“Structure only” or “structure incl. content” — ideal for templates and variants.
Export registers as JSON and import them into other instances — renamable on import.
Save the entire configuration (registers, entries, rules, workflows) as a template and restore it in any instance.
Restore or permanently delete removed entries per register — incl. “empty trash”.
The register list has a search (name, description, section, area) and shows each register's assigned areas as badges — so it's immediately clear who can see it.
Deleted fields keep their values and can be restored with their content — see chapter 27.
🔒 Read only & master data
- Field option “Read only”: The field appears in the form with its value and a 🔒 – it cannot be changed there. Values are set only by workflows, rules and admins (e.g. status, traffic lights or details taken over from another register). Admins open the field with ✎ when needed and close it again with 🔒.
- Register option “Master data: maintained by admins only”: Everyone with read access sees the entries and can select them in links; only admins may create, change or delete them. Ideal for catalogues such as AI models, countries or locations. Anyone who tries anyway is told why.
- Register option “Reachable via links only (not in menu)”: Users do not see the register in the sidebar, on the start page, in “My Floriti” or in search – they only select its entries in link fields. This keeps helper and catalogue registers out of sight. Admins still see it, marked “not in menu”. Not access protection: anyone with read access can still open it via a link.
- Field in header: The value of a chosen field is shown with its colour coding in the header of form and view – e.g. the “Result” of a review or the “Status” of a risk.
3 All field types at a glance
Field types are the building blocks of every register — from simple text to linked registers and calculated formulas.
| Field type | Description & specials |
|---|---|
| Text / Text area | Single/multi-line input. With input hint, default value and explanatory text. |
| Number | Numeric input — also usable in formulas. |
| Date | Date picker; usable in formulas, e.g. for deadline calculations. |
| Timestamp | Date with time (e.g. “Detected on 06/10/2026, 14:30”) — for deadlines in hours, completion times and automatic stamps via NOW(). |
| Input with e-mail format. | |
| 👤 Assignee | Person or group: a user's email address, a group name or an external email address — with suggestions while typing. Ideal as the source for conditional workflow assignment (see chapter 11). |
| ✉️ Send e-mail | Sends e-mails straight from the entry: recipients, subject and text with {{placeholders}}, optionally with attachments, password protection and an automatic trigger. The field value is the date of the last sending (see Chapter 26). |
| Select | Dropdown with fixed options. Optional: multi-select or rendering as buttons (with adjustable width) — great for workflow triggers. |
| Checkbox | Yes/no. Often a control field for conditions (“Other partners? → extra fields appear”). |
| Formula | Calculated field: expression over other fields, with IF, arithmetic and VLOOKUP/LINKED into linked registers. Optionally “hidden in form” (silent calculation), still shown in the register list on demand. |
| Link | Reference to entries of another register — as dropdown, list or with server-side search (fast even at 400k+ entries). Optional: multi-select, “create new” right from the form, filters (offer only matching target entries, AND/OR rules) and a default entry. |
| Matrix | Embeds a matrix register as a clickable grid inside the form (see chapter 4). |
| Direct link | Jump link to a specific entry of any register. |
| Info text | Display-only block (rich text) in the form — explanations, legal notes, instructions. Not counted as a question. |
| Divider | Section heading; structures the form into chapters and feeds the chapter navigation. |
| Area visibility | Controls which areas can see an entry. |
4 Matrix registers
A matrix combines two registers into a clickable grid: X axis from register A, Y axis from register B, assignment by clicking a cell.
Typical uses: risk matrix (likelihood × impact), data subjects × data categories (GDPR), competence matrices. Matrix registers appear as their own menu item and can additionally be embedded as a matrix field in forms — each entry then stores its own cell selection.
- Colour grading: cells automatically coloured green/yellow/red — incl. manual override of individual cells (“this risk is red regardless of its position”).
- Section: matrices can be grouped into sidebar sections like registers.
- Enlarged view: the matrix field of an entry can be opened in its own full view.
🎯 Tailoring matrix fields in questionnaires
When you embed a matrix as a matrix field, the register editor lets you define what the questionnaire offers:
- Value and group field: In the matrix definition (Administration → Matrix) you choose, per axis, which field labels the rows or columns and, optionally, a group field of type dropdown (multiple selection works too). The group is then shown next to every row and column.
- Offered rows & columns: Offer only the relevant entries; whole groups can be switched on and off with one click.
- Allowed combinations: Exclude individual combinations that make no sense (hatched). Clicking a column or row header marks it; the group buttons then apply only to the marked columns or rows, e.g. “Master data” only for “Customers”.
- Excel template & import: Download the selection as a matrix (x = offered), edit it and import it again, which is handy when migrating from legacy systems. Matching is done by label. A preview shows names that do not match, suggests similar ones, lets you assign or ignore them and can swap rows and columns. Nothing changes until you click “Apply”; it takes effect when the register is saved.
Illustration: matrix with colour grading and clicked assignments.
5 Entering & maintaining data
Four ways lead to data: direct entry, questionnaires, public forms and the AI form assistant. This chapter covers working directly in the register.
The register list (table)
- Server-side pagination: even huge registers (tested with 400,000+ entries) load in milliseconds.
- Filtering: per field with operators (equals, not equals, contains, filled/empty, greater/less) — including a filter on the entry ID (e.g. “everything above ID 400”).
- Sorting by columns or manual ordering (custom sequence by moving entries).
- Bulk actions: edit or delete filtered entries collectively — set-based, even with tens of thousands of matches.
- Status colours: approved, pending, rejected, draft are colour-coded.
- Saved filter views: name and save a combination of filters, sorting and columns — as Mine or shared with the Team. One click restores the view (more in Chapter 19).
The entry form
- Chapter navigation: dividers create a chapter menu listing every question — in edit and view mode; clicking jumps to the question.
- Progress bar: counts only real input fields (no dividers, info texts or formulas) and only genuinely answered values. Plus a question filter “all / unanswered / mandatory / open mandatory”.
- Full-screen mode (⛶) for focused work — the AI assistant stays available.
- Field comments (💬) and file attachments (📎) directly on a field, plus attachments on the entry.
- Comment thread on the entry (💬): one discussion thread per record — notes, questions and agreements stay right with the entry (with author and time, editable and deletable).
- Drafts: save intermediate states before requesting approval — drafts are visible only to their author.
- History: every change is traceable in the entry history and the central audit log (who, when, what — incl. field authors in collaborative editing).
- Invite additional editors: let colleagues or externals work on an entry via an e-mail link (no login required, token-secured).
- Quick access: mark entries and registers as a ⭐ favourite, 👁 watch them and give them an ⏰ review date — details in Chapter 19 and Chapter 20.
Tidied header & audit columns
- ⋮ menu: copy form link, Excel/CSV/PDF export, audit report, import, “recalculate formulas”, recycle bin, reorder mode and “create report” are bundled in one menu — the header keeps only “Create assignment” and “New entry”.
- Search button & filter chip: search right inside the register view; active filters appear as a chip above the table.
- Audit columns: creator, contributors, “approved by” and “approved on” as switchable columns — also available in reports (chapter 13).
- Remembered column order: columns arranged via drag & drop stay saved per register and user.
- Pinning: every entry can be “pinned to My Floriti” in edit mode — as its own watcher tile on the start page (chapter 19).
Helpful when filling in
- Messages with jump links: If a message names fields (e.g. “Please fill in first: …” or a missing required field), the field names are clickable – one click jumps straight to the field.
- Clear reasons: If the server is briefly unavailable (e.g. during an update) or an action is rejected, Floriti tells you why – and that your input has not been saved yet.
- Your view is kept: The view you last selected for a register – including your own sorting – is active again when you return to the register later.
6 Questionnaires: the same data, asked in a tailored way
A questionnaire is an alternative view of a register: a selection of fields, rephrased as questions — without duplicating the data structure.
- Field selection: a questionnaire contains a subset of the register fields in its own order.
- Overrides: per field its own label (“Which data do you process?” instead of “Data categories”), its own explanatory text and its own mandatory setting — only for this questionnaire.
- Info blocks & dividers: additional display blocks that appear only in the questionnaire (introductions, legal texts, chapters).
- Usage: questionnaires are attached to work assignments and invitations — different audiences get different views of the same register.
Questionnaire-workflow dynamics
Questionnaires, conditions and workflows interlock:
This creates a guided process: people answer only what concerns them; as soon as e.g. “incident reported” is selected, the workflow jumps to the next step, assigns the responsible group and notifies it — details in chapter 11.
7 Public forms & public views
Registers can be opened to the outside — for capturing (form) or reading (view). Entirely without a user account.
Public form
- Its own friendly URL (freely chosen slug), shareable via link or QR code.
- Invisible bot protection against automated submissions — no puzzles or captchas for your submitters.
- Optional file attachments by submitters (via a switch on the register).
- Language selection right on the form — translations come from the register translations (chapter 17).
- Conditions and default values work like in the internal form; submissions land regularly in the register (optionally through the approval process).
Public view
- Read-only list of a register under its own URL — e.g. a public directory or status overview.
- Controllable per field whether it is publicly visible (“show in public view”).
Company look
- Form and view carry your company's logo, instance name and colours (Admin → Translation & branding), including the browser tab title and icon.
- The footer shows your address, legal notice and privacy policy, optionally also a contact email and accessibility statement. Enter them under “Public forms & read-only views”; clicking the logo leads to your website.
- Shared links show title, description and company logo in messengers and email programs.
- If a company colour is too light for white text, Floriti switches to dark text automatically. Logos are only loaded from your own server — public pages make no connections to third parties.
Page designs
- Under Admin → Page designs you shape the look of public pages: layout (classic, banner, split, minimal), colours, background, images, fonts, corners, shadows, spacing and your own thank-you page — with a live preview of form, thank-you page and read-only view on desktop and phone.
- A design applies to every register you assign it to (register editor → Settings › Sharing and public → “Design of public pages”). Change it and all assigned forms change immediately.
- “Take over from website” reads colours, font and key image from your company website.
- Images are resized automatically, stored without metadata and count towards your storage quota. Fonts are hosted on the Floriti server. Structure transfer and demo snapshot carry designs including images.
- Custom page designs are available from the Starter plan.
- Translate banner title, banner text and thank-you texts under Admin → Register translations (automatic translation available); visitors see them in their chosen language.
Own address & embedding
- Embedding: in the register editor, under Settings › Sharing and public → “Design of public pages”, you'll find ready-made embed code for your website; the height adjusts automatically. It only works on websites you list in the design under “Embedding allowed on” — no other site can embed your form.
- Own address (Full plan): under Admin → Branding enter e.g.
forms.company.comand create a CNAME record at your domain provider. Floriti checks it automatically and obtains the SSL certificate. Only the public pages are reachable under your own domain; its home page redirects to your website. - Also in the Full plan: your own font file (WOFF2, house font) and hiding “Powered by Floriti”.
8 ✨ AI form assistant & AI analysis
The AI reads documents and fills questionnaires — as a chat assistant right inside the form, or as an analysis tool for whole documents.
The chat assistant in the questionnaire
When a questionnaire opens, the assistant (✨ button bottom right, with a friendly speech bubble) offers its help:
- Hand over documents: via the 📎 button or drag & drop — even several at once (PDF, Word, text, Markdown, CSV). Or simply describe the case in your own words.
- Automatic filling: the AI extracts values for the still-empty fields — it never overwrites an existing value and never guesses: if information is missing, the field stays empty and the assistant asks a targeted question.
- Understands the form logic: fields hidden by conditions do not exist for the AI. If an answer activates new fields (e.g. “DPA in place” → contract partner), the assistant immediately reports them as open items.
- Links included: if the AI recognises e.g. an asset name, it links the existing entry — or offers, with one click, to create the asset.
- A dialogue with memory: the chat history is preserved; questions and answers build on each other. At the end the assistant summarises: what was filled, what is open, which documents would still help — plus filling tips.
Illustration: form with progress and AI chat — documents via drag & drop, follow-up questions in dialogue.
More AI tools
Upload whole documents — the AI proposes finished register entries; you review and adopt them (optionally with a review assignment for a colleague). All created entries receive a tag so you can find them again.
The AI analyses which fields are frequently empty and recommends which documents (contracts, concepts, lists) would fill them.
AI included in your plan — a monthly included quota with a warning before it is reached; activation is an admin decision, and AI can be switched off per register via the ✨ toggle. Your data is not used for AI training.
The AI gets to know your company
Four building blocks make the AI company-specific — without any model training and fully under your control:
Upload company documents (policies, templates, concepts) as a knowledge source — for the entire workspace or targeted per register. The AI pulls the most relevant sections into its answers and names the sources (“company knowledge used”). Indexing happens directly on the server — your knowledge base never leaves it. The test search shows which passages are found for a question.
In the register editor you store binding rules for the AI per field: expected format, scope versus other fields, desired inferences (e.g. “country outside EU/EEA ⇒ third country = Yes”). Users never see these hints — the AI treats them as a mandatory checklist that outranks everything else.
Floriti automatically records whether AI suggestions were accepted, corrected or discarded — per field, with examples (AI value → final value). Fields with a weak rate are listed first: the candidates for an AI hint, with a direct link into the register editor.
Fixed test cases (material text + expected field values — also via drag & drop from files) safeguard AI quality permanently: a test run checks all cases against the current AI and shows the hit rate plus the change versus the previous run (▲/▼).
Assistant refinements
- Conflict notices: if a document yields a different value than an already filled field, the AI never overwrites — it shows the conflict and you decide with one click: replace, combine both, or keep. Confirmation suggestions state their reasoning.
- ✨ marking that expires: AI-filled fields are marked; edit a marked field manually and exactly that marking disappears — the value then counts as yours.
- Movable chat window: drag, resize, reading zoom — and push it mostly off-screen when needed so the questionnaire stays visible.
- Read the knowledge base: every stored document has a “Read” button — it shows the extracted text in sections, i.e. exactly what the AI sees when searching.
AI administration: who, with what, how much
- Activation (opt-in): in paid plans the AI features start deactivated — an admin deliberately enables them on the AI info page (the decision is logged); only when the AI is used are the selected texts sent to the AI provider. In demo workspaces the AI is active from the start for trying things out and can be switched off at any time.
- AI switch & AI info: a dedicated admin page shows the current AI configuration and the data flow (what is transmitted, what always stays in-house) at a glance; AI can be switched off entirely per instance.
- “AI usage” role: the admin controls which users can see and use the AI features (chapter 15).
- Monthly quotas per plan as cost protection — with a warning before the quota is reached. Usage is counted in AI points: a document analysis costs 10 points, the form assistant and document suggestions 1 point each (Demo 50 · Starter 1,000 · Full 3,000 points per month).
- Your own AI connection: instead of the built-in AI you can store your own Anthropic key (BYOK) or your own OpenAI-compatible AI endpoint (e.g. EU-hosted or on-premise) — quotas then don’t apply.
- Monitored availability: The built-in AI is monitored around the clock — if there is a disruption, the Floriti team is notified automatically and takes care of it.
9 Conditions & formulas
Forms that think along: fields appear only when relevant — and values calculate themselves.
Visibility conditions
- Every field can depend on one or several other fields — combined with AND or OR, also as nested groups (e.g. “X AND (Y OR Z)”, up to three levels).
- 18 operators in five families — the editor offers only those that fit the field type:
- Basics: = equals ≠ not equals is filled is empty
- Comparison (number & date): > greater than ≥ greater or equal < less than ≤ less or equal
- Text: contains does not contain starts with ends with
- Lists (multi-select & links): any of these is selected all of these are selected none of these is selected not all of these are selected
- Visibility: question is shown question is not shown — refers to an earlier question
- Conditions behave identically everywhere: in the form, the questionnaire, the public form, the approver view — and in the AI form assistant.
- Cascades are possible: field C depends on B, B on A.
Formula fields
- Expressions over field values in square brackets: [Price] * [Quantity]
- Case logic: IF([Location] = "DE", "domestic", "abroad")
- Pull values from linked registers: VLOOKUP / LINKED — e.g. the risk class of the linked asset.
- Formulas calculate live in the form and are stored server-side; “recalculate formulas” refreshes existing data.
- Silent formulas: “hide in form” + optionally “show in register list” — ideal for scores and traffic lights.
Date & time in formulas
- TODAY() today's date · NOW() date and time · CREATED() creation time of the entry.
- ADDHOURS([Detected on], 72) adds real hours — correct even across daylight-saving changes.
- EDATE([Date], 1) adds calendar months; if the day does not exist in the target month, the last day of the month is used (31 Jan + 1 month = 28/29 Feb).
- DATEDIF([From], [To], "D") days (or "M" months, "Y" years) between two dates; YEAR / MONTH / DAY split a date.
- All times refer to German time (Europe/Berlin).
Order & formula checker
- A formula may refer to any field of the register — including fields further down and other formulas. Floriti calculates formulas in the order of their dependencies.
- The formula checker in the register editor reports unknown fields and functions (with a suggested fix), wrong arguments and circular references (A refers to B, B to A) while you type. A circular reference results in “#FEHLER: Zirkelbezug”.
Deadline traffic light
Every regular field can carry a deadline with traffic light. The light is evaluated live against the current time — even without saving again.
- Due date from field: the field itself, any date, timestamp or formula field, or the entry's Created or Modified time — each with an offset “+ X hours” (e.g. Created + 72 h; Modified + 24 h for entries left lying). Simple deadlines therefore need no separate formula field.
- If the traffic light sits on a field other than the due date (e.g. on “Status”), the register list and entry view show that field's value with the light next to it; the calculated due date appears in the tooltip.
- Warning stages can be defined freely: “time left ≤ X hours → colour” (green, yellow, orange, red). Above all stages the light is green, once overdue it is red; red can also start before the deadline.
- Done field: as soon as the chosen field is filled in, the light shows ✓ instead of the time left.
- Shown with the time left (“5 h 20 min left”, “overdue by 2 h”) in the register list and entry view; a plain date is due at the end of that day.
10 Approval process
Four-eyes principle per register: entries only take effect once approvers have released them.
- Approver pool: per register users and/or 👥 groups as approvers, with a default preselection. For groups, “one is enough” — any member can fulfil the slot.
- Multi-approver: several approvers per entry (“all must agree”), including override and a record of who decided for a group.
- Flow: editor saves a draft → “request approval” → approvers review in their own view (with progress and all answers) → approve or reject with a reason.
- Queries: approvers ask questions directly on individual fields; the editor answers and, via the 🔔 notification (“Reply”), lands directly in edit mode at the question concerned. Questions can be closed, the thread remains.
- Entry-specific approvers: individual entries can have deviating approvers.
- Status colours in all lists: approved · pending · rejected · draft.
11 Workflows: multi-stage processes
Workflows guide entries through defined steps — with automatic assignments, notifications and custom continue buttons.
- Steps: a workflow belongs to a register and consists of ordered steps (e.g. “Report → Assessment → Measures → Closure”).
- Triggers: a step starts when a field receives a certain value (e.g. select buttons “Status = Assessment”) — or via the continue button.
- Assignment: per step an editor group — members see the entry as a task.
- Notifications: notify groups per step, with a custom message (🔔 bell + e-mail).
- Forward/backward buttons: label freely configurable per step (“Hand over to business unit” instead of “Next”); going back is possible.
- Transparency: the workflow display in the entry shows the current step; every trigger is logged with user, time and value.
- Field updates per button: a step can set fields automatically when its continue button is clicked — with a fixed value or a formula, e.g. “Notification sent on” = NOW(). The change appears in the entry history.
Illustration: workflow display with active step, group assignment and configurable continue button.
The workflow editor
You edit workflows in the register editor on the “Workflows (count)” tab. The list shows each workflow’s status and number of steps; JSON and Excel export are in the ⋯ menu.
- Timeline at the top: all steps as numbered circles, as in the entry. A click jumps to the step and opens it.
- Collapsed steps: each step is one line – “Step 2: Assessment”, the trigger (“when Status = Assessment”) and a short summary (editor, continue button, step back, notifications). A click opens it; only one step is open at a time.
- Start and end follow from the position: the first step is the start, the last one the end. Insert new steps between two steps with “+ Insert step here” (appears on hover).
- In the opened step: step name, trigger field and triggering value are visible; everything else sits in four expandable groups with a summary: Next button (label, comment, “Continue only when answers are complete”, set fields), Responsibility and notification (editor, conditional assignment, notifications, recipient selection, message), Step back and Advanced (conditional display, locked fields, timeline, dormant sub-tasks, linked entry).
- Applicability condition of the workflow: collapsible at the top, with the summary “always applies” or “only under a condition”.
Branching, jumping back, travelling along
- Workflow condition: several workflows per register — a register field decides which one runs (e.g. “report type = data breach” starts the breach workflow).
- Defined back jumps: per step its own back button with a fixed target step and selectable comment requirement; back paths actually taken are drawn as arcs above the timeline.
- Travels along: with “Transfer building blocks”, workflows travel to the target instance including steps and assignments (resolved via username/group name).
- Self-reporting: if a step’s trigger field no longer exists (e.g. after a structure change), the workflow editor warns right at the affected step.
Who works on it? Conditional assignment, take over, email recipients
- Conditional assignment: Any number of rules per step: “If [condition], then editor = …” — a group, a user, the value of a field in the entry or a lookup in another register (e.g. register “Responsibilities”: location → responsible). Rules are checked from top to bottom, the first match wins; if none matches, the step’s fixed editor applies.
- Field type “Assignee”: contains a user’s email address or a group name. An external address without a user account only receives the info email, not a task.
- Reassignment: If a deciding field changes while the step is running, the task and the editing right move to the new assignee automatically.
- ✋ Take over: If a step is assigned to a group, a member can take over the entry. From then on the 🔔 bell and emails only go to that person — for the whole entry, including later steps of the same group. The other members can still stand in or take over themselves; “Release” returns the task to the group.
- Choose email recipients: With the step option “let the user choose email recipients”, clicking Next or the return button first shows all recipients (all ticked) — so not every group member gets every email. All assignees still get the 🔔 bell notification.
- Bell: Assignees see the new task in the 🔔 bell immediately; recipients who are only informed get the message “Workflow step … reached” there.
Completeness & informing those involved
- “Continue only when answers are complete”: selectable per step – for all visible fields or only selected ones. If something is missing, the message names the fields (with jump links). Saving in between is always possible; questions hidden by a condition do not count, and a checkbox always counts as answered. The check also applies when a step advances via a trigger field.
- Checkbox instead of button: A yes/no field as trigger (e.g. “Start review now” or “Report result now”) advances the workflow on saving – so nobody forgets the extra click.
- Notify people from the entry: Besides fixed users and groups, a step can notify the creator of the entry and people from fields (e.g. “Process owner”) via 🔔 bell and email.
- Several registers working together: Steps can set fields in a linked entry – see chapter 28.
- Show in timeline: Instead of “trigger field: value”, a step shows the values of chosen fields with colour coding once it is reached – e.g. “Result: Green with conditions” or the departments' traffic lights in the central register.
12 Rules: automation between registers
Rules react to entries and automatically create follow-up entries in other registers — including data transfer and assignment.
- Trigger: register + event (create/change) + optional field condition (field, operator, value).
- Action: create an entry in the target register, with field mappings (source field → target field).
- Automatic assignment of the new entry: to the creator, to people from fields of the source entry, to register approvers or to the editors of the source entry.
Assignment & approvers of the new entry
- Real work orders: the assignees (fixed users, creator, users from fields, editors of the source entry) receive the new entry as a task in their task list plus e-mail — no longer just a notification.
- Configurable approvers: for the new entry you can pick fixed approvers or adopt those of the trigger register. If the target register has default approvers, they take precedence — the editor shows and explains this.
- Clearly separated: the rule editor distinguishes “assigned workers” (receive the entry) from “approvers & notification” (a pure info mail to the trigger register’s approvers).
Detecting changes & reviewing again
- Operator “changes to”: The rule fires only at the moment a field changes to the value (e.g. “Start review now” is ticked) – not on every later save.
- Target entry already exists: With a primary key in the target register, no duplicates are created. The rule either skips or updates the copied details and reopens the review – but only if something changed or the review was not completed regularly. The new task lists the changed fields; you choose the step at which the review resumes.
- Only update an existing entry: The rule never creates anything but only changes an existing target entry – e.g. sets a risk to “Void – basis changed” as soon as its cause has gone. Nothing is deleted, and the history shows why the status changed.
- Review-relevant fields and changes field: When reopening, you can define which copied fields reopen a completed review; other changes are updated silently. Optionally, the rule writes all changes (old → new) into a text field of the target, e.g. “Changes since last review”.
13 Reports, scheduler & e-mail dispatch
Registers become reports — on demand or automatically on a schedule, straight to the inbox.
Report builder
- Choose a primary register and compose columns — including fields of linked registers (e.g. a ROPA report with asset details).
- View reports on demand and download them as Excel.
Scheduler & dispatch
- Schedule per report (e.g. weekly, Mondays 07:00) — Floriti generates the report automatically.
- E-mail dispatch to defined recipients, with the report attached.
Illustration: scheduled reports with schedule, recipients and status.
14 Search, import & export
Find, bring in and hand out data — fast and permission-aware.
Global search
- Full-text search across all entries — right from the top bar.
- Permission-aware: everyone finds only what they are allowed to see (areas, roles, own drafts).
- Tags: Search also finds tags from AI analysis and import; without a search term it shows all active tags (chapter 24).
Import
- Excel/CSV import per register — processed in blocks and therefore suitable for very large files (tested with 400,000 rows).
- Primary-key field: existing entries are matched on re-import instead of duplicated; imports are repeatable.
- Tag: When importing into an existing register, all new entries receive a tag — so you can find the whole batch again later (chapter 24).
Export
- Single entry: Excel, CSV or PDF — optionally with “include linked” (linked entries come along).
- Whole register: Excel, CSV, PDF (each entry on its own page) — generated as a stream, so it works reliably even for 400k registers.
- Everything at once: “All → Excel” (one workbook, one sheet per register) and “All → CSV (ZIP)”.
- Link overview: all register links as their own Excel/CSV evaluation.
- Official PDF forms: Floriti fills in prescribed PDF forms (e.g. notification forms from authorities) with the values of an entry — see Chapter 25.
15 User management: roles, groups, areas
Three building blocks control who sees and does what: roles (function), groups (assignment) and areas (data access).
Roles
| Role | Rights |
|---|---|
| Admin | Everything: build registers, manage users, all data, direct write access. |
| Approver | Reviews and approves entries of their registers; sees all entries there; manages the trash. |
| User | Captures and edits own entries via the approval process. |
| Direct editor | Writes directly to the register without the approval loop. |
| Assignment creator | Creates empty entries and distributes them as work assignments. |
| Translator | Maintains register translations (own areas); approval by admins. |
| Register creator | Assigned per area only: creates registers in that area (and its sub-areas), edits their structure and moves them to the recycle bin — details below. |
Roles are combinable — a user can be approver and translator at the same time.
User groups 👥
- Groups bundle users and can be used wherever a single user is possible: as approvers (“one is enough”), assignment recipients, default editors, workflow editors, notification recipients.
- Membership changes take effect everywhere immediately.
Areas
Areas control who sees which register. The mandatory-area rule applies: nothing is open until someone releases it. A register is seen only by the members of the areas it is assigned to — and by admins.
- Registers without an area are visible to admins only. In the area editor they are listed under the fixed entry “Not assigned (admins only)”; from there you drag them into an area. For everyone else they are invisible — in the menu, list, entries, search, attachments, export, reports and chatbot. The same applies to matrix registers.
- Registers in an area are seen only by that area's members. For everyone else the register is completely invisible — in the list, entries, search and attachments.
- “All staff” area: if the “All staff (automatic)” switch is set on an area, every active internal user is automatically a member — including users created later. Locked and offboarded users do not count; external users only if you add them explicitly. The area can be renamed, but not deleted while registers are assigned to it.
- External user: use this checkbox in user management to mark consultants, service providers and other externals. They do not automatically belong to “All staff” and see only areas they have been added to explicitly. The checkbox can also be set via Excel import (column “External”), bulk update and SSO group mapping.
- Nested areas: areas can be arranged into a hierarchy via drag & drop. Members also see the parent and child areas of their chain.
- Only admins see all areas and all registers. Approvers and assignment creators — like all other roles — act only in their own areas; as the approver of a single entry they can open exactly that entry. Direct editors may only edit directly in the table — like everyone else, they only see the registers of their areas.
- Exceptions for single entries: an assignment, an open query, an approver slot, a workflow step or an e-mail invitation opens exactly the entry concerned — even across area boundaries (form mode). Public forms and invitation links keep working regardless of areas.
- Assign in two places: in the area configuration (which registers and users belong to it) and directly in the user editor (which areas a user has).
- Per entry, visibility can additionally be fine-tuned via an area-visibility field.
The “Register creator” role
So that not every new register has to go through an admin, you can give individual members the area role Register creator in the area editor. It applies only to that area and its sub-areas; there is no global version of this role.
- May: create registers in the area, edit their structure (fields, rules, workflows, questionnaires, translations, settings) and move them to the recycle bin. If a register belongs to several areas, the role in one of them is enough.
- May not: delete registers permanently or restore them from the recycle bin, change areas, users or roles, or change instance, AI or SSO settings. Registers can only be moved between areas in which the creator holds the role.
- When creating a register, only the creator’s own areas are offered and at least one must be chosen; “Admins only (assign later)” is not available.
New in administration
- “AI usage” role: controls who can see and use the AI features (chapter 8).
- Area assignment via Excel: export all assignments (users→areas, registers→areas) as Excel, maintain them externally and re-import additively — with a dry run that shows in advance what would change.
16 Open interfaces & data sovereignty
Floriti is no silo: data flows in, out and in both directions — under control.
Connect registers with tables of external databases (e.g. Microsoft SQL Server): field mapping, direction and matching configurable — for leading systems such as ERP or CMDB. Supported: MS SQL Server, PostgreSQL, MySQL/MariaDB, Oracle, SQLite; SAP HANA on request, provided your company's SAP licence permits the connection.
Read-only views and capture forms under their own URL — secured by token or invisible bot protection (chapter 7).
Provide report data for external evaluations (BI, Excel links) — kept up to date automatically.
Exchange register structures as JSON between instances — renamable on import.
Full database backup plus GDPR-compliant data export — at the push of a button in the admin area.
System mails (invitations, approvals, notifications, reports) via your SMTP dispatch, with test function.
External systems read and write via an API key, and Floriti actively reports changes to your systems — in detail in chapter 21.
17 Multilingual
The interface speaks 10 languages. What gets translated are the labels of your registers — never the content.
🌐 Interface
German, English, French, Spanish, Italian, Polish, Dutch, Portuguese, Czech, Turkish — selectable per user, switchable in the top bar. Public forms offer the language choice directly to submitters.
📋 What gets translated
- Registers: name, description and the thank-you text shown after a public form is submitted.
- Fields: field label, input hint and explanation — explanations keep their formatting (bold, lists, links).
- Options: display only (form, detail view, table). The original value is always what gets stored — conditions, colour rules, filters, formulas and reports therefore work the same in every language.
- Workflows: step names and the “Complete step” and “Jump back” buttons.
- Alternative questionnaires: name, header text, own field labels and explanations, and info blocks.
- Across registers (admins only): section names, matrix names and the texts of public page themes.
✍️ Writing in your own language
Anyone using Floriti in a language other than German finds the 🌐 button on text and multi-line fields in the questionnaire. It opens the translator view: write the text in your own language → Translate → the AI provides the German version and a back-translation for checking. If the meaning fits, Insert in German puts the text into the field. The German text is stored; the original stays traceable on the entry — in the view below the field (“machine-translated from …”) and in the history under the Translated input tab. Each translation costs 1 AI point.
🔀 “Multilingual” switch per register
Under Admin → Register translations, choose a register and switch it to Multilingual. Only then do users and submitters of public forms see the translations; otherwise the original is always shown. This lets you translate and approve in advance, without pressure.
✨ Translate with AI
“Translate with AI” translates all texts of a register in one pass — with the whole register as context, so technical terms come out right (e.g. “Rechtsgrundlage” → “Legal basis”). The source language is freely selectable. Only missing texts and AI translations whose original has changed are translated; manually edited and approved ones stay untouched. One pass costs 1 AI point and requires AI to be switched on (chapter 8).
✅ Approval and history
Every translation has a status: AI → edited → approved. Admins approve individually or with “Approve all”; name and date are stored. Approved translations are locked — neither the AI nor translators change them until an admin revokes the approval. So fields don't get a different name every week. The history of each text shows who translated, changed or approved it and when.
⚠️ Original changed – please review
If the original changes after translation, the translation stays but is flagged. The “Please review” status filter shows exactly these places; they also appear in data quality, and admins get a notice in the bell. A renamed option counts as a new text and is translated again.
👥 Translator role
Translators maintain the translations via Administration → Register translations, including with AI. They only see the registers of their own areas. Approving, revoking approval and the “Multilingual” switch are reserved for admins.
18 Administration & operations
The admin area bundles all management functions into six clear groups — present as navigation boxes on every admin page.
| Group | Functions |
|---|---|
| ⭐ Main group | Registers · Matrix registers · Users · User groups · Areas · Reports · Rules |
| 🌐 Translation & branding | Register translations · App branding (logo, colours, instance name) |
| ℹ️ Information area | 📜 Audit log · Link overview |
| 🔑 Licensing | Licences · 🔓 Activation |
| 🛠️ Boundary functions | External reporting · Backup · Transfer building blocks · Test e-mail · Demo area · External data sources |
| 📤 Export | All → Excel · All → CSV (ZIP) · Links Excel/CSV |
- Audit log: complete timeline of all actions (create, change, approve, restore, permanently delete …) with user, time, IP and field snapshots.
- App branding: own logo and appearance per instance.
- Mobile: the core areas (login, lists, forms, workflows, dashboard, public forms) are optimised for smartphones; the admin editors are deliberately desktop-oriented.
- Registers without release: the “Registers without release (n)” box shows how many registers are not yet assigned to an area and are therefore visible to admins only. One click takes you to the area editor.
Log, storage & backup
- Retention period: how long the activity log is kept is configurable (1–3650 days) — Floriti deletes older entries automatically, documented in a GDPR-compliant way.
- Storage display: a progress bar shows the instance’s used storage (also as a My Floriti tile) — so you see early when a bigger plan is due.
- Backup explains itself: the page describes purpose and key handling and recommends the full Excel export as a readable secondary backup; every backup is logged.
19 Personal area & productivity
Tools that speed up daily work: find things fast, keep what matters in view, and everything personal in one place.
Navigate & find again quickly
Press Ctrl+K (Mac: ⌘+K) to open a jump window: go to pages and functions, search “recently visited” or search across all entries directly.
Mark registers and entries as a favourite — they appear grouped in the sidebar and are one click away.
Floriti remembers the entries and pages you opened last (locally in the browser) — carry on without searching.
Name and save a combination of filters, sorting and columns — as Mine or shared with the Team.
👁 Watching & digest mail
Watch individual entries or whole registers — Floriti then reports every relevant change (new entry, edit, approval or rejection). You set the delivery rhythm yourself in the “Personal area”:
- Immediate (single mail): every change is reported by mail at once.
- Daily / weekly (digest mail): Floriti bundles all watched changes into one clear mail per day or week.
🙋 The “Personal area” menu
The avatar menu at the top right brings everything personal together in one place:
Your roles and areas, last login, “access valid until” (expiry date) and your open tasks at a glance.
Change your password, see the two-factor status and reset trusted devices (asks for a code again at the next login).
Decide per category (e.g. approvals, watched entries, review reminders) whether you want e-mails about it.
Set the current page as your personal start page — after login you land there directly.
Copy a personal, secret ICS link and add it to Outlook or Google — your due review reminders then appear as calendar events. Renew the link at any time (this invalidates the old one).
Pick the interface language, open this manual, view the version and log out.
My Floriti — the personal start page
The start page is a tile dashboard every user composes via “✎ Customize”: add tiles, move them and arrange them in three sizes (S/M/L).
- Work at a glance: My tasks · Open approvals · My open questionnaires · Due reviews.
- Quick start: Quick start (most-used registers) · Questionnaire start · Favorites · All registers · Recently visited.
- Build your own: KPI and mini list from saved views · 📝 notepad (with rich text) · quick links.
- Watcher tiles: 🚦 workflow watcher and 📄 questionnaire watcher pin a specific entry to the start page — straight from the entry via “Pin to My Floriti”.
- Tags: 🏷 tile with the active tags from AI analysis and import, including progress (chapter 24).
20 Review reminders, data quality & audit
Keep data current and audit-proof: regular review, a quality dashboard and the presentable audit report.
⏰ Review reminders & intervals
Compliance registers (records of processing, risks …) must be reviewed regularly and provably. For that, every entry carries a review reminder:
- Next review as a date, optionally with an interval (1, 3, 6, 12 or 24 months).
- “Mark as reviewed” records who reviewed when and automatically moves the date on by the interval — the gap-free audit trail.
- Due entries appear in the 🔔 bell (also for all admins) and are reported to the responsible person as one digest mail per day.
- All due dates can also be subscribed to as a calendar feed.
- Switch off review reminders per register: in the register editor under Settings › Form, untick “⏰ Offer review reminders” if a register needs no review dates. The box, bell, digest email, calendar feed and the “Overdue reviews” metric then no longer apply to this register; existing dates are not deleted.
🩺 Data quality dashboard
The admin page Data quality shows at a glance, per register, where the data is weak — with jump links straight to the affected entries:
- Empty required fields — entries where a required field is missing or empty.
- Orphaned links — references whose target entry has been deleted.
- Not updated for a long time — entries older than an adjustable threshold.
- Overdue reviews — entries whose review date has passed.
- Invalid choice values — saved values that are no longer in their field's choice list.
- Matrix cells outside the selection — checked cells the matrix field no longer offers or whose row/column no longer exists.
- Values of deleted fields — entries with values in the field archive (see chapter 27).
- Value does not match field type — numbers, dates, timestamps, checkboxes or email addresses not stored in the format of their field, for example after the field type was changed (see chapter 27).
- Outdated translations — translations whose original has changed since they were translated (multilingual registers only, see chapter 17); the link leads to the register translations.
Green ✓ means “all good”, otherwise a traffic-light number shows the count. The analysis is built for speed even on very large registers (tested with 400,000+ entries) and is cached briefly; “Recalculate” forces a fresh run.
Filter by issue type: At the top of the page you switch individual issue types on and off — each switch also shows the total across all registers. “only registers with findings” hides registers without hits. Your browser remembers the selection.
📄 PDF audit report
Alongside Excel and CSV, Floriti produces a formatted PDF report per register — the document you present to an auditor:
- Cover page with your logo or instance name, register name, creation date, creator and entry count.
- Entry table with the visible fields; automatically in landscape when there are many columns, with page numbers and a footer.
- Optional review proof per entry (last review) — connecting review reminders and report.
- Selectable language (uses existing register translations). For very large registers, Excel and CSV remain the right choice.
21 Public API & webhooks
Other systems are welcome to join in: they read and write your registers through an interface — and Floriti reports back by itself as soon as something changes.
An external system (ERP, CRM, your own script) signs in with a key — no user account, no password.
Your system asks Floriti “what is new?” — whenever and as often as it likes.
Floriti calls your system as soon as an entry is created, changed or approved.
🔑 Step 1: create an API key
In the admin area under 🧰 Interfaces → 🔑 API keys:
- Name — what the key is for (e.g. “ERP connection”). Give every system its own; that way one can be revoked without disturbing the others.
- Permission — Read only or Read and write.
- Limit to registers (optional) — the key then sees only the registers you tick.
📥 Step 2: read and write data
The key travels with every call as a header: Authorization: Bearer flk_…. The base address is your instance plus /api/v1.
| Call | What it does |
|---|---|
GET /api/v1/registers | All registers visible to the key, including the field list (name, type, required, options) — the blueprint for everything else. |
GET /api/v1/registers/{id}/entries | Entries of a register, page by page via limit and offset. With updated_since you fetch only what has changed since the last sync. |
GET /api/v1/entries/{id} | A single entry. |
POST /api/v1/registers/{id}/entries | Create a new entry. |
PATCH /api/v1/entries/{id} | Change individual fields — fields you do not mention stay untouched. |
DELETE /api/v1/entries/{id} | Move an entry to the recycle bin (restorable, exactly as in the program). |
Values are addressed by field name, not by internal numbers — which keeps your integration readable:
POST /api/v1/registers/4/entries
Authorization: Bearer flk_…
Content-Type: application/json
{"values": {"Company": "Example Ltd", "Contact": "A. Sample"}}
- Calculated fields (formulas, links, matrix, direct links) are deliberately read-only — Floriti works them out itself and rejects write attempts with a clear message.
- Pace: 120 calls per minute and key; beyond that Floriti answers
429— the signal to “take a breath”. - Traceable: the key page shows for every key when it was last used.
/api/v1/docs there is a dedicated documentation page (German and English) with all fields, example responses and error codes — the “Open API documentation” button on the key page leads straight there. You can simply pass that page on to your IT department or service provider.🔔 Step 3: webhooks — Floriti gets in touch by itself
Instead of asking regularly, you can have Floriti call you. Under 🧰 Interfaces → 🔔 Webhooks you enter a target URL in your system; Floriti sends a small data package there for every event you choose.
| Event | Reported when … |
|---|---|
entry.created | an entry is created — including through a public form. |
entry.updated | an entry is changed. |
entry.approved | an entry has been approved. |
entry.rejected | an entry has been rejected. |
entry.deleted | an entry has been deleted. |
For each webhook you choose the events, optionally the registers concerned, and whether the field values should travel with it. Without them your system only learns “entry 123 has changed” and fetches the data itself via the API — sensible for particularly sensitive content.
POST https://your-system.example.com/floriti-hook
X-Floriti-Event: entry.updated
X-Floriti-Signature: sha256=6b1f6c…
{"event": "entry.updated", "entry_id": 123, "register_id": 4,
"register_name": "Suppliers", "occurred_at": "2026-08-06T21:15:03",
"changed_fields": ["Status"],
"changes": {"Status": {"old": "inactive", "new": "active"}},
"data": {"Company": "Example Ltd", "Status": "active"}}
For entry.updated, changed_fields shows which fields changed. With field values enabled, changes also contains the old and the new value, so your system does not have to compare by itself.
🛡 How your system knows the call is genuine
When you create a webhook you receive a signing secret — likewise shown only once. From it Floriti computes a check value over the exact content of every call and sends it along as the header X-Floriti-Signature. Your system recomputes it with the same secret: if the value matches, the message really came from Floriti and was not altered on the way. A ready-made verification example is in the API documentation.
- Delivery attempts: if your system does not answer, Floriti tries again — after 1, 5, 30, 120 and 720 minutes. A brief outage therefore costs you no notification.
- Self-protection: after 20 consecutive failures a webhook goes quiet and the operator is informed, instead of running endlessly against a dead address. Once repaired, one click reactivates it.
- Outward only: only publicly reachable
httpsaddresses are allowed as targets; addresses from internal networks are refused. - Never blocking: sending runs in the background. A slow target system never holds up someone who is saving an entry — depending on the cycle the notification arrives up to a minute later.
22 🧪 Register versioning (change management)
Rebuild a register during live operation — safely: test on an invisible draft first, then publish the changes in a controlled way. Every publish is versioned.
1 · Create a draft
- In “Manage registers” via 🧪 Draft: Floriti creates a working copy with fields, conditions, questionnaires, workflows and approvers — optionally with the entries as test data.
- The draft is visible to admins only (badge + notice banner); regular users keep working undisturbed in the live register.
- Anything goes on the draft: rebuild fields, test, capture sample entries. Note: test submissions notify the real approvers.
- Several drafts in parallel are possible — each one remembers the state of the original at its creation (its “base”) and is published individually.
2 · Publish the changes
- ⇧ Publish (on the draft card) first shows the difference: new, changed (with “previously …”) and removed fields plus changed register properties.
- Impact analysis: every delicate point lists what depends on it — number of values, formulas, rules, workflow steps, sync mappings, questionnaire references. Every field removal must be confirmed individually.
- Parallel changes are safe: if the live register was edited after the draft was created, a banner warns you — and nothing is overwritten without asking. Changes made only on the live register are kept automatically; fields added in parallel remain (deletion only via checkbox), fields deleted in parallel stay deleted (re-creation via checkbox).
- You decide conflicts: if the same field was changed both on the live register and in the draft, the dialog requires a choice per field — keep live state or take draft state. Without a decision, publishing stays locked.
- Publishing plays the changes back onto the live register instead of replacing it: field mappings, entries and all references remain intact — even renamed fields are matched correctly.
- The draft’s test entries are discarded (notice in the dialog); workflows and alternative questionnaires are deliberately not published — maintain changes to them directly on the live register.
3 · Versions, history & rollback
- Every register carries a version badge (🕘 v1, v2 …). Every publish counts up — and direct changes in the register editor are versioned too (changes of the same session are merged).
- The history (click the badge) shows per version who changed what and when — with the ➕/✏️/🗑️ balance; clicking a row expands it and lists the concrete field changes.
- Rollback: “Load as draft” brings any earlier version back as a new draft — reviewed and published via the same safe path, even if a draft already exists in parallel.
- Audit bonus: every entry stores the questionnaire version it was captured with.
23 🔐 Single Sign-On (SSO)
With single sign-on, your employees sign in to Floriti with their familiar company account. Password and two-factor verification are handled by your identity provider. Floriti only receives confirmation of who signed in and which groups that person belongs to.
What is an identity provider?
An identity provider (IdP) is your company’s central user directory. It holds all employees, their passwords, two-factor sign-in and groups. Anyone joining or leaving the company is maintained there only, and all connected applications follow automatically.
| Provider | Typical use |
|---|---|
| Microsoft Entra ID (formerly Azure AD) | Companies using Microsoft 365, the most common case. |
| Google Workspace | Companies working with Google accounts. |
| Okta, OneLogin, JumpCloud, Auth0 | Specialized cloud identity services. |
| Keycloak, authentik | Open-source solutions you run yourself, e.g. in your own data center. |
Floriti uses the open standard OpenID Connect (OIDC). Any identity provider that supports OIDC can be connected, and that includes practically all modern ones.
Step 1 · Register Floriti with the identity provider
Your IT team creates a new application at the identity provider. In Entra ID this is called an app registration, in Keycloak a client, in Google an OAuth client. The following settings matter:
- Type: web application with OpenID Connect.
- Redirect URI:
https://<your-instance>.floriti-register.com/api/auth/sso/callback. If you use your own domain, enter your domain accordingly. - Allow accounts in your own organization only (in Entra: “Accounts in this organizational directory only”).
- Claims in the sign-in token: e-mail address or user name, first and last name, and the user’s groups.
- Grant the
offline_accesspermission (in Entra: API permissions → Microsoft Graph → Delegated, with admin consent). This lets Floriti check in the background during a session whether the account is still valid (see “Leavers and blocked accounts”). - Do not generate a client secret: Floriti authenticates itself with a certificate that we send you (step 2). So no secret needs to be exchanged between you and us.
At the end of this step you have two values. Neither is secret, so both may be sent to us by ordinary e-mail:
| Value | Meaning | Example |
|---|---|---|
| Issuer | Address of your identity provider. In Entra it contains your company’s tenant ID (directory ID). | Entra: https://login.microsoftonline.com/<tenant-ID>/v2.0Keycloak: https://<server>/realms/<realm> |
| Client ID | Identifier of the Floriti application at the identity provider (in Entra: “Application (client) ID”). | a long ID with hyphens |
Step 2 · Upload the certificate and activate SSO
- Send us the values: send us the issuer and client ID as well as the label you want on the sign-in button, e.g. “Microsoft” or your company name.
- Receive the certificate: we send you a certificate file (
floriti-sso-….cer) and its fingerprint. The file contains only the public part. The private key never leaves our servers. - Upload the certificate: in Entra ID, open the app registration → Certificates & secrets → Certificates tab → Upload certificate, select the file, enter a description (e.g. “Floriti”) and click Add. In Keycloak, set the Client Authenticator to “Signed JWT” under Credentials in the client and import the certificate under Keys.
- Compare the fingerprint: the fingerprint (thumbprint) displayed must match the one in our e-mail.
- Let us know: we check whether your identity provider accepts the certificate and only then activate SSO. The login page then shows the button “Sign in with …”.
Alternatively, sign-in with a client secret is still possible, for example if your identity provider does not support certificates. In that case, send the secret via a secure channel, not by unencrypted e-mail, and tell us its expiry date.
Renewing the certificate
Our certificates are valid for two years. Renewal is largely automatic:
- Four weeks before expiry, the administrator of your Floriti instance receives a new certificate by e-mail. In addition, Floriti shows administrators a notice banner.
- Upload the new certificate in addition to the existing one, as described in step 2. Do not delete the old one beforehand.
- Floriti detects the uploaded certificate automatically, by the following day at the latest, switches over and confirms the switch by e-mail.
- After that you can remove the old certificate at the identity provider.
Until the switch, we send reminders weekly, and daily in the last week before expiry.
Step 3 · Define who may sign in
Configure the identity provider so that only assigned users may use the Floriti application, and assign the desired people or groups there. In Entra this is done under Enterprise application → Properties → “Assignment required?” = Yes. Anyone not assigned is rejected by the identity provider itself. Floriti never even sees the attempt.
Step 4 · Create groups and link them to Floriti rights
So that you can maintain rights centrally in the identity provider, link its groups to Floriti roles and areas:
- Create groups at the identity provider, e.g. Floriti-Admins, Floriti-Purchasing, Floriti-Readers, and add the employees as members.
- Have the groups included in the sign-in token (in Entra: Token configuration → “Add groups claim” → Security groups, Group ID).
- Note the identifier of each group – exactly the one the identity provider sends. Entra sends the group’s Object ID, a long ID with hyphens shown on the group’s overview page. Keycloak and many others send the group name.
- If groups are to apply to areas, create the areas in Floriti first (chapter 15).
- In Floriti under Administration → Users → SSO group mapping, create one mapping per group: enter the identifier from item 3 in the field “IdP group (name or object ID)”, then select the roles and the areas. If needed, separate roles can be set per area.
| Group at the IdP | Mapping in Floriti |
|---|---|
| Floriti-Admins | Role Admin |
| Floriti-Purchasing | Role User (Editor), area “Purchasing” with role Editor |
| Floriti-Readers | Role Reader, area “Purchasing” with role Reader |
This is how the mappings take effect:
| Situation | Result |
|---|---|
| User is in a mapped group | The identity provider is in charge: roles and areas are reset on every SSO login and synchronized every 15 minutes during the session. A change of group therefore takes effect after 15 minutes at the latest, without signing in again. |
| User is in several mapped groups | The rights of all groups are combined. |
| User is in no mapped group | On the first login they receive only the role Reader. After that their rights are left untouched and can be maintained manually in Floriti. |
| Last active admin | Is never downgraded automatically. You therefore cannot lock yourself out by accident. |
What happens on the first login
- Automatic creation: on the first SSO login, Floriti creates the user account itself, with first and last name from the identity provider. Users therefore appear in the user list only after their first sign-in.
- Existing accounts: if Floriti already has an account with the same e-mail address, that account is used. No second account is created. Such an account keeps its password sign-in until an admin sets it to “SSO only”.
- SSO-only accounts: automatically created accounts sign in exclusively via the identity provider. Password sign-in, “Forgot password” and password changes are blocked for them. This way the identity provider’s blocking and two-factor check cannot be bypassed. In user management, the “Single sign-on only” flag can be toggled per user; such accounts carry the badge 🔐 SSO there.
- Plan limit: once your plan’s number of users is reached, no new account is created. The login page then shows a corresponding notice.
Leavers and blocked accounts
- As soon as you block or deactivate the person at the identity provider, no new sign-in is possible.
- An already open Floriti session ends as well: during the session, Floriti checks with the identity provider in the background every 15 minutes. If the provider reports the account as blocked, the person is signed out after 15 minutes at the latest. If the identity provider is temporarily unreachable, the session continues normally.
- If access is to end immediately, also deactivate the person in Floriti (user management). Floriti checks this on every request. Users deactivated in Floriti are also rejected via SSO.
Messages on the login page
| Message | Meaning |
|---|---|
| “SSO sign-in failed” | The response from the identity provider was invalid, or the e-mail address was missing. A common cause is a certificate (or client secret) that has expired or been removed at the identity provider. |
| “Your account is deactivated in Floriti” | The person is active at the identity provider but deactivated in Floriti. |
| “Your plan’s user limit has been reached” | Your plan has no room for further users. |
Error page of the identity provider (in Entra e.g. AADSTS50105) | The person is not assigned to the Floriti application there (step 3). |
24 🏷 Tags: finding and working through new entries
An AI analysis or an Excel import often creates many entries at once — spread across several registers. A tag bundles such a batch so you can find it again and work through it step by step.
Assigning a tag
- AI analysis: Above the button that creates the entries you find the field “Tag for the new entries” — pre-filled with date and file name, e.g. “AI analysis 10/11/2026 – Contract.pdf”. You can change the text freely.
- Excel/CSV import into an existing register: the same field in the import dialog, suggestion “Import date – file name”.
- Validity: 30 days by default, adjustable from 1 to 365 days. Leave the field empty = no tag.
- After creation, “Show entries in search” takes you straight to all new entries.
Where to find tags
| Place | What you see there |
|---|---|
| Search | Without a search term: overview of all active tags with count, progress and expiry date. With a search term: matching tags appear as chips above the results. |
| Tag view | All entries of a tag across all registers, with a progress bar (“12 of 40 edited”), expiry date and “Open in register” for the filtered register view. |
| Register view | “🏷 Tag” filter in the view bar (appears as soon as the register has tagged entries). Tagged entries show a 🏷 in the # column. |
| Entry | Badge at the top next to the title; a click opens the tag view. |
| My Floriti | “🏷 Tags” tile with the most recent tags and their progress (chapter 19). |
Every tag has a fixed colour — the same everywhere, so you recognise related entries at a glance: in the register view it appears as a coloured pill in the # column (showing the distinguishing part of the name, e.g. the file name; the full name appears on hover), and a colour stripe marks the start of the row.
Working through
- Progress: An entry counts as “edited” as soon as it has been saved after tagging.
- ✓ Done: In the tag view, ✓ removes a finished entry from the tag — the list gets shorter until nothing is left. Anyone who may write in the register can do this.
- Extend & remove: Admins and whoever assigned the tag can reset its validity or remove the tag entirely.
- Expiry: Expired tags disappear automatically.
25 📄 PDF form templates: fill in prescribed forms automatically
Authorities, insurers and business partners often prescribe their own PDF form, such as the notification form for data breaches under Art. 33 GDPR. Floriti fills in such forms with the values of an entry: for viewing and downloading in the entry view, or as an email attachment.
Uploading a template
- Where: in the register editor under Settings › PDF templates, button “Upload PDF template”. Administrators create and edit templates.
- Only PDFs with real form fields: the fields must be clickable and fillable in a PDF reader. A scanned form, or one only meant for printing, without fields is rejected.
- No XFA: Floriti rejects forms in the outdated XFA format (Adobe LiveCycle). If a PDF also contains normal form fields, Floriti removes the XFA part and uses the normal fields.
- Limits: at most 10 MB per PDF and 20 templates per register. Password-protected PDFs cannot be uploaded.
- Security: scripts and automatic actions in the PDF are removed during upload.
- Right after the upload, Floriti suggests a mapping. The list then shows e.g. “84 of 110 fields mapped”.
✨ Register from PDF form: the AI builds the register and the mapping
Instead of creating fields by hand, the AI builds a complete register with mapping from a blank PDF form.
- New register: Administration → Transfer building blocks, tile “Create register from PDF form”, or the “From PDF form” button in the register management. Choose the PDF, optionally enter a name, “Create register”. After usually 1–3 minutes Floriti shows how many fields were created and how many PDF fields were mapped; “Open register and review” takes you straight to the register editor.
- What the AI creates: fields with clear labels and the form’s numbering, grouped by its sections. Check boxes that belong together become a multi-select, separate date and time boxes one timestamp, free texts for “other” only appear when needed.
- Existing register: in the “PDF form templates” section, “✨ Missing fields with AI” maps the still open PDF fields to existing fields and only creates the missing ones. The page then reloads; save unsaved changes first.
- Requirements: AI is enabled for your instance (Chapter 8). One run uses 10 AI points. Only the blank form (text and field names) is sent to the AI, no entry data.
Mapping PDF fields
“Edit mapping” opens the “Map PDF fields” dialog. It shows all fields of the PDF, sorted by page, with the label printed next to them in the PDF. For long forms, the search and the “Unmapped fields only” filter help; “View blank template” opens the original for comparison. For each PDF field, choose in the dropdown where the value comes from:
| Setting | Effect |
|---|---|
| Register field | The value of this Floriti field is filled in, exactly as it appears in the entry view. Formula fields are calculated. |
| — leave empty — | Floriti leaves the PDF field unchanged. Whatever the template contains there stays. |
| ✎ Text template | Text fields only: free text with {{placeholders}}, e.g. {{First name}} {{Last name}}, or a fixed text such as “Germany”. Placeholders name a field by its label; with {{= formula}} you calculate directly in the text. This puts several Floriti fields into one PDF field. |
| date only / time only | For date, timestamp and formula fields: if the PDF has separate boxes for date and time, Floriti outputs only the date (DD.MM.YYYY) or only the time (HH:MM). The default is “full value”. |
| checked if… | For checkboxes in the PDF: checked if the Floriti field is not empty (“value not empty”), or specifically when a certain option is selected. With multiple selection, it is enough for the option to be among those selected. If the Floriti field is itself a checkbox, choose Yes or No. |
| Value mapping | For radio buttons (single choice) and choice lists in the PDF: for each option of the Floriti field, you define which PDF option is set. “automatic (same text)” uses the PDF option with the same text. |
- “Apply suggestion”: Floriti compares the labels in the PDF with the labels of your fields and pre-fills only unmapped PDF fields. Fields already mapped stay untouched. Please check the suggestions.
- “Burn in values (no longer editable)”: recipients get a finished PDF without editable fields that looks the same in every PDF program. Without this option, the fields remain editable; some programs (e.g. Apple Preview or browsers) then display the values unreliably.
- Renaming is no problem: mapping uses the field name, not the label. If a mapped field later disappears from the register, the dialog marks it with ⚠.
Filling in from the entry
If a register has templates, the entry view shows a “📄 PDF form” button next to the export buttons. With a single template, the button carries its name and opens the filled PDF in a new tab. With several templates, it opens a menu: clicking a name displays the PDF, ⬇ downloads it. The form is filled in afresh with the current values on every click.
As an attachment in the send-email field
In the ✉️ Send e-mail (see Chapter 26) field type, select one or more templates under “Attach filled PDF forms”. On every send, whether by button or automatically via a trigger, Floriti fills in the PDFs afresh with the current values and attaches them.
{{Customer number}}). It is sent either as a “Separate email” to the same recipients, or you pass it on yourself, for example by phone. Because the protection only covers PDFs, no other file types can be sent along. Alternatively, Floriti encrypts the attachments with the recipient’s PGP key, see Chapter 26.What stays empty
- Approver-only fields stay empty if the person who opens the form or triggers the email is not allowed to see them. For automatic sending after a submission via a public form, Floriti fills in with administrator view.
- Hidden fields, i.e. fields currently not shown because of a condition, always stay empty.
- Mapped but empty fields are cleared in the PDF, even if the template contains something there. Unmapped PDF fields keep the state of the template.
Ready-made example: data breach under Art. 33 GDPR (BfDI)
To get started, there is the structure file Datenpanne-Art33-BfDI.floriti.json. It contains a complete register for notifications to the German Federal Commissioner for Data Protection and Freedom of Information (BfDI), based on the notification form for providers of publicly available telecommunications services:
- around 80 fields, structured like the official form,
- the PDF template “BfDI-Meldeformular Art. 33 DSGVO” with a complete mapping and burned-in values,
- a workflow Erfassung → Freigabe durch Datenschutz → Gemeldet (capture → approval by data protection → reported),
- a send-email field that automatically sends the filled notification, encrypted, to the supervisory authority when the status is “Gemeldet”; the password follows in a separate email.
The example register is in German, like the official form. Import: Administration → Transfer building blocks → Import, select the structure file and import it. The PDF template and its mapping come along; conversely, every structure export also includes the PDF templates of a register.
26 ✉️ Send-e-mail field: e-mails straight from the entry
With the ✉️ Send e-mail field type you send e-mails directly from an entry, for example the reply to a data subject request, an acknowledgement of receipt or a notification to an authority. Every sending is logged with its content and attachments.
The parts of an e-mail
In the register editor, the field opens the area “Configure e-mail sending”. There you decide for each part where it comes from:
| Part | Meaning |
|---|---|
| Recipient / CC / BCC | One or more addresses separated by commas, e.g. {{E-mail}} or a fixed address. At most 20 recipients per e-mail in total. |
| Sender address | The reply-to address: replies from recipients arrive there, e.g. in your data protection mailbox. |
| Sender name | The name recipients see as the sender, e.g. “Data Protection Example Ltd”. |
| Subject / Text | Subject line and content of the e-mail. |
Each part works in one of three modes:
- “Default text”: fixed text with placeholders, built the same way for all entries.
- “Formula”: the whole part is evaluated as a formula; field references go in square brackets, e.g.
[First name] & " " & [Last name]. Values from other registers via LINKED or VLOOKUP are possible too. - “Fill in questionnaire”: the text is only a pre-fill. Whoever edits the entry adjusts it before sending; “Reset to template” restores the pre-fill.
Placeholders
Default texts and pre-fills understand these placeholders (overview in the editor under “Placeholder overview”; insert fields with a click under “Insert field:”):
| Placeholder | Replaced by |
|---|---|
{{Field label}} | the value of a field of this entry, formatted for reading (e.g. a date or a linked entry). |
{{= Formula}} | the result of any formula, e.g. {{= LINKED([Customer], "E-mail")}} for an address from a linked register. |
{{#link}} · {{#id}} · {{#date}} | the link to the entry, the entry ID and today’s date. |
{{#register}} · {{#user}} | the name of the register and the user name of the person sending. |
Sender
- “Floriti system”: ready to use at once. The e-mail goes out via the Floriti system address with your sender name; replies go to the sender address. Depending on your plan, a daily limit applies; the field shows the current count next to the “Send” button.
- “Own SMTP account”: sending via your own mailbox, without a daily limit; the sender address is then the real sender. Administrators set up the account in the administration under the SMTP settings (“Own SMTP account for e-mail fields”). Your domain must be authorised for this with your mail provider (SPF/DKIM). Optionally, Floriti detects undeliverable e-mails in this mailbox via IMAP.
Attachments
- “Entry attachments selectable when sending”: when sending, you tick the files attached to the entry.
- “Attach register entry fields as PDF (preselected)”: Floriti attaches the entry as a PDF; choose the PDF language next to it (DE, EN, FR …). The PDF contains all fields, including empty ones and ones hidden by a condition. Not included are send-e-mail fields and approver-only fields if the sender is not an approver.
- “Attach filled PDF forms”: prescribed PDF forms, filled in afresh with the current values on every sending, see Chapter 25.
- All attachments together may be at most 15 MB. Floriti keeps a copy of every sent attachment in the sending log, even if the entry is deleted later; these copies count towards your storage.
🔒 Password protection for PDF attachments
With “Protect PDF attachments with a password”, Floriti encrypts all PDF attachments with AES-256: the entry PDF, filled PDF forms and PDF files of the entry. Other file types can then no longer be sent along because they would be unprotected; if any are selected, the e-mail is not sent. To send other files as well, use PGP encryption instead (below).
| Password | Effect |
|---|---|
| generate randomly | Floriti creates a new random password for every sending. |
| Default text | Fixed text, also with placeholders, e.g. {{Customer number}}. |
| Formula | The password is calculated from a formula. |
Specified passwords need at least 6 characters. Choose something only the recipient knows and state in the e-mail text what the password consists of. This is how the password reaches the recipient:
- “Separate email”: Floriti sends the password in a second message to the same recipients right after the e-mail. Its language follows the entry PDF; without an entry PDF you choose it under “Language of the password email:”.
- “Pass on yourself”: right after sending, Floriti shows the password and you pass it on another way, e.g. by phone. Later, anyone with write access to the entry can retrieve it in the sending log via “Show password”.
🔐 PGP encryption of attachments
If the recipient uses PGP, for example a supervisory authority with a published key, Floriti encrypts the attachments with their public key. PGP then replaces password protection; no password mail is sent.
- Setup: in the register editor, in the e-mail sending field under “Attachments”, switch on “🔐 Encrypt attachments with PGP” and paste the public key or load it from a file. Floriti shows fingerprint, owner and validity. Compare the fingerprint with the recipient, e.g. by phone.
- What is encrypted: each attachment separately (extension
.pgp): entry PDF, filled PDF forms and files of the entry, including file types other than PDF. The mail text stays readable; do not write anything confidential there. - Safety rules: nothing is sent without a valid key. If the key has expired or been revoked, has changed since it was stored, or a recipient (To, CC, BCC) is not in the key, the mail is not sent.
- Proof: the sending log shows 🔐 PGP with the fingerprint used for every mail. In the questionnaire, editors only see for whom it is encrypted, not the key itself.
Sending from the entry
- The field shows a preview of the finished e-mail with all values filled in: sender, recipients, subject, text and attachments. The preview already reflects unsaved changes, but sending only works once the entry is saved.
- “Send” sends the e-mail. Anyone who may edit the entry may send. If the same e-mail has already gone out, Floriti asks before sending it again.
- The field value is the date of the last successful sending (“Last sent: …”). You can use it in formulas, conditions, columns and follow-ups, e.g. for a deadline traffic light “Reply sent?”. If the receiving server reports an e-mail as undeliverable, it no longer counts as sent and administrators receive a notification.
- The sending log below the field and in the “E-mails” tab of the entry history shows every e-mail with sender, recipients, subject, text, the sent attachments for viewing and the delivery status, e.g. “Delivered” or “Undeliverable”.
⚡ Triggering automatically
With “Trigger automatically when …” you tie the sending to a condition, built the same way as for conditional field display (Chapter 9), e.g. “Status is Reported”. It is checked on every save, whichever way: in the form, via a public form or in a workflow. When the condition is met, there are two options:
- “Submit for approval” (recommended, e.g. for replies to data subjects): the finished e-mail appears as “E-mail for approval” in the 🔔 bell. A person reviews it and sends or discards it.
- “Send immediately”: the e-mail goes out without asking.
27 🗄️ Changing fields without losing data
Registers evolve: fields are dropped, choice lists change. Floriti makes sure no data already captured gets lost — and shows you where old values still exist.
🗄️ Deleted fields go to the archive
When you remove a field in the register editor and save (or publish a draft that no longer contains a field), Floriti does not delete its values. The field moves with all filled-in values into the register's field archive:
- In the register editor, on the “Fields” tab below the field list, the section “Deleted fields (archive)” appears — with the number of values, deletion date and who deleted it.
- ↩ Restore re-creates the field at the end of the field list and writes all values back into the entries. Set visibility conditions and the primary key flag again afterwards if needed.
- Delete permanently removes field and values irrevocably — only after an explicit confirmation.
- Admins see the collapsible section “Values of deleted fields” in every affected entry — so it stays traceable what was once recorded there.
🛡️ Warning before removing, and notifications
When you click Remove on a saved field in the register editor, Floriti immediately checks what depends on exactly this field. If anything does, the dialog “Remove field …?” shows:
- Values in entries — including completed ones. They are kept in the field archive.
- Usage: questionnaires, formulas, conditions of other fields, rules, workflow triggers and synchronisation.
- Open items: drafts, entries under review and open work orders.
Keep leaves everything as it is. Remove field takes the field out of the field list — but it is only deleted when you save your changes to the register.
If open items are affected, Floriti shows a summary of all changes that editors will notice when you save: removed fields, new required fields, fields that become required, changed field types and removed choice options. There you decide whether to notify the people affected (switched on by default):
- Creators, submitters, current editors and assignees, and approvers who still have to decide are notified — you yourself are not.
- Each person receives one bell notification and one e-mail with links to their entries.
- You can add a separate note to each change (for example “Please use field X instead”), plus a general note.
When you publish a draft, the open items appear with the same option to notify.
⚠️ Values that are no longer in the choice list
If you remove an option from a choice list, values already saved are kept. Floriti marks them in yellow:
- In the entry view the value carries the label “no longer in the list”, with a short note below.
- In the edit form the old value stays selected and marked in yellow. Saving does not change it until you deliberately choose another value or deselect it with ✕.
- Matrix fields: Checked cells whose row or column the field no longer offers, or whose combination is excluded, stay visible and can be unchecked. If cells refer to rows/columns that no longer exist at all, a note shows how many — with a button to remove them.
🔤 Changing the type of a field that has values
If you change the type of a saved field in the register editor — for example from text to number, date, select list, checkbox or email —, Floriti first checks the existing values when you save and shows the dialog “Change field type – saved values”:
- how many entries have a value and how many of them already fit,
- how many can be converted (e.g. “1,5” → 1.5 or “25.10.2026” → date) — with examples,
- which ones do not fit (e.g. “approx. 5” in a number) — with a clickable entry number. Affected entries as Excel downloads the complete list.
Convert where possible saves the convertible values in the new format; every change is recorded with old and new value in the entry history (origin “Field type changed”). Leave everything unchanged only changes the type. Cancel saves nothing.
🩺 Finding old values in data quality
The data quality page counts such cases per register as separate issue types — Invalid choice values, Matrix cells outside the selection and Values of deleted fields — with links straight to the affected entries. Use the filter by issue type to show only these cases.
28 🔗 Review processes across several registers
One case, several departments: a central register records the case, each department reviews it in its own register – and the result flows back automatically. In parallel, with separate permissions and without duplicate maintenance.
How it is structured
- Central register: records the case (e.g. “AI use cases”) and shows the overall status – for example a traffic light and a status per department, plus an “Overall status” formula.
- One register per department: with its own questionnaire, its own workflow and its own area – so the works council, for example, does not see the IT security assessment.
- Rules distribute: When the case is submitted (operator “changes to”), one rule per department creates the review entry – with a link back to the case, the copied details (ideally “read only”) and a task for the department's group.
- Only those concerned: If a department should only review under a condition – e.g. data protection only when personal data is processed – a formula hidden in the form calculates “submitted and required”; the rule reacts when it changes to “Yes”. The “Overall status” formula counts departments that are not involved as done.
- The requester fills in first: The first workflow step in the review register can belong to the person responsible for the case (assignee taken from a copied person field). They receive a task with a note, answer the questions as far as possible and hand over; only then does the department take over – with a button to send queries back. A field set on handover shows the result section only afterwards.
Reporting back into the linked entry
- In the workflow editor, every step has the section “Linked entry”: the central entry is addressed via a link or direct-link field.
- When the step is reached, Floriti sets fields there – with a fixed value, with a formula from the review entry, or as “line per source”: each department writes its own line into a collecting field (e.g. “Conditions of the departments”) and replaces it the next time.
- This applies on every path: continue button, trigger field, return or reopening. Formulas then recalculate and the central register's workflow reacts – e.g. “Approved” as soon as all traffic lights are green.
- Notifications of such a step can point to the central entry and include its creator and people from its fields – so even people who may not see the review entry itself end up in the right place.
Show-stopper, revise, resubmit
- If a department reports a show-stopper, the central case switches e.g. to “Show-stopper”; the person responsible receives a task to revise it.
- On resubmission, the rules update the copied details. Only reviews whose details changed or that were not completed regularly are reopened – an unchanged approval stays in place.
- Relevant per department: Each department only reopens when “its” fields change – a changed number of users concerns the works council, not security. What changed is shown in the review entry under “Changes since last review”.
- Risks automatically: One rule can create a risk from an answer (e.g. “Works agreement missing”) and a second one can set it to “Void” as soon as its basis has gone – resolved instead of deleted.