Administrate separates business entities, people, and permissions. Understanding these distinctions is critical to interpreting visibility and access behavior.
Companies
A Company represents an organization that uses Administrate to manage training.
Examples include:
- A primary client organization.
- A subsidiary with separate permissions or financial handling.
A single Administrate instance may contain multiple Companies.
Accounts
An Account represents an external entity being managed, such as a client, partner, or vendor.
- Accounts belong to one or more Companies depending on permission logic.
- Accounts may have one or many Contacts.
Contacts
A Contact represents a person.
- Contacts may belong to one or more Accounts.
- Contacts may appear as Learners across multiple Events.
In some cases, an Account may represent an individual (merging account and contact concepts), but this is an exception rather than the rule.
Visibility and permissions
Visibility is governed by:
- Company membership.
- Role permissions.
- Coordinator assignments.
Important:
System operations (such as imports) may succeed even if a user cannot later see the resulting records due to permission constraints.
CRM terminology
“CRM” refers to the conceptual layer that manages Accounts, Contacts, and opportunities. It is no longer a visible label within the TMS interface.