Organization Type
What It Is
An Organization Type is the workspace's category for a body, such as Member Firm or Chapter. It is a named catalogue definition with a stable configuration identity, selected by organization records. The type can include presentation assignments and organizational policy, so its significance extends beyond a display label.
Its policy can restrict the roles staff add to affiliations and enable compliance with minimum or maximum role-holder expectations. Notice options identify relevant roles and a Platform-owned template. These facets configure how Organizations and their representatives are treated; individual affiliations and assessments remain separate records.
Why It Exists
Our reading is that different association bodies need different expectations while sharing one organization model. A chapter and a member firm can both be organizations without requiring identical officers or representatives. A reusable type lets staff classify them and configure role policy consistently rather than embedding a competing set of rules in each individual organization or entry screen.
What It Is Not
An Organization Type is not an Organization, an Affiliation Type, or a Contact Role. It classifies the body; an affiliation type describes how a person relates to that body, and roles describe responsibilities. A restriction says what may be assigned, while a coverage rule says how many effective holders are expected. Neither is the calculated compliance result itself.
What It Controls
Role restrictions determine allowed new or changed responsibilities at organizations of that type. Compliance options supply the bounds evaluated by Organization Compliance, including meaningful maximum-zero cases. Notification roles and the type's template supply the policy for transition notices, subject to the separately owned recipient and delivery behavior.
Presentation assignments can override workspace forms and layouts for organizations. A changed type policy does not itself immediately refresh every organization's stored assessment; reaction, reconciliation, or reprocessing must reach them. References prevent deleting a used classification. Template changes cross Platform's service boundary and have their stated validation and compensation behavior rather than pretending to be one invisible local transaction.
How It Is Used
The CRM Administrator configures types, role restrictions, coverage expectations, and notice content. The CRM Editor creates organizations and assigns responsibilities under those choices. The CRM Reader inspects classifications and assessments. Good administration distinguishes a new policy from already refreshed assessments and uses the compliance reprocess when existing organizations need reevaluation, with previews to inspect notice content without treating them as actual sends.
Example
An association creates a Chapter type that allows officer roles and requires a billing representative. Harbor West Chapter uses it. A coordinator cannot add a disallowed new responsibility, and a compliance calculation reports missing billing coverage. When the administrator changes the minimum expectation, she requests reprocessing before assuming the chapter's saved status reflects that change. A draft preview checks the notice without storing or sending it.
How It Relates
Organization Type classifies Organization and refers to Contact Role definitions in allowed lists, coverage rules, and recipient policy. Organization Compliance evaluates effective role periods on Affiliations. CRM Settings supplies presentation fallbacks, while Platform metadata owns forms and layouts and Platform notifications owns templates and delivery. Contact Type and Affiliation Type remain separate classifications for the person and relationship.