Skip to main content
A Business Unit is a team inside the organization that runs events. Each unit has its own members, roles, and content: events, attendees, emails, and settings belong to that unit. The hierarchy has three layers:
  • Organization — the contracting party: billing, the shared member pool, the audit trail.
  • Business Unit — the team that runs events: its own members, roles, settings, and events.
  • Content — what is being run: events and everything inside them.
A company running corporate summits and field-marketing roadshows as separate teams gives each its own Business Unit — different people, different roles, different public branding — while sharing one member pool and one contract.
Every organization starts with one Business Unit. A second unit is optional. The default unit is enough for a single team.

​
Creating a Business Unit

  1. Open Business units in the organization section of the console.
  2. Choose Create business unit and give it a name (for example, “Field Marketing”).
  3. The new unit appears in the list with the assigned role, its access mode, and its creation date.
Only organization owners and admins can create Business Units.

​
Business Unit home and settings

Opening a Business Unit shows its home: the assigned role there, its access mode, and its details — description, timezone, currency, and contact email. Timezone and currency become the defaults for events created in this unit. Under Settings, edit the name and description, pick the timezone and currency, and switch the access mode described below.

​
Access: organization-wide vs. restricted

Each Business Unit is in one of two access modes, shown in the Access column of the list:
  • Organization-wide — any organization member can open this unit with their organization role. This is the default and is appropriate for most teams.
  • Restricted — only members granted a role in this unit, plus organization owners and admins, can enter. Everyone else does not see the unit at all.
Restricted mode is for confidential work — an unannounced product launch, an executive event — where organization-wide visibility is not appropriate. See Members & roles for how roles resolve.

​
Each Business Unit is its own public boundary

orriven does not host a site per Business Unit — events are presented on your own website. What the unit owns is everything the public side relies on: its attendee records (one per email address in the unit), the publishable API keys a storefront calls it with, and the name and logo from its profile that the hosted pages — checkout, order page, entry pass — show above the event name. Two units means two sets of attendee records, two keys, and two names on the hosted pages, with nothing to keep apart by hand.

​
Rules to know

  • A Business Unit cannot be nested. The hierarchy is organization → Business Unit → content. For sub-teams, use roles inside one unit or create sibling units.
  • Content does not move between units. An event belongs to the unit that created it. Registrations, orders, and audit history belong with it.
  • Restricted hides the unit. A restricted unit does not appear in lists. Pages return not found. Grant a role to give access.
  • Organization owners and admins always have access, restricted or not. An organization cannot be locked out of its own Business Unit.
  • Timezone and currency are defaults, not locks. Individual events set their own schedule. Correct unit defaults reduce corrections after event creation.