Hi,
I have a user that can read but not edit Account records which I want. However, once I relate the Account record to a "Property Role" custom object record then the user gets to edit the Account and the Contact.(I want them to edit the Property Role fields and be able to relate them but not the Account or Contact fields). Even if they don't own the Account and if I delete the lookup relationship, the user can still edit the Account and Contact. I would think since they were not able to edit this Account prior to it getting related then once the relationship gets deleted then the edit access would be removed but it isn't.
I have a custom object name Property Role which has a lookup field to Account and is the detail object to a Master Detail object called Property. I'm trying to avoid duplicate Accounts and prevent some users from editing those fields but also giving them the ability to relate Accounts to Property Roles. Any help is appreciated!
Something doesn't sound right in what you're describing. There's no standard sharing capability that would grant access to an account record that is being referenced via a lookup, except sharing sets...but that would need to be setup different than how you have things setup.
So I think the first thing you should do is figure out where this edit access to the account record is coming from. Check the sharing details on an example account record and look at the sharing reasons...is there custom apex sharing in place? is it ownership? is it manual sharing? etc.
