Confidentiality Declarations
Feature Detail
Description
Supports the collection and storage of confidentiality declarations from peer mentors acting as drivers or performing sensitive support roles. Blindeforbundet requires drivers to sign a taushetseerklæring (confidentiality declaration) before receiving driver honoraria. The feature presents the declaration as a mandatory in-app step within the relevant expense registration flow, captures the peer mentor's digital acknowledgement, and stores a timestamped record linked to the expense or assignment. Coordinators can view declaration status in the admin portal.
User Flow
Analysis
Confidentiality declarations are a legal and organisational compliance requirement for peer mentors handling sensitive personal data or acting in driver roles. Without a digital workflow, organisations rely on paper forms that are easily lost, difficult to audit, and create administrative burden when chasing outstanding signatures. Digitising declarations within the app ensures that no honorarium or assignment can be processed without a valid declaration on record, creating a reliable audit trail for compliance reviews. This is particularly critical for Blindeforbundet, whose peer mentors regularly handle sensitive health and personal information as part of encrypted assignment dispatch.
Implement declaration screens as a conditional step injected into the expense registration wizard when the selected expense type requires one (e.g. driver honoraria). Store declarations in a dedicated `documents` table linked to both the user and the triggering expense or assignment record, with a timestamp and the declaration text version hash to track which version was accepted. Declaration text should be versioned and managed as backend content so it can be updated without an app release. On the admin portal, surface declaration status per user in the expense approval view. Ensure the declaration screen is fully accessible per WCAG 2.2 AA — large tap targets, clear heading, and plain-language Norwegian text.
Components (113)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.