Keep session attendance connected to the attendee who entered the event.
Domplatta sessions continue from the shared People domain. Attendance actions can stay tied to the attendee, the session and the event instead of becoming another disconnected spreadsheet.
Attendance should not create a new attendee universe.
Session context
Connect the attendance action to the configured session.
Attendee identity
Use the same attendee domain already available to the event.
Operational role
Give session staff only the scanner/session workflow required.
Attendance record
Keep participation available for authorized downstream use.
Attendance data can remain useful after the room closes.
Reporting
Review participation alongside other event activity.
Learning
Where enabled, connect sessions to learning or on-demand workflows.
Certificates
Where configured, attendance can contribute to certification logic rather than requiring manual reconciliation.
How this fits into event operations.
Configured programme item
Identify event person
Record attendance
Keep participation
Reporting / learning
Practical questions.
Do session staff need the full event portal?
No. Session-scanner staff can be routed directly to the operational surface required for their assignment.
Is session attendance separate from People?
No. The intended model keeps attendance connected to the event attendee domain.
Can session participation be used after the event?
Yes. Depending on enabled modules, attendance can feed reporting, learning and certification workflows.
Show us how your event needs to operate.
We can review attendee flow, access, onsite operating points, badges, organizations, sessions, reporting and integrations around the modules you actually need.
