Hi all! I think I can't get around this but I'm wondering if anyone has any ideas. I have two lines of business (line a and line b) and line b wants to see some information from line a. Previously this has not been needed or possible.
I have managed (using a looking field on the opportunity and a sharing rule) to make that happen. The problem is that if line b runs an account report (for example) they get line a info and we don't want that to happen. If I remove the sharing rule that makes this whole thing work - what I created falls apart.
I'm thinking the only way is do something thing that would require a LOT of work and probably involve bringing in a developer - one or more of the following
- custom dl account reference object
- screen flow search
- custom LWC
anyone have any other thoughts/ideas?
Thank you in advance as always for any help! :)
#Salesforce Admin #Salesforce #Sales Cloud #Automation
Hi @Bill Hare
I think the issue is related to Salesforce's record-level sharing model. A sharing rule that grants Line B access to Line A's Account records can also make those records available in Account reports.
Before building a custom LWC or Screen Flow, I would consider these options:
- Field-Level Security: If Line B should see the Account records but only specific information, use field-level security to hide sensitive fields. However, this won't prevent Line B from seeing the Account records themselves in reports.
- Restriction Rules: Check whether restriction rules are supported for the object and use case. They can filter records users can access, but they don't provide field-level access control and aren't available for every standard object.
- Custom Object: If Line B only needs a small subset of Line A's information, create a custom object containing only the information that Line B is allowed to access. Share those records with Line B without granting broad access to the original Account records.
- Custom UI: If Line B only needs to search for and view selected information, a custom LWC or Screen Flow could provide a controlled interface. Make sure the underlying Apex enforces the required access restrictions; hiding records in the UI alone is not a security boundary.
My recommendation would be to clarify whether Line B needs access to the entire Account record or only a few fields. If it is only a few fields, a separate custom object or a carefully designed sharing model may be cleaner than sharing the original Accounts.
Salesforce references:
- https://help.salesforce.com/s/articleView?id=platform.security_data_access.htm
- https://developer.salesforce.com/docs/platform/restriction-rules/guide/restriction-rules-about.html
I hope this helps! If you find this answer helpful, please select it as the Best Answer.
Thanks,
Deepak Sachdeva
Nubys Technology Pvt. Ltd.