Core concepts
Organisations, events, ticket types, orders, tickets, attendees and people.
| Object | What it is |
|---|---|
| Organisation | The organiser's workspace. Owns events, team, keys and billing. |
| Event | A single event with dates, venue, sessions and speakers. |
| Event page | The public page for an event: a template plus configuration. |
| Ticket type | Something you sell or give away: price, capacity, sale window. |
| Order | One checkout by one buyer, containing one or more tickets. |
| Ticket | One admission, with a QR token and a check-in state. |
| Attendee | A ticket holder for one event, with that event's registration answers. |
| Person | A human's persistent Konecto identity across events (attendee app). |
| Profile | A person's public Konecto profile and QR, customised by them, with per-field visibility. |
| Booth | An exhibitor's stand at an event; scans at a booth count towards challenges and exhibitor reports. |
| Challenge | A gamified goal built from actions (booth scans, connections, sessions, surveys) with targets and an organiser-chosen reward. |
| Connection | A link between two people, recording where they met. |
| Suggestion | A person the attendee might like to meet, from shared or related interests and matching "would like to meet" choices, with the reason shown. |
| Community | An organisation's community of attendees in the attendee app. |
| Module | A paid add-on enabled for one event. Organisation-wide plans are arranged with the Konecto team. |
Event states
draft → published → live → ended → archived
Money
All payments run through Stripe Connect. Ticket money is paid to the organiser's Stripe account; Konecto takes an application fee on paid tickets.
Plain-text version for agents: llm.konec.to/docs/concepts.md