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.
app.aditum.id · Media Leaders Roundtable 2026 · Security
01
Every field has a protection class
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.
Passport and date of birth are P3: not visible even on the card
A reveal takes a reason; the entry goes to the log
A photo is served by a signed link for a few minutes
02
The exchange with the security service — in batches
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.
A person’s data changed — they are in the re-export queue
Security status is a separate axis from the application status
Without a green verdict a badge can’t be issued at the desk
03
The photo archive and columns — as the service asks
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.
The export template is an event setting
The photo archive is built as a separate file, next to the list
Every file download is logged
04
The audit log: who, what and when
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.
The log is append-only — entries are not edited
Filter by person, action, event
Log export for an internal review
05
Roles, two-factor sign-in, isolated organizations
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.
Two-factor authentication and trusted devices
A separate role for the security service
Team invitations — only from an organization administrator
06
Everyone on the team sees only their own work
A desk operator is invited to the summit alone, and a Danube Coaches worker only to their runs. The kind of work in the invitation decides what the person sees: the desk, accommodation and transfers, applications or the doors. For every event you see whether the team is complete and whom to invite.
“Desk operator”, “Logistician”, “Approver”, “Door security”, “Carrier worker” and more
Several roles per person; every change goes to the log as “before/after”
Staff app roles open nothing in the console
07
Sign-in without a password — a passkey from the password manager
A desk operator opens the staff app with a passkey created in the console’s browser: no password, no code. Whoever signs in with a password enters a code from an authenticator or a backup code every time. An account can switch on “Passkey only” — then password sign-in is refused.
Up to 10 passkeys per account
“Passkey only” turns on with one synced passkey or any two
Sensitive actions in the profile need a fresh confirmation, valid for 10 minutes
A demo is a 30-minute call with the team that develops Aditum. Not slides but your scenario: we set up categories, approvals, zones and desks for your event.
1Fill in the form: event type, number of participants, a few words about it
2Within one business day we email you to agree a time
3On the call we show Aditum configured for your event and answer your questions