Skip to main content

Companies Logic

Updated

Company logic determines how communication Triggers apply when filtering or targeting specific Companies within Administrate.

If you are unfamiliar with how Trigger activation types work (for example, On Registration, Days Before, or Hourly Offsets), see: Trigger Types and Timing.

In this article:

What is a Company?

In Administrate, a Company represents a business entity that controls key areas of your system, including financials, permissions, course ownership, and reporting.

Company logic determines how data is grouped, who can access it, and how workflows (including communication Triggers) are applied.

Single vs Multiple Companies

In many cases, a single Company is sufficient, with all training activity managed under one business entity.

  • Regions and locations can be used to separate operational logic
  • User roles control access within that single Company

Multiple Companies are used when different business units operate independently but within the same Administrate instance.

  • This introduces segregation, meaning data, financials, and workflows are isolated between Companies
  • Common use cases include franchises, internal vs external training, or partner organizations

Each Company can manage its own:

  • Accounts and contacts (CRM)
  • Course templates and events
  • Users and permissions
  • Sales ledger and invoicing

Users with a Super Company User role can access and operate across multiple Companies.

How Company Logic Works

Triggers can be configured to evaluate conditions based on Company records. This allows communications to be sent only when certain Company-level criteria are met.

  • Triggers may filter by Company attributes
  • Triggers only evaluate data within the Company context available to the user or system
  • Company-based logic can be combined with other object conditions (such as Events, Bookings, or Contacts)

Visibility and Access

Company configuration directly impacts which records a Trigger can evaluate.

  • If data is segregated across multiple Companies, Triggers will only act on data within the relevant Company scope
  • User roles and permissions determine which Companies are visible and therefore which data can be included in Trigger logic
  • Super Company Users can evaluate and act across multiple Companies

Practical Considerations

  • Ensure Company records are correctly assigned and aligned with your business structure
  • Confirm that Company-level conditions match your intended communication workflows
  • Be aware of data segregation when troubleshooting why a Trigger did or did not fire

Related articles