Every field has a protection class, passports are masked everywhere, and a reveal takes a reason and leaves a log entry. The exchange with the security service runs in batches, not in email threads.
P1 — working data visible to the team. P2 — contacts, masked in lists. P3 — documents, masked everywhere. P4 — files in private storage with short-lived links.
You build a batch in the service’s template and hand over the file. Verdicts come back as a file — the import shows a preview before anything changes.
The export columns and the photo file names are composed from form fields. The photo archive is built separately and served under the same access rules.
Who viewed a passport and for what reason. Who changed a status. Who exported a list. Not “we’ll recall” but a log that can be exported.
Every organizer is a separate workspace with separate media storage. Roles exist at platform and organization level; a desk operator sees their desk, not the whole database.
Your security service’s requirements, your roles, your fields — we’ll set the demo up for a real scenario.
Not slides — your scenario: categories, approvals, zones, desks. We’ll set the demo up for your event.