[SalesForce] how are custom object permissions set for standard profiles

I'm looking at the std profile, contract manager, and for some custom objects in our org, they have CRUD privileges for a bunch of objects and no access whatsoever to a bunch more. What drives the privileges to be set this way when it comes to standard profiles?

EDIT- oddly, enough I checked all 6 STD profiles and 4 of them had the same CRUD access to the same custom objects. Read-only could only read those same objects…

I suspect there maybe a historical thing going on here?

Best Answer

Standard Profiles come default with set User Permissions. User Profiles and their customizations are set based on the org type:

In Contact Manager, Group, and Professional Edition organizations, you can assign standard profiles to your users, but you can't view or edit the standard profiles or create custom profiles. In Enterprise, Unlimited, and Developer Edition organizations, you can use standard profiles, or create, edit, and delete custom profiles. For standard profiles, only certain settings can be changed.

Each standard or custom profile belongs to exactly one user license type.


Essentially, these profiles are set up and only some of them allow certain functionality. Not all of the profiles allow access to certain objects (specifically, profiles associated to Portals are very restrictive). This is just how the profiles are set up.

Related Topic