About this question
I just started a project at a new company who is configuring a new Salesforce org. I've learned that they are planning on using only one Profile for what currently looks like 3 different personas (each persona has different CRUD needs on various objects).
They are planning on using Permissions Sets to control any/all access to objects. At the moment, the reason for this is "that's the way [our company] does it".
I know enough to know that this is unusual, and may have significant long-term costs that they're not considering (for example, Field Level Security can't be assigned via Permission Set), but need some 'official' list of reasons to use Profiles--along with Permission sets--to control object access for different personas.
Is there a list, for example, of Salesforce features that are only assignable (without code) using Profiles (like FLS)?
Better yet, any Salesforce-sponsored articles explaining why you'd use both, and not just rely on Perm Sets for everything....Or what the best practices are for using either, based on business requirement?
