# Single owner across multiple records

**URL:** <https://community.hubspot.com/t/single-owner-across-multiple-records/79318>\
**Category:** CRM\
**Tags:** workflows\
**Created:** [April 13, 2023, 8:01pm UTC](https://community.hubspot.com/t/single-owner-across-multiple-records/79318 "2023-04-13T20:01:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinyoliver](https://avatars.discourse-cdn.com/v4/letter/v/b9e5f3/32.png) [@vinyoliver](https://community.hubspot.com/u/vinyoliver)\
**Post date:** [April 13, 2023, 8:01pm UTC](https://community.hubspot.com/t/single-owner-across-multiple-records/79318/1 "2023-04-13T20:01:08Z")

</div>

Hey guys,

We’d like to have a single owner for contact, company, and deal. So whenever the owner of one of them is updated, we should reflect the change in the others records associated with it.

Eg. If I change the owner of a deal from Michelle to Richard, the associated company and contacts of this deal should also change the owner to Richard.

Is this something we can do?

Cheers.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [April 14, 2023, 4:48am UTC](https://community.hubspot.com/t/single-owner-across-multiple-records/79318/2 "2023-04-14T04:48:12Z")

</div>

Hi @vinyoliver,

There isn’t any default setting for this but it can be achieved using workflows.

Here’s how it would have to be approached:

- There needs to be a workflow for each object. A contact-based workflow that copies the contact owner into the deal owner, company owner, ticket owner field. A company-based workflow that copies the company owner into the contact owner, deal owner, ticket owner field. And so on.
- To ensure that each change triggers the copy workflows, each workflow re-enrolls records based on “[record] owner is known”.
- The main challenge is preventing a loop, so that workflows aren’t going in circlees. This can be achieved with a branch and a custom property that is set by the workflow of origin and labels the change as automated.

This is what a contact-based workflow could look like. (You would have to replicate the same workflow for companies, deals, tickets.)

 ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/1/3/1319a8091aa32e432982270097b94ee75b692c1d.png)

I haven’t tested this (so you should) but I’m fairly confident it works.

The workflow now updates all records within 1 level of relationship – but it doesn’t trickle down to further associations. For example, if you update a contact, all records associated to the contact will updated. However, the contacts associated with the company won’t be. (I don’t think that’s possible without creating a loop and without custom code actions.)

Best regards!

---

<div class="post-metadata">

**Author:** ![vinyoliver](https://avatars.discourse-cdn.com/v4/letter/v/b9e5f3/32.png) [@vinyoliver](https://community.hubspot.com/u/vinyoliver)\
**Post date:** [April 14, 2023, 6:25pm UTC](https://community.hubspot.com/t/single-owner-across-multiple-records/79318/3 "2023-04-14T18:25:39Z")

</div>

Hi @karstenkoehler,

thanks for your help! I’m trying to create a simpler workflow based on your answer where the company is the single source of truth for the owner. This way, the company owner should be the owner for the associated deals and contacts as well.

Unfortunately, looks like the workflow is not able to overwrite the current owner of the contact or deal record. It only works when the contact or deal does not already have an owner associated with it.

 ![vinyoliver_0-1681496605532.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/6/d673a52ab47ce93cf089399cb2963014ab56b218.png)

Any suggestions about how to fix that?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [April 14, 2023, 6:41pm UTC](https://community.hubspot.com/t/single-owner-across-multiple-records/79318/4 "2023-04-14T18:41:27Z")

</div>

Hi @vinyoliver,

Your workflow is a **contact** -based workflow, not a **company** -based workflow. It needs to be a **company** -based workflow that has **re-enrollment enabled** for the enrollment trigger “Company owner is known”, otherwise this won’t work.

The only action in this workflow would then be “Copy company owner into contact owner”.

Best regards!

---

<div class="post-metadata">

**Author:** ![vinyoliver](https://avatars.discourse-cdn.com/v4/letter/v/b9e5f3/32.png) [@vinyoliver](https://community.hubspot.com/u/vinyoliver)\
**Post date:** [April 14, 2023, 7:24pm UTC](https://community.hubspot.com/t/single-owner-across-multiple-records/79318/5 "2023-04-14T19:24:34Z")

</div>

Hi @karstenkoehler

I tried the suggestion above but it didn’t work.

Any ideas about what am I missing?

 ![89247iB11C80B466D53281.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/1/0/10de676ea568cce2a4d620ff8c65d2e2009f5c6d.png)

---

<div class="post-metadata">

**Author:** ![vinyoliver](https://avatars.discourse-cdn.com/v4/letter/v/b9e5f3/32.png) [@vinyoliver](https://community.hubspot.com/u/vinyoliver)\
**Post date:** [April 14, 2023, 9:34pm UTC](https://community.hubspot.com/t/single-owner-across-multiple-records/79318/6 "2023-04-14T21:34:49Z")

</div>

I’ve managed to achieve the desired outcome. Looks like the secret lies in the **re-enrollment enabled**

Although, I had to keep one workflow for each record type. Assuming the company is the single source of truth for the owner.

Here it’s an example. This way, whenever I update the company owner or associate the contact with the company, the company owner will be set into the contact.

 ![89256i2CF4A8A96CCFEB1A.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/a/d/ad344bf4b64540afb2883c1570ed45c8ff1ea5bd.png)

 ![89257i5D5C7A8EF7BC4BE8.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/6/f/6fba4164edf2ae3a59d55b9342f3a800afb7a348.png)

thanks @karstenkoehler for the support!
