New answers tagged


To get this out of the way, this question is very broad, and it's unlikely I or anyone else can fully address it in the scope of a single answer. Further, the "right" solution is most certainly product-specific, and many different choices in product architecture may influence the final design decisions. With that said, here are my thoughts. ...


With Sharing and without sharing is not related to CRUD access. Regardless of the sharing mode, enforce object-level access and field-level security in your SOQL queries or code. For example, with sharing mechanism doesn’t enforce user’s access to view ...


After much investigation through trial and error, I have discovered the permission required for this to work. For some reason that I don't really understand, the required permission is.... drumroll... Manage Users


There are often situations where there's a one-off use case where a user persona needs access to data but they shouldn't have blanket access to those objects/fields via OLS/FLS. When reviewing the code from a security perspective static analysis tools such as PMD are often used. If it is really appropriate in this case for the Guest User to have access to ...


The main way to avoid leaks in the current system is to use Security.stripInaccessible. Using this ensures that you will not be in violation of Security Review problem.


For users running into this error on custom profiles, you will have to enable the new permission introduced in Winter '22 called View DeveloperName in your sandbox. This is mentioned in Grant Access to the DeveloperName Field to Users Who Required It. Standard profiles (with Salesforce User License) will have this enabled for them with the release (as they ...


with sharing only enforces record level sharing. It does not check for field permissions or object permissions for the user. For example, it is possible to query for records on objects the user has no access to, as sharing doesn't account for profile and permission set permissions. In addition, a user can technically modify a record (e.g. the user has Edit ...


Createable means that the user can put a value in this field when they are creating a new record. Updateable means that the user can put a new value in this field when they are editing a record. If a user has Edit permission on a field, normally Createable and Updateable will both be true. However, there are times when this won't be true. For example, a ...


Updatable for a field means the user has update permission for the object containing the field and has edit permission for the field. Creatable for a field means the user has create permission for the object containing the field and has edit permission for the field.

Top 50 recent answers are included