[Alex MedvedevParticipant]

Yes, i’ve considered approach to change ownership type on my side just like you say above, but this can be conflict-dangerous during further ORO updates since such things affect vendor db schema and entity config in fact. Therefor i’ve choosen to have ‘system’ user hardly related to each BU to link entities to whole BU if needed until we cannot change entities ownership type out of the box in ORO.

Thank you for conversation.

[Alex MedvedevParticipant]

No, i want to divide responsibilities between business units.

Suppose there are 2 sets of different Contacts (or Accounts): A and B
and 2 Business Units: C and D.

I need to make Contacts/Accounts from A viewable/editable by participants of business unit C, but not of D and
Contacts/Accounts from B viewable/editable by participants of D, but not of C.

Btw i use more extended structure with hierarchical BU’s, but in simplified view it looks just like i described above.

So IMHO ability to change ownership type for Contacts/Accounts (and ideally for any other built-in entities) can solve this case pretty elegant, as i mentioned above)

[Alex MedvedevParticipant]

Thanks, Yevhen!

Yes, ability to change such thing as ownership type sounds as a great thing, but from the other side it is obviously not so trivial since this config is tightly related to db schema (in fact to relation constraints between the entities), so may be it can be done with the help of migrations.

In my use case the person could be moved to another business unit due to promotion (movement to parent BU), demotion (movement to child BU) or horizontal displacement in the position (movement to generally unrelated BU) and this case should not affect any permissions to view or deal by users from original business unit of replaced user with entities (Contacts or Accounts for example) ownered by replaced user.

[Author]

Replies