Administrate’s structural configuration (Companies, Regions, Locations, Workplaces, and Venues) does more than organize data. It actively drives financial logic, availability, permissions, scheduling, and reporting outcomes.
This article explains how these structural layers relate, what each one controls, and the rules power users rely on when scaling.
Contents
- The configuration hierarchy
- Companies: segmentation and control
- Regions: financial and operational context
- Locations: time zones, availability, and requirements
- Workplaces: shared operating areas
- Venues: granular physical detail
- Common implications and “why is this happening?”
- Related references
- Where to go next
The configuration hierarchy
From a logic perspective, Administrate’s structure flows top-down:
- Company → defines major segmentation and contains Regions
- Region → defines financial and operational context
- Location → defines time zone, availability, and event requirements
- Workplace → groups Locations into a shared operating area
- Venue → optional, granular physical detail under a Location
Most unexpected behavior in pricing, availability, and reporting can be traced back to this hierarchy.
Companies: segmentation and control
Companies are the highest-level boundary. Many customers operate successfully with a single Company, but multiple Companies are used when intentional separation is required.
Multiple Companies are commonly used to segment:
- financial processing and invoicing entities
- CRM records (Accounts and Contacts)
- course catalogs and delivery workflows
- user access and permissions
Certain roles may be granted cross-company access when operationally appropriate.
Regions: financial and operational context
Regions function as financial and operational silos, not merely geographic groupings.
Regions commonly control:
- currency and pricing context
- tax handling (where applicable)
- course catalog segmentation and visibility
- region-specific operational workflows
If pricing or currency appears incorrect, Region configuration is the first place to check.
Locations: time zones, availability, and requirements
Locations are required because Events must have a Location. Selecting a Location immediately influences Event behavior.
Locations control:
- Time zone for scheduling and communications
- Instructor and resource availability
- available Venues
- which Region’s pricing and currency context applies
Workplaces: shared operating areas
Workplaces group multiple Locations into a shared operating area for:
- instructors delivering training
- learners participating across nearby locations
- resources being allocated efficiently
Workplaces reduce friction when delivery spans multiple Locations.
Venues: granular physical detail
Venues are optional and always tied to a Location. They inherit Location logic, including time zone.
Venues are most useful when you need:
- specific physical addresses
- consistent room or site selection
- venue-level reporting or logistics
Common implications and “why is this happening?”
- Emails firing at the wrong local time → Location time zone
- Pricing or currency unavailable → Region context
- Instructor or resource not selectable → Location or Workplace availability rules
- Users cannot see certain data → Company boundaries and role permissions
Related references
Where to go next
- Events: How Training Is Delivered in Administrate
- Finance in Administrate: Pricing, Revenue, and Region Logic
- Users & Permissions: Access Control by Role and Scope