My idea is:
scenario: you have a company that has marketers dived into departments, each department can /edit specific leads/segments but not others.
we are considering adding new feature to Mautic core that would introduce departments. Each department would group together users (marketers), that are allowed to view and otherwise manipulate leads that are assigned to department the user is in.
On lead view there would be additional field, let’s say »Departments«, where you would specify which departments can view/manipulate the lead data.
One lead could belong to more than one department, but the user (marketer would only belong to one department).
This allows us to get multiple owners on one lead. I want to leave the owner functionality intact as I do not really know what side effects it brings if we suddenly change the relationship between the lead and the owner.
I would also suggest that the department functionality is opt-in feature, because this feature makes queries bigger and if the user does not really need it, why complicate the queries, so there would be a setting in Mautic allowing us to toggle functionality on/off.
Creating a view where we could add departments and users into departments and creating appropriate database schema for it, is not a problem for me.
What is a little bit unclear at this point is how much of existing Mautic core would I need to update in order to make departments work. After my research I came to the conclusion that I would generally need to adjust two types of classes: models (getEntities) and controllers.
Mutli-owner functionality has already been suggested before, see here: < Multiple Owners for a contact > for details.
My questions for now:
Q1. Is this something Mautic team would be open to include to the core if we implement it?
Q2. Does my suggestion make sense, is my thinking about models and controllers correct or is there a hidden layer, something obvious that I have missed?
I think these groups of people would benefit from this idea:
Companies with multiple marketing departments where marketers should only see and work on leads they have been a signed to.
Why I think they would benefit from this idea:
Because at the moment you can only see all leads (administrator) and your own leads (owner). You do not want to give all people admin access and you cannot have more then one owner.
Any code or resources to support this idea:
[not for now]
Are you willing to work on this idea?:
What skills and resources do you need to explore this further?
For now, if I can just get answers to my questions above thats a good first step, but down the line if we decide to actually go into implementation, we should probably sync. with core development team to get clear about some implementation details.
Curious to read, what others think. Any suggestions and pointers are much appreciated.