Looked with searching and did not find a suggestion for this scenario:
We would have three countries, with three different ERP's, so databases in EspoCRM would be distinct. A user from country ABC, would not be interested in events, like quotes in country GGG - but they would have the exact same user interface. And maybe sales managers could be interested in total overview to all countries.
I would try to install three instances of the CRM, like ABC.company.com / GGG.company.com with a clear distinction between users, customers etc.
But then my worry would be, that if we would like to add an entity into customer, we just need to do it three times? Or could those three databases be connected somehow, that if I would create an entity in one, all three would be populated with it?
Perhaps using a cron job and copying? Entity Manager - EspoCRM Documentation
That might solve the entity "issue" if I am not mistaken of the purpose in that function. And maybe Layouts also would be a copy from one folder to another?
Or, it could all be running on one instance, but just some other means of limiting what the user would see? Teams?
I mean that a user in country ABC would not even see a customer that is originating from country GGG and defined to "Team" GGG. Not able to search, see records etc.
With the one instance method, we could generate a report for sales managers that would show all countries at once.
We would have three countries, with three different ERP's, so databases in EspoCRM would be distinct. A user from country ABC, would not be interested in events, like quotes in country GGG - but they would have the exact same user interface. And maybe sales managers could be interested in total overview to all countries.
I would try to install three instances of the CRM, like ABC.company.com / GGG.company.com with a clear distinction between users, customers etc.
But then my worry would be, that if we would like to add an entity into customer, we just need to do it three times? Or could those three databases be connected somehow, that if I would create an entity in one, all three would be populated with it?
Perhaps using a cron job and copying? Entity Manager - EspoCRM Documentation
That might solve the entity "issue" if I am not mistaken of the purpose in that function. And maybe Layouts also would be a copy from one folder to another?
Or, it could all be running on one instance, but just some other means of limiting what the user would see? Teams?
I mean that a user in country ABC would not even see a customer that is originating from country GGG and defined to "Team" GGG. Not able to search, see records etc.
With the one instance method, we could generate a report for sales managers that would show all countries at once.
Comment