Core concepts
Tenant
An organization (company, club, agency) registered on the platform. Each tenant has an isolated data space: events, attendees, settings, and billing of one tenant are inaccessible to another. A single user can be a member of multiple tenants.
Organizer
A tenant employee who creates and manages events. The organizer works in the tikento dashboard: setting up forms, monitoring registrations, accepting payments, and analyzing statistics.
Attendee
A person who registers for an event through an tikento form. The attendee fills out a form, receives a confirmation and a QR ticket. Attendees do not interact with the organizer dashboard.
Registration
An attendee's application for an event. A registration goes through several statuses: email verification, moderation (if enabled), payment (for paid tickets), and final confirmation. All registrations are available in the "Attendees" section within the event.
Events
Event
The core entity of the platform — an event with a name, date, venue, and registration form. An event follows a lifecycle: draft -> published -> completed (or cancelled).
Event type
An event category: conference, webinar, workshop, festival, wedding, children's party, and 20+ more. The type affects setup recommendations and how the event appears in the catalog.
Slug
A unique URL identifier for an event within a tenant. Format: lowercase Latin letters, digits, and hyphens (2 to 32 characters). Used in the public registration link: app.tikento.com/events/your-slug/register.
Tickets and payments
Ticket
A type of access to an event. The organizer creates ticket templates (e.g., "Standard", "VIP", "Online Access") with a price, quota, and sales period. When purchased, the attendee receives a ticket instance with a unique QR code.
Ticket option
An add-on to a ticket with its own price and limit: transfer, meals, T-shirt size, etc. The attendee selects options during registration.
Promo code
A code for a ticket discount. The organizer sets the discount amount (percentage or fixed sum), usage limit, and expiration date. A promo code can apply to all or selected ticket types.
Reservation
A temporary hold on a spot until payment is completed. If payment is not received within the allotted time, the reservation is cancelled and the spot becomes available again.
Forms and widget
Registration form
A set of fields that the attendee fills in during registration. Built using a drag-and-drop builder. Supports 14 field types, conditional logic, versioning, and localization.
Widget
An embeddable module for placing the registration form on an external website. Connected with a single line of HTML code. Runs in Shadow DOM to avoid style conflicts with the host site.
On-site operations
Check-in
Confirming an attendee's presence at the entrance. The organizer scans the ticket's QR code with tikento — the system validates the ticket and marks the attendee as arrived. Works offline.
Sync
Automatic data exchange between the device and the server. If the organizer worked offline (checking attendees, marking payments), when internet connectivity returns all changes are sent to the server and updates are downloaded.
Technical terms
PWA (Progressive Web App)
A web application that can be installed on a device's home screen. Works without the address bar, supports push notifications, and works offline. tikento at app.tikento.com is a PWA.
Deep Link
A special link that leads to a specific section of the app. In tikento, a deep link in the format https://t.me/tikento_bot/app?startapp=... opens the Mini App directly on the relevant event or form.
RLS (Row Level Security)
A database-level security mechanism that ensures complete data isolation between tenants. Every query is automatically filtered by the current user's organization — it is impossible to access another tenant's data.
Access Key
An individual code for accessing event content (e.g., a webinar recording). The organizer uploads a pool of codes, links them to a ticket type, and the system automatically issues a code to each buyer.