Contact Role
What It Is
A Contact Role names a responsibility a person can hold at an organization, such as Billing Contact or Chapter Chair. The role is a reusable workspace catalogue entry with a name and stable identity. An actual holder is a contact with a dated role period on an affiliation; the definition itself does not identify who currently performs the work.
A role can have automatic-assignment settings, including assignment for a qualifying first contact. Catalogue activity and ordering help govern eligible choices and automatic use. Existing holders and organization policy references retain the role's meaning even when its future use changes.
Why It Exists
Our reading is that association responsibilities need a shared meaning to support both staff interpretation and organizational policy. If each contact carries a free-form title as the only explanation, staff cannot consistently count billing representatives or select notice recipients by responsibility. A reusable role connects dated individual work to the workspace's expectations without treating every person with a similar job title as equivalent.
What It Is Not
A Contact Role is not a Platform security role and grants no application permission by itself. It is also not the person's job title or their affiliation type. Billing Contact describes responsibility within an organizational tie; Employer describes the kind of tie. A role period is a facet of the affiliation, carrying when this particular holder performs the responsibility.
What It Controls
Role definitions determine the responsibility choices and the identity used by dated role validation. Automatic flags can supply eligible assignments on new qualifying relationships or their start-day processing, subject to contact status, locks, and organization-type restrictions. Repeated processing does not restore a deliberately removed automatic responsibility.
Organization Type can name roles in its allowed list, coverage rules, and notification selection. Organization Compliance counts effective holders by role and selects applicable recipients. Current and historical holders or policy references can block deleting the definition. Catalogue order affects staff choice presentation; a customer lock protects content or deletion separately from its position in that order.
How It Is Used
The CRM Administrator maintains the role catalogue, while the CRM Editor gives people dated responsibility periods through Maintain responsibilities on organizational relationships. The CRM Reader inspects held roles in person and organization relationship views. Good use separates an allowed responsibility from a required coverage count and distinguishes the catalogue entry from each individual period of service, especially when someone leaves and later returns.
Example
A member firm type requires a Billing Contact and selects that role for compliance notices. Ruth holds it on her current firm affiliation, so the assessment can count her as a billing representative. Ending that period changes effective coverage without deleting the role definition. If she returns later, a new period preserves the earlier service gap rather than claiming continuous responsibility.
How It Relates
Contact Role belongs to the classification catalogue and is held within Affiliation. Organization Type can restrict or require it; Organization Compliance evaluates its current holders and notification recipients. Contact supplies the holder identity and primary e-mail. Record Protection and History explains supported role locks and audited changes. Platform security roles remain a separate access model whose similar name must not obscure the distinction.