> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Units

> The team that runs events — its own members, roles, settings, content and public portal, inside your organization.

A **Business Unit** is the team inside your organization that actually runs events. Each business
unit has its own team, roles and content: its events, attendees, emails and settings belong to it
and to no other unit.

The hierarchy is deliberately three layers:

* **Organization** — who signed the contract: billing, the shared member pool, the audit trail.
* **Business Unit** — who trades: its own team, 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
still sharing one member pool and one contract.

<Note>
  Every new organization gets one business unit automatically. If your whole company is one team,
  you never need to create another — the default one simply is where you work, with no extra
  ceremony.
</Note>

## 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 your role, its access mode and its creation date.

Only organization owners and admins can create business units.

## The business unit home and settings

Opening a business unit lands on its home: your 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** you can 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 right 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 genuinely confidential work — an unannounced product launch, an executive
event — where "everyone in the company can look" is wrong. See
[Members & roles](/en/organization/members-roles) for exactly how roles resolve.

## Each business unit has its own portal

Every business unit comes with its own **portal** — a public website with its own address, its
own attendee accounts and its own theme. Events run by the unit publish on this portal by
default, and one attendee account there covers everything a person booked with that unit. (An
event can instead be created standalone with a portal of its own — see
[Core concepts](/en/concepts).)

This is why business units are the right split for brands: two units means two public faces, two
attendee realms, two themes — with nothing to keep apart by hand.

## Rules to know

* **A business unit cannot be nested.** The hierarchy is exactly organization → business unit →
  content; if you need sub-teams, use roles inside one unit or create sibling units.
* **Content never moves between units casually.** An event belongs to the unit that created it,
  and its registrations, orders and audit history belong with it.
* **Restricted hides, not just blocks.** To a member without a grant, a restricted unit is
  invisible — it does not appear in lists and its pages read as not found. Don't be surprised
  when a colleague says the unit "doesn't exist"; grant them a role there.
* **Organization owners and admins always get in**, restricted or not. That is the escape hatch
  that guarantees an organization can never lock itself out of its own business unit.
* **Timezone and currency are defaults, not locks** — individual events set their own schedule,
  but keeping the unit's settings right saves correcting every event after creation.