Configure an affiliation type and use it on a contact
Story
A CRM Administrator introduces Member Firm as a new kind of affiliation for the association. She supplies its description and default mappings from the firm's billing address and main phone to the person's work details, then chooses it as the workspace default. The catalogue now offers that relationship vocabulary for later contact work.
A subsequent Organization command on a contact omits an explicit affiliation type and uses Member Firm. The administrator checks the contact editor's new-affiliation selector and Link When Added choices, connecting configuration to the staff experience rather than stopping at catalogue creation.
She also tests retirement. Deletion is refused while the type is selected as default or referenced by affiliations. Resetting the default and deactivating Member Firm preserves existing ties while removing it from new selection. Configuration changes govern later use without retroactively replacing existing people's relationship meaning.
Duplicate destination mappings refuse creation because they would compete for one contact slot. A caller without set-default authority cannot change the workspace default. The frontmatter also includes catalogue-administration variants for contact roles and for a contact type deactivated after selection; these illustrate related retirement behavior, but they are distinct from configuring the Member Firm relationship itself.
For Ruth Kim at Harbor Engineering, the administrator checks the later Organization command's result rather than assuming the configuration list proves contact behavior. The saved affiliation uses Member Firm, and the configured work-detail sources remain associated with that tie. If she later retires Member Firm, Ruth's retained relationship explains its earlier meaning. A fresh selector and an existing affiliation therefore provide two different checks of the retirement outcome.
What Is True Afterwards
The Organization command uses the configured workspace relationship type when it needs a default, and the contact editor exposes the applicable sharing choices. After retirement, existing affiliations keep their type and new choices exclude it. Default and reference checks prevent deletion from removing meaning still in use. The administrator has changed future selection without claiming a rewrite of prior affiliations or complete proof of every saved-query path.