Event setup
Agenda with sessions and rooms, speakers, sponsors, in person, online or hybrid, a time zone per event and a capacity.
From event page to door check-in
Run events with ticket types, a registration page, QR tickets and check-in at the door.
An event can be in person, online or hybrid with a venue, a time zone, a capacity, multi-day sessions by room or track, speakers with photos, sponsors by tier and tags, and moves through draft, published, closed, ended and cancelled. Tickets are free or paid in INR with GST included or added, a quantity, a sale window, a per-order limit and hidden tickets behind an invite code. The public page takes registration with custom questions, group orders, a waitlist with timed offers, approval, honeypot and rate limits, and the last seat is decided by order number. A ticket page shows a QR code, an 8-character code and a calendar file and allows cancel, transfer and accepting a waitlist offer; emails cover confirmation, approval, payment, waitlist, offers, cancellation, transfer and reminders 24 hours and 1 hour before. Check-in uses the camera where the browser has BarcodeDetector, a typed code or a name, once per ticket and session, with walk-ins, live counts and an offline queue of scans. Paid orders use Payments, discount codes use Coupons and certificates use Certificates, each through a service binding and a sealed key and each optional. Reports show attendance, no-shows, revenue and refunds due, with CSV; refunds are marked manually. Uploads for covers and speaker pictures go to R2. Optional Claude features propose copy and an agenda from an outline. API /api/v1/events, /api/v1/registrations and a workspace feed; webhooks registration.created, registration.paid, registration.cancelled, registration.checked_in and event.published.
What Events does for you.
Agenda with sessions and rooms, speakers, sponsors, in person, online or hybrid, a time zone per event and a capacity.
Public page with questions, group orders, waitlist with timed offers, approval, an email code to find a ticket, transfer and cancel, and reminders 24 hours and 1 hour before.
Check-in by camera scan, typed code or name, per session, walk-ins, live counts; attendance, no-shows and revenue with CSV export.
A suggested path for Events. What you can do depends on your access in the app.
Add the details, agenda and ticket types, then publish.
People register and receive tickets by email.
Open the check-in page on a phone at the door.
Live host, inventory, governance, health checks, verification, dependencies and history.
An event can be in person, online or hybrid with a venue, a time zone, a capacity, multi-day sessions by room or track, speakers with photos, sponsors by tier and tags, and moves through draft, published, closed, ended and cancelled. Tickets are free or paid in INR with GST included or added, a quantity, a sale window, a per-order limit and hidden tickets behind an invite code. The public page takes registration with custom questions, group orders, a waitlist with timed offers, approval, honeypot and rate limits, and the last seat is decided by order number. A ticket page shows a QR code, an 8-character code and a calendar file and allows cancel, transfer and accepting a waitlist offer; emails cover confirmation, approval, payment, waitlist, offers, cancellation, transfer and reminders 24 hours and 1 hour before. Check-in uses the camera where the browser has BarcodeDetector, a typed code or a name, once per ticket and session, with walk-ins, live counts and an offline queue of scans. Paid orders use Payments, discount codes use Coupons and certificates use Certificates, each through a service binding and a sealed key and each optional. Reports show attendance, no-shows, revenue and refunds due, with CSV; refunds are marked manually. Uploads for covers and speaker pictures go to R2. Optional Claude features propose copy and an agenda from an outline. API /api/v1/events, /api/v1/registrations and a workspace feed; webhooks registration.created, registration.paid, registration.cancelled, registration.checked_in and event.published.
Online sessions with a live room belong to Webinars; bookable slots belong to Timeslots; certificates belong to Certificates.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
events.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.