Custom Object Permissions Off by Default
|Knowledge Article Number||000005198|
In the Spring ’10 release, when you create a new custom object, the “Read,” “Create,” “Edit,” “Delete,” “View All,” and “Modify All” permissions for that object are disabled by default. You must specify which users should get access to custom objects. This is only applicable in organizations with customizable profiles (Enterprise, Unlimited, and Developer edition, since the introduction of our Lightning Edition, this now also applies to Lightning Professional Edition)
|Resolution||You can only change the object permissions for custom profiles, not standard profiles. As a result, users with standard profiles (except System Administrator) can't access custom objects created after the Spring ’10 release.
If you have users assigned to standard profiles, clone these profiles and reassign your users to the newly created profiles. Then, when you create a new custom object, you'll edit the user profiles to enable object permissions. Additionally, you can use enhanced profile management to edit multiple profiles at once.
For custom objects created before the Spring ’10 release, access to these objects won't change. Therefore, standard profiles will continue to have access to custom objects created prior to the Spring ’10 release.