Organization
What It Is
An Organization is the independent CRM identity of a body an association works with, such as a member firm, chapter, national association, or school. It is created from a name and organizational information and has its own workspace identity and organization number. Staff can describe the body even before any person is affiliated with it.
The organization owns its addresses, phones, and customer-defined values and can have a parent organization. Its current ancestry is derived from that parent chain. People relate to the organization through their own affiliations, so a departing representative does not take the organization's identity or information away.
Why It Exists
Our reading is that association staff need to separate a body from its changing representatives. If the firm exists only as a field on one contact, replacing that contact can lose the shared organizational context. Independent organization records let multiple people reference the same body and let hierarchy and policy remain understandable when representatives join, leave, or return.
What It Is Not
An Organization is not the workspace that owns the CRM data, and its place in an organizational hierarchy does not grant application access. It is not an affiliation or a roster row: those describe people's relationships to it. Organization status, archive, and role compliance answer different questions. An organization type named Member Firm does not itself establish membership rights or a financial account.
What It Controls
Its parent determines the ancestry and descendant structure used by organizational reads and people discovery. Its contact points can provide sources for affiliated people's linked details. Organization Type classifies the body and can supply role restrictions, compliance expectations, and presentation assignments. The stored compliance result is calculated by the compliance capability rather than controlled by arbitrary client values.
Archive changes ordinary availability while retaining identity and relationships. Locks govern ordinary mutation and deletion, and dependencies can prevent hard deletion even when all affiliations are ended. Version and history preserve the explanation of committed changes. These distinctions let staff understand why a closed firm may remain readable while no longer being offered for new work.
How It Is Used
The CRM Editor creates organizations, records parents, and connects people through contact-owned affiliations. The CRM Reader inspects organizational context and permitted people views. The CRM Administrator manages type policy, archive, and safeguards. Find current affiliates across an organization hierarchy explains when a national body and its chapters supply a wider current-person list.
Good use keeps the hierarchy structural and the affiliations human: moving a chapter's parent differs from moving a member's employer. Staff select an appropriate people date when investigating past representation. They inspect compliance as a stored assessment with defined reevaluation triggers, rather than assuming a recent type edit has already refreshed every organization.
Example
Harbor National has a western chapter represented by two members. Staff create the chapter beneath the national organization and add each person's dated affiliation. One representative leaves, so their tie becomes past; the other continues. The chapter still has its independent name, contact points, ancestry, and identity.
If the national body reorganizes its councils, a parent move changes the chapter's derived ancestry on the next read without altering the representatives' affiliations. If the chapter later closes, archive can remove it from ordinary discovery while those people's historical connections remain interpretable. Deletion must still account for dependencies.
How It Relates
Organization Type supplies the body's classification and role policy. Affiliations connect Contact identities to it, and Contact Roles on those ties supply coverage for Organization Compliance. Contact Details and Communication Preferences includes organization-owned sources as well as person-owned values. Record Protection and History supplies safeguards. Platform metadata and notifications own definitions, files, templates, and delivery; other applications own their program or financial records about the organization.