Object-level Create Read Edit Delete permissions
Key Takeaway
User access is the intersection of object permissions and sharing, so a user needs both to work with a record.
Object permissions are the base layer of data access in Salesforce. For each object, they decide whether a user can create, read, edit, or delete that kind of record at all. Sharing settings then decide which individual records the user can reach.
The four object permissions
An object is a collection of records, such as leads or contacts. Object permissions set a user's base-level access to each object, so they answer "can this user work with leads at all?" rather than "which leads?".
The four permissions are Read, Create, Edit, and Delete, and they build on each other:
| Object permission | What it lets users do |
|---|---|
| Read | Only view records |
| Create | Read and create records |
| Edit | Read and edit records |
| Delete | Read, edit, and delete records |
For example, imagine recruiters who must create, view, and edit candidate records. They must never accidentally delete a candidate record, because the law requires those records to be kept. The right setup grants Read, Create, and Edit on the object and leaves Delete off.