How to Fix Permission Denied Errors

You see a “Permission denied” or “Access denied” error when trying to view, create, edit, or delete a record.

Common causes

1. Your profile doesn’t have access to this entity. Each security profile defines which entities a user can access and what actions they can perform (Read, Create, Update, Delete).

2. You have read access but not write access. You may be able to view records but not edit or delete them.

3. Field-level security is restricting a specific field. Even if you can edit the record, certain sensitive fields (e.g., revenue, salary) may be restricted for your profile.

4. Record ownership rules apply. Some configurations restrict users to only see their own records, not records owned by other team members.

5. The entity is in a restricted state. Records in certain states (e.g., Archived) may have limited edit permissions.

Step-by-step fix

1. Note the exact error message and where it appeared (which entity, which action).
2. Ask your administrator to go to Settings > Profiles and select your profile.
3. Check the Entity Permissions tab for the entity in question. Verify that your profile has the appropriate permission level (Read, Create, Update, Delete).
4. If you can view the record but not edit a specific field, check the Field Permissions section for field-level restrictions.
5. If you can see some records but not others, check whether Record Scope is set to “Own records only” vs. “All records” for your profile.
6. Save any permission changes. The user may need to log out and back in for permission changes to take effect.

Still stuck?

Permission denied errors always come down to profile configuration. If your administrator confirms your profile should have access and it still doesn’t work, try logging out and back in to refresh the permission cache. If the issue persists, ask your administrator to check the permission cache in Settings > System.