Loading
Salesforce Enforces New Security Requirements in Summer 2026Read More
Manage Users and Data Access
Object Permissions

Object Permissions

Object permissions specify the base-level access users have to create, read, edit, and delete records for each object.

Required Editions

Available in: both Salesforce Classic and Lightning Experience
Available in: Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions

We recommend that you use permission sets and permission set groups to manage your users’ permissions. Because you can reuse smaller permission set building blocks, you can avoid creating dozens or even hundreds of profiles for each user and job function.

Object permissions either respect or override sharing rules and settings. The following permissions specify the access that users have to objects.

Permission Description Respects or Overrides Sharing?
Read Users can only view records of this type. Respects sharing
Create Users can read and create records. Respects sharing
Edit Users can read and update records. Respects sharing
Delete Users can read, edit, and delete records. Respects sharing
View All Records Users can view all records associated with this object, regardless of sharing settings. Overrides sharing
Modify All Records

Users can read, edit, delete, transfer, and approve all records associated with this object, regardless of sharing settings.

“Modify All Records” on documents allows access to all shared and public folders, but not the ability to edit folder properties or create folders. To edit folder properties and create folders, users must have the “Manage Public Documents” permission.

Overrides sharing
View All Fields Users can view all fields and field data in records of this type, regardless of assigned field permissions. To see an object’s fields, the user must also have at least Read permission. Respects sharing
Note
Note A profile or a permission set can have an object, such as Account, with a master-detail relationship. A broken permission dependency exists if the child object has permissions that the parent must have. For updates made in Setup, Salesforce updates the parent object for a broken permission dependency on the first save action for the profile or permission set. For updates made using the API, you must manually fix broken permission dependencies.
If the child object has these permissions These permissions are enabled on the parent object
Modify All Records OR View All Records View All Records
View All Records OR Read Read

You can see which permission sets, permission set groups, and profiles grant access to an object in Object Manager. You can also edit object access for custom permission sets and custom profiles. Select an object, and then click Object Access.

  • Manage Object Access in Object Manager
    See the permission sets, permission set groups, and profiles that grant access to an object, and the level of access granted. You can also update the object permissions enabled in custom permission sets and profiles.
  • “View All” and “Modify All” Permissions Overview
    The “View All” and “Modify All” permissions ignore sharing rules and settings, allowing administrators to grant access to records associated with a given object across the organization. “View All Records” and “Modify All Records” can be better alternatives to the “View All Data” and “Modify All Data” permissions.
  • Comparing Security Models
    To manage your users’ access to data, you can configure sharing settings, permissions, and other features.
 
Loading
Salesforce Help | Article