We are working on a portal app that will run inside a Community and the limited sharing rule capabilities of the lowest priced Communities licenses is making life difficult, particularly as this app is an "add-on" to existing live production orgs. The app does lock down its own access in code by always linking back to and checking the Contact being accessed.
Two alternatives come to mind:
- The least likely to be misconfigured approach would be to make all the Apex classes
- We could also mandate that "View All" and "Modify All" be granted in the profile or permission sets.
If you have experience or insight into how a Salesforce Security review would regard either of these approaches, please post an answer.