Each core CRM object has a default owner property: contact owner, company owner, deal owner and ticket owner. The property holds one active user at a time. Admins can also create extra user properties, for example a customer success owner on companies, when more than one person needs to be named on a record.
Ownership drives more than a name on the record. Permissions can limit users to the records they own or their team owns. Workflows, forms and chat routing assign owners to new records, and owners receive notifications and tasks for their records. Most sales and service reports group by owner, so performance, pipeline and workload numbers all depend on the field being set.
Gaps in ownership are common and expensive. Records created by imports, integrations or forms without routing rules often have no owner at all. When someone leaves the company, their records can be left with an inactive owner, or none, unless someone reassigns them. In both cases nobody gets the follow-up task, and the record disappears from every rep’s view.
Teams that manage ownership well decide who owns each object at each stage, assign owners automatically on creation, and keep owners consistent across associated records where that makes sense, such as a company and its open deals. When a user is deactivated, reassigning their records is a step in the offboarding checklist, not an afterthought.
Example
Thistle Insurance Brokers, a fictional firm, deactivated two departing reps without reassigning their records. Six weeks later, 85 open deals and 1,400 contacts had an inactive owner, and inbound replies were going unanswered. The ops lead reassigned them by territory and added owner reassignment to the offboarding checklist.