- Issue created by @jdleonard
- πΊπΈUnited States jdleonard Austin, TX, USA
Should a Contact Detail have a field representing the Contact that "owns" it? This would make the access control logic simpler as we could just delegate to
ContactAccessControlHandler
. Should that field be read only (would that interfere with future sharing)?I suppose we could still delegate to
ContactAccessControlHandler
without such a field, but it would require a query to find the Contact referencing the Contact Detail. I err on the side of setting a read only back reference as described above. - πΊπΈUnited States bluegeek9
Adding a contact reference field is how I would implement Detail sharing; it shouldn't interfere.
- πΊπΈUnited States bluegeek9
If a contact field is added to the contact detail, the contact form(s) will need to be updated. The add form can not create contact details because the contact id does not exist yet.
I think it is a blocking issue, just something we will need to address.
- Assigned to bluegeek9
- Merge request !83Issue #3525361 by bluegeek9: Address/Phone/Email CRUD access control β (Merged) created by bluegeek9
- πΊπΈUnited States bluegeek9
These are the permissions that allow users to create contact details. Should we add additional permissions?
$permissions = [ 'create crm_contact', 'edit any crm_contact', 'administer crm', ];
- πΊπΈUnited States bluegeek9
bluegeek9 β changed the visibility of the branch 1.0.x to hidden.
-
bluegeek9 β
committed dc45e9c8 on 1.0.x
Issue #3525361: Address/Phone/Email CRUD access control
-
bluegeek9 β
committed dc45e9c8 on 1.0.x
- 08a3250d committed on 1.0.x
Issue #3525361 by bluegeek9: Address/Phone/Email CRUD access control
- 08a3250d committed on 1.0.x