> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing-rules/ownership-rules.md).
# Ownership rules
Use an ownership rule to keep a prospect with an existing CRM owner or assign matching prospects to a specific teammate.
Open **Form routing → Ownership Rules → New Ownership Rule**. The editor has **Basics**, **Conditions**, and **Assignment** steps.
## Choose the CRM match
In **Basics**, enter a **Rule name** and choose the CRM record to look up. Available choices depend on your integration: HubSpot contacts or companies, or Salesforce contacts, accounts, or leads.
For person records, exact matching uses the prospect's email. Fuzzy matching tries the exact email first, then a domain fallback. Company or account matching uses the email domain. A domain match can identify a different person at the same company, so use it only when that relationship is appropriate for your routing.
## Add conditions
Use **Conditions** to narrow when the match applies. Choose the field, comparison operator, and value. Use **AND** when every condition must match and **OR** when any condition can match. For example, require both an existing CRM relationship and an enterprise company size.
The CRM lookup runs first. Additional conditions narrow that result before assignment.
## Select the host
Under **Meeting assignment**, choose:
| Option | Required setting |
| ------------------------ | -------------------------------------------------------------------------------- |
| **Matched record owner** | **Owner property to read** identifies the teammate who owns the matched record. |
| **Specific user** | **Teammate** identifies the person who should always receive matching prospects. |
The selected owner must correspond to a usable Distro teammate. Check the CRM member mapping and calendar connection when an expected owner cannot receive the meeting.
## Update ownership and meeting details
**CRM owner sync → Update the record owner** writes the assignee back to the configured **Owner property to update**. This can run when the rule matches during routing, before a meeting is booked. It is separate from creating a CRM meeting activity. Vacation coverage does not update the original CRM owner.
Under **Advanced meeting options**, **Default guests** adds comma-separated email addresses to the invitation. Their calendars are not checked as required participants. **Override meeting settings** selects a different event type from the router default.
Save the rule, add it to the router, and review its priority. Use **Test route** and [activate the router version](/routing/router-versions.md) before relying on the change for new prospects.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.distro.so/routing-rules/ownership-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
