Zum Hauptinhalt springen

Documents & Signatures Overview

Atrium manages the documents that visitors must acknowledge during check-in: NDAs, safety regulations, WiFi acceptable use policies, GDPR data processing notices, and any custom documents your organization requires.

The document lifecycle​

Documents in Atrium follow a defined lifecycle:

Template → Render → Display → Sign → Archive

  1. Template: You create an HTML template with placeholder variables (e.g., {{visitor_name}}, {{visit_date}}). This is the reusable master document.

  2. Render: When a visitor checks in at a kiosk, the template is rendered with the visitor's actual data — their name, the date, the host's name, etc. This rendering happens on the kiosk (client-side), which enables offline check-in.

  3. Display: The rendered document is shown to the visitor on the kiosk tablet in a scrollable view. The visitor reads the document.

  4. Sign: The visitor draws their signature on the tablet's touchscreen. The signature is captured as an image along with stroke data (coordinates and timestamps).

  5. Archive: After check-in, the server generates an archival PDF from the exact HTML the visitor saw, with their signature embedded. This PDF is the tamper-evident legal record.

What's stored​

For every signed document, Atrium stores:

  • The template ID and version — which document, which version.
  • The rendered HTML snapshot — the exact content the visitor saw on the kiosk.
  • The signature image (PNG) and stroke data (coordinate arrays with timestamps).
  • The archival PDF — generated server-side from the HTML snapshot + signature.
  • A SHA-256 hash of the HTML snapshot + signature data for tamper evidence.
  • Metadata: timestamp, device ID (which kiosk), visitor ID.

Version tracking​

Templates are versioned. When you edit a template, a new version is created; the previous version is preserved immutably. This guarantees that the archived PDF always corresponds exactly to what the visitor signed — even if you've since updated the template.

Visitors are tracked per template version. If a returning visitor has signed version 3 of your NDA, and the current version is still 3, they won't be asked to sign again. If you publish version 4, they'll sign the new version on their next visit.

Default templates​

Every Atrium tenant starts with three default templates:

  • Non-Disclosure Agreement — A generic NDA covering confidential information.
  • WiFi Acceptable Use Policy — Terms for guest WLAN usage.
  • GDPR Data Processing Notice — Informs visitors about data collected during the visit and their rights.

These templates are functional out of the box. You can use them as-is or as starting points for your own customized versions. See Default Templates.