Use the event's registration flow and configured fields to create the operational attendee record.
From registration to the last scanned Session, keep the attendee in one connected event workflow.
Registration, People, Agenda, Sessions, Rooms, Desk, Kiosk, badge output and session attendance use the same event context instead of becoming separate onsite tools.
Registration→People→Desk / Kiosk→Check-in→Badge→Rest of event
Registration & attendee identity
The onsite operation starts before anyone reaches the entrance.
Registration creates the event attendee context used by People, agenda access, sessions, check-in, badge output and other authorized event workflows.
Search, review and maintain the attendee information used by event operations.
Give attendees access to the schedule and the Sessions relevant to the event.
Keep session time, room, attendance and onsite access tied to the same attendee identity.
Registration Builder
Build the registration that creates the operational attendee record.
Configure the Main Registration Form and publish it into the event journey. Submitted registrations become Event People used by Desk, Kiosk, badges, Sessions and downstream event workflows.
EVENT REGISTRATIONJoin Domplatta Summit.
01
The attendee record
First, Domplatta needs to know who arrived.
Registration data becomes part of the event People domain. Find an attendee by name, email, registration code or QR and open the record when your role allows it.
ExampleMaria Ionescu · Nova Events · Main Stage · Pending
People / DeskPending
Search: Maria Ionescu
Maria IonescuNova EventsMain Stage
Email
maria@example.comType
Speaker
maria@example.comType
Speaker
02
Desk Mode
The operator verifies the attendee and can correct permitted data.
Desk Mode is the staff workspace. The operator does not only see a row in a list: they open the attendee record and work with the current event data.
- Find the attendee: QR, code, name or email.
- Review the record: Organization, type, access and configured fields.
- Correct where allowed: Authorized changes become the current record.
- Continue the workflow: Check-in and print without a parallel list.
Desk ModeFront Entrance
SaveSave + Check-inPrint
All actions use the same Maria Ionescu record.
03
Check-in
Check-in updates the attendee’s status across the event.
Maria changes from Pending to Checked in. Other authorized operational interfaces can then use that current status instead of relying on a separate copy of the attendee list.
Maria IonescuPending
CHECK INMaria IonescuChecked in
Organizer
+1 arrivalEntrance B
Checked inBadge
Current data
+1 arrivalEntrance B
Checked inBadge
Current data
04
Badge printing
The badge is generated from the attendee’s current data.
The event defines the active badge template. At print time, Domplatta combines the template with the attendee fields and configured QR payload.
- Template: defines layout and visible fields.
- Attendee record: provides name, organization, access and current values.
- QR: uses the event’s configured payload.
- Reprint: uses the current record again, not an old copy.
DOMPLATTAMaria IonescuNova EventsMain Stage
Badge Designer & Printing Operations
Design the badge visually, then operate printing as a live-event workflow.
Use the Badge Editor for templates, dimensions, attendee fields, QR elements, typography, positioning and live preview. Badge Operations then carries the active template into print stations, jobs, logs, failures and reprints.
ELEMENTSTextAttendee fieldQRImageBackground
DOMPLATTA SUMMITMaria IonescuSpeaker · Nova Events
BADGE80 × 80 mmSafe margins2 copiesActive templateLive preview
Choose the badge design used for the event.
Operate printing through configured stations.
Generate output from current attendee data.
Keep useful operational evidence visible.
Recover quickly when a badge needs another print.
05
Kiosk Mode
Kiosk Mode gives attendees a focused self-service arrival flow.
The attendee scans a QR code, Domplatta finds the matching event record and continues through the steps enabled for that kiosk. The interface deliberately stays simpler than Desk Mode.
QR scanIdentity confirmationSelected editsAutomatic check-inBadge printAuto reset
Kiosk ModeReady
Scan QR codeDP-1001
06
Multiple entrances
One attendee, correctly visible at every authorized entrance.
If Maria checks in at Entrance A, Entrance B should not process her as if she were still Pending. Authorized interfaces work from the same operational state.
Maria IonescuChecked in
Entrance AChecked inEntrance B
Checked inVIP Desk
Checked inOrganizer
Arrival visible
07
Organizer
See the operation changing in real time while your teams work.
Depending on the enabled modules, the dashboard can surface checked-in attendees, pending attendees, printing activity, station activity and recent operational actions.
Checked in318Pending126Printed301
08
People continues through the event
The attendee record does not disappear after the entrance.
The same person can continue, depending on enabled modules, into sessions, lead retrieval, learning, certificates and reporting. The goal is one person domain rather than a new disconnected list for every module.
People→Check-in→Sessions→Lead Retrieval→Learning→Reporting
Sessions & attendance
Arrival is only one state change in the attendee lifecycle.
Keep the same attendee connected to Session access and attendance so you can measure participation beyond the entrance.
Use the attendee's event identity for Session scanning where attendance tracking is enabled.
Keep Session access decisions connected to the scheduled Session and attendee context.
Track attendance against the Session instead of maintaining a separate door list.
Use Session attendance alongside other authorized event activity in analytics.
Session Scanner
Give session operators a focused scanner instead of a general event console.
The dedicated Session Scanner uses the attendee and Session context to record attendance while respecting eligibility, capacity and duplicate-state rules.
SESSION SCANNERAI in Events
Main Stage · 14:30
✓ Maria Ionescu · Checked in
Global People
Keep Event People operational while connecting authorized identity across events.
For recurring events and portfolios, a Global Person can connect Event Participation and cross-event activity without turning each event's People list into one universal attendee database.
09
Organizations
Organizations and attendees are different domains, but they can be connected.
Nova Events can be an exhibitor. Maria can be a representative of Nova Events and, if registered for the event, also appear in People. The organization keeps its commercial/operational relationship while the attendee keeps the attendance history.
Nova EventsExhibitor
Maria Ionescu
Registered attendeeAndrei Popescu
Representative
Registered attendeeAndrei Popescu
Representative
Lead Retrieval · Expo Hall · Organization scope
10
Permissions
Your team sees only the interface and data relevant to each assigned role.
Domplatta does not rely only on visually hiding menu items. Access is modeled through capabilities and scope.
11
Before · Live · After
Now the complete lifecycle has context.
Before the event you prepare data, permissions, badges and operating points. Live, teams search, scan, correct, check in, print and monitor. Afterwards, attendance, activity, sessions, leads and exports remain available for delivery and follow-up.
Before
→Registration · People · Organizations · Badges · Permissions · Readiness
Live
→Desk · Kiosk · QR · Check-in · Print · Sessions · Leads · Live Ops
After
Attendance · Activity · Exports · Reporting · Learning
Real operating setup, not a generic package
Tell us how arrival needs to work for your event.
We’ll review registration data, entrances, attendee types, Desk/Kiosk, badge requirements, printers, permissions and integrations.