Apex doesn’t enforce object-level and field-level permissions by default, you can enforce these permissions in your SOQL queries by using WITH SECURITY_ENFORCED. You can also enforce object-level and field-level permissions in your code by explicitly calling the sObject describe result methods (of Schema.DescribeSObjectResult) and the field describe result methods (of Schema.DescribeFieldResult) that check the current user’s access permission levels. In this way, you can verify if the current user has the necessary permissions, and only if he or she has sufficient permissions, you can then perform a specific DML operation or a query. For example, you can call the isAccessible, isCreateable, or isUpdateable methods of Schema.DescribeSObjectResult to verify whether the current user has read, create, or update access to an sObject, respectively. To check the field-level update permission of the contact’s email field before updating it:

1. if (Schema.sObjectType.Contact.fields.Email.isUpdateable()) {
2. // Update contact phone number

3. } To check the field-level create permission of the contact’s email field before creating a new contact:
1. if (Schema.sObjectType.Contact.fields.Email.isCreateable()) {
2. // Create new contact
3. }

To check the field-level read permission of the contact’s email field before querying for this field:

1. if (Schema.sObjectType.Contact.fields.Email.isAccessible()) {
2. Contact c = [SELECT Email FROM Contact WHERE Id= :Id];
3. }

To check the object-level permission for the contact before deleting the contact:
1. if (Schema.sObjectType.Contact.isDeletable()) {
2. // Delete contact
3. }