Hello All, I'm working on an inventory of my org's users. In looking at the custom profiles in the org (I'm just over a month new to this role!), I am curious to hear from the community regarding your use of custom and standard profiles.
Would you create custom profiles if the business model begs for them? OR, would you use a standard profile and perm sets/groups to build it out [regardless]?
These questions stem from the idea that standard profiles may get updated from release to release, which I could see helpful in keeping up with the latest functionality. But, I can also see that perhaps the latest functionality isn't needed.
Would anyone have any insight or preference based on experience here? If you have a case where one worked better or not, I would love to hear about it! Thank you for reading!
#Solo Admins #Best Practices #Best Practices Advice #ImpostorSyndrome #AwesomeAdmins
Michael Brown (Salesforce) 
Forum Ambassador
Hi Laura,
As great as the standard profiles are, I've never found them to work because the one limit is that they don't get access to custom objects, and every org I've worked in has at least 1 custom object. Because of that, I usually clone a standard profile into a new custom profile. If you're using entirely native objects, I think standard profiles are a way to go, but that almost never happens.
As far as keeping up to date with latest functionality, the major releases and impacts are made well aware of well in advance, and there is plenty of documentation to help you update profiles accordingly, but for the most part I've found that there is very little impact at the profile level with release updates.
Thanks,
Mikey
