Create the organization
Each client, chapter, or business unit gets its own record with identity, contact, plan, and region, then one switch turns on the white-label experience.
White-Label Event Platform
Run white-label event organizations from one platform workspace
Give clients, chapters, or business units their own organization identity and event workspace while your platform team manages access, plan controls, usage, domains, and supported payment setup.
Organization-level brand settings Scoped teams and event records Plan-aware capability control
Trusted By Event Teams 500+ Events Run on EventHex15+ CountriesPer-org Scoped RecordsPlan-aware Capability Control
Set Up Around Who Owns Each Event
Create the organization, switch on white label, and let the plan decide what each one can use.
Organization created Add organization
Plan-aware controls Edit plan
Gate capabilities by plan
Custom domains, white label, and event limits follow the plan an organization is on, and attendee mobile app settings are managed per organization.
White label and custom domains are plan-gated. Confirm what your plan includes during the demo.
Per-event branding
Your Brand on Every Event
On a white-label plan, switch on branding for an event and set your own brand title and logo. They replace the EventHex footer on the event website, registration forms and tickets, and carry onto printed badges.
Custom domain
Put Every Event on Your Own Domain
Add a custom domain to an event website, check that it is verified, and switch it on or off whenever you need to. The EventHex subdomain stays available. Custom domains depend on the organization's plan.
Keep Ownership, Access, and Usage In One Context
White label is not only a logo field. The organization boundary carries teams, events, capabilities, metering, and account context.
Organization directory
Find the client, chapter, or business unit without flattening every event into one undifferentiated list.
Scoped access
Organization admins, event teams, platform admins, and event-level roles keep responsibilities separated.
Org adminEvent teamPlatform adminScanner
Feature gates
Control paid tickets, API access, white label, custom domains, and AI website generation by plan.
Resource limits
Apply configured limits to events, team members, attendees, campaigns, and other metered resources.
Usage counters
Review events, attendees, content records, campaigns, and AI or media fields tied to the organization.
EventsAttendeesCampaignsAI fieldsMedia
Payment setup
Keep supported gateway credentials and connected-account configuration attached to the owning organization.
From Organization Record to Live Event Portfolio
-
01
Create the organization record
Capture identity, contact, plan, and region before any events are created.
- ·Client or chapter identity
- ·Plan context
- ·Region and support context
-
02
Connect the people who need access
Invite organization admins first, then scope event teams and narrower event roles.
- ·Organization admin
- ·Event team
- ·Event-level role
-
03
Configure brand, domain, and payments
Apply supported brand fields, verify domain eligibility, and attach the approved payment relationship.
- ·Logo and color settings
- ·Custom-domain verification
- ·Gateway or connected account
-
04
Create events in the right workspace
The organization becomes the parent context for users, events, plan rules, and supported settings.
- ·Correct organization boundary
- ·Inherited brand context
- ·Plan-aware capabilities
-
05
Review portfolio usage
Track counters that inform capacity, plan conversations, renewals, and support context.
- ·Events and attendees
- ·Campaign usage
- ·AI and media fields
Payouts
Let Each Organization Get Paid Directly
Each organization can connect its own Stripe account for bank payouts, set up Razorpay Route for split payments, or add its own gateway keys. Its events can then choose the organization payment option at checkout setup.
See also Payment Processing.
Built for Every Kind of Distributed Event Business
Event agencies
Manage client organizations and repeat programmes under distinct commercial relationships.
Associations
Support chapters, committees, or regional teams while keeping portfolio oversight.
Enterprises
Separate brands, business units, or markets without creating disconnected tooling.
Conference portfolios
Operate recurring event series where each edition or region needs its own context.
Exhibition groups
Coordinate show brands, exhibitor records, and event teams across a portfolio.
Platform partners
Define plan, payment, support, and capability responsibilities before launch.
What can we brand?
Organization logo and color fields plus a white-label configuration path are supported. Exact coverage across organizer tools, event sites, emails, PDFs, apps, and domains should be demonstrated for your required journey.
Can every client have its own workspace?
EventHex supports organization records with scoped users and events. The allowed number of organizations, events, users, and capabilities follows the agreed plan.
Are custom domains supported?
Custom-domain entitlement and event-domain workflows exist. Availability depends on the plan, DNS setup, target surface, and verification.
Can we control features and usage by organization?
Subscription plans contain feature toggles and limits, while organization usage counters track portfolio and per-event activity used by plan enforcement and operations.
Can each organization use its own payment account?
Supported organization-level Stripe, Razorpay, or Tap credentials exist. Connected-account models also exist, but fees, routing, onboarding, and payout responsibilities require specific scoping.
Does EventHex guarantee total data isolation?
Organization identifiers and access checks scope application behavior. Review roles, permissions, region, support access, and required controls for your operating model before launch.
