Organization
The contracting party. The organization is the company account: the shared member pool, and the container for everything else. A person can belong to several organizations and switch between them in the console.Business Unit
The team that runs events. A Business Unit is a team inside the organization with its own events, members, and roles. It is also the public boundary: attendee records, publishable API keys, and the name and logo shown on hosted pages all belong to one Business Unit. One unit might run corporate events and another field marketing — different people and different branding. Every organization starts with one Business Unit. A single-team company can ignore this layer. See Business Units and Members & roles.Event
One event run by one Business Unit: a name, dates, a page on your site, and everything attached to it — ticket types, agenda, exhibitors, housing, emails. Events are created as drafts and become public only when published. See Creating an event.Your site and the hosted pages
You present the event; orriven hosts what must be the platform’s. The event page — the description, the ticket list, the buy button — lives on your own website, built against the Storefront API or the Developer API. Each event records its page address in the console. When a buyer chooses a ticket, your site opens a checkout session, and orriven takes over the parts that must be trusted: the checkout page, the order page, and every attendee’s entry pass (QR code, wallet passes, certificate, surveys). Those hosted pages are addressed by links unique to one order or one person, and open only for the email they were sent to. There is no attendee login. See Hosted pages.Registration
One person in one event. The Attendees page lists registrations. Capacity counts them. Perks attach to them. A registration does not require an order: someone added manually on the Attendees page is fully registered with no order. The hosted checkout always creates one.Attendee vs. Contact
The same person appears in two records:
A contact is the organizer’s record of anyone who has interacted with the organization. An attendee is the person as the platform addresses them: their registrations in one Business Unit, the ticket emails they receive, and the entry passes they carry. There is no attendee login. A “my tickets” area, if wanted, is a page on the organizer’s own site fed by the Developer API.
Order
Every purchase through the hosted checkout — free or paid — goes through an order. A pending order holds its seats for 15 minutes. Confirming settles a free order immediately and sends a paid order to the payment page. Organizers typically view orders rather than create them. See Orders.Perk
A named entitlement — “Breakfast voucher”, “VIP lounge access” — defined once per event and then attached. Attached to a ticket type, add-on, or redemption code, a perk is granted to anyone who registers through it. Attached to a session or venue, it restricts entry to holders. Ticket → perk → session is how gated programming works. See Perks.Structure
Console permissions follow this hierarchy: organization role first, then the role inside each Business Unit. See
Members & roles.