# Multiple Owners for a contact

**URL:** <https://forum.mautic.org/t/multiple-owners-for-a-contact/25223>\
**Category:** Ideas and Feature Requests\
**Created:** [August 30, 2022, 12:02am UTC](https://forum.mautic.org/t/multiple-owners-for-a-contact/25223 "2022-08-30T00:02:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jessebrightman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/jessebrightman/32/9646_2.png) [@jessebrightman](https://forum.mautic.org/u/jessebrightman)\
**Post date:** [August 30, 2022, 12:02am UTC](https://forum.mautic.org/t/multiple-owners-for-a-contact/25223/1 "2022-08-30T00:02:02Z")

</div>

My idea is: Multiple owners for a contact. We work in a team environment where multiple agents will be working on the same file and will therefore be sharing any leads.

I think these groups of people would benefit from this idea: Any company that shares leads.

Why I think they would benefit from this idea: It seems like a simple data type change.

Any code or resources to support this idea: Other systems utilize this idea out of the box.

Are you willing to work on this idea?: Yes.

What skills and resources do you need to explore this further? I can’t imagine this has never come up before. It seems like a basic data type storage issue and a viable use case. I have not worked with Mautic specifically before but I have the ability to do so.

Thanks.

---

<div class="post-metadata">

**Author:** ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)\
**Post date:** [April 12, 2023, 4:36pm UTC](https://forum.mautic.org/t/multiple-owners-for-a-contact/25223/2 "2023-04-12T16:36:25Z")

</div>

Hi! You can always create a custom field, with a value: opened by company one / opened by company two.  
What particular functionality do you miss?

---

<div class="post-metadata">

**Author:** ![jessebrightman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/jessebrightman/32/9646_2.png) [@jessebrightman](https://forum.mautic.org/u/jessebrightman)\
**Post date:** [April 12, 2023, 5:10pm UTC](https://forum.mautic.org/t/multiple-owners-for-a-contact/25223/3 "2023-04-12T17:10:21Z")

</div>

Hi joeyk,

Thanks for the reply and for all your tireless efforts running this great ship called Mautic. I currently use it with multiple clients and many 100’s of thousands of contacts and would like to give back to the community in any way I can.

One client in particular is a real estate firm where sometimes a contact could be shared by multiple agents or by a team. The situation can arise when one agent gets an inquiry from an existing contact that also already belongs to another agent/inquiry. This causes the contact to change ownership and the first agent agent cannot follow-up or access the contact any longer. I am currently experimenting with additional custom fields with the unique attribute based on the agent id and email combination.

My original idea was to look at the Contact Owner field and see what it would take to make it an array of ids instead of just one id field (int). Of course, that would be a massive undertaking (interfaces/poly’s) across the entire platform so that’s kind of where that idea died. Nonetheless, I thought it was worth putting it out to the community in case anyone else came across this use case or has any ideas to accomplish this.

Thanks again for the reply and the ideas and I’m looking forward to the new versions!

All the best,

Jesse

---

<div class="post-metadata">

**Author:** ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)\
**Post date:** [April 12, 2023, 9:18pm UTC](https://forum.mautic.org/t/multiple-owners-for-a-contact/25223/4 "2023-04-12T21:18:42Z")

</div>

Hi, I think the undertaking is way too large. I don’t know any good way around it. You would need to seriously change the way ownership works…

---

<div class="post-metadata">

**Author:** ![samuelfk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/samuelfk/32/12606_2.png) [@samuelfk](https://forum.mautic.org/u/samuelfk)\
**Post date:** [November 19, 2024, 8:47am UTC](https://forum.mautic.org/t/multiple-owners-for-a-contact/25223/5 "2024-11-19T08:47:27Z")

</div>

Hi, just a follow up question in this thread: any plans regarding multiple owners for the future?

We have the problem that we are multiple organizations part of an international movement using the same Mautic instance, it is important that the individual organizations own their own contacts and are the only one that can access them and contact them.

However, sometimes contacts want to be part of two or more organizations, then this organization will “steal” the contact from the old one, which is not working.

I think multiple are the only solution then, due to how the permission system is working?

---

<div class="post-metadata">

**Author:** ![samuelfk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/samuelfk/32/12606_2.png) [@samuelfk](https://forum.mautic.org/u/samuelfk)\
**Post date:** [November 19, 2024, 8:56am UTC](https://forum.mautic.org/t/multiple-owners-for-a-contact/25223/6 "2024-11-19T08:56:40Z")

</div>

I found a possible solution here!

> [@Same Email - Different Owners](https://forum.mautic.org/t/same-email-different-owners/28425/3):
>
> So by default Mautic unique identifier is email, this can however be changed to anything else you want. We had numerous user cases where the client wanted to have multiple contacts with the same email address (for whatever reason, it is less relevant) and what we did was set a different field as the unique identifier, in our case we had something like unique\_contact\_id. For us it was easy as the customer was generating their own unique\_contact\_id’s however a simple script in the middle can do …

To use another unique ID for the contact and then let all organisations have their own instance of the contact. It is better than nothing, but multiple owners would still be a much better option I think to not spread out contact data on different instances of the contact.
