Salesforce Facts by Abhishek

There is a System permission 'Exempt from Transaction Security' which bypasses the triggering of transaction security policy. It can be added to profile or permission set level and assigned to the intended users. Note: This doesn't apply to LoginEvent type. Reference:  https://help.salesforce.com/s/articleView?id=xcloud.enhanced_transaction_security_exempt.htm&type=5

Sometimes we want the login as option to be restricted for one particular user like the integration user or deployment user in the org. We can create a transaction security policy on LoginAs event to impose the same. Note: The user Id should be 15 digit Id in the condition Attached is the screenshot.

We can use transaction security policy to prevent multiple users from logging into Salesforce. To implement this, we use the LoginEvent, an apex class and custom permission set. In this example, we have created a permission set 'Prevent Login PS' and in the apex class we are checking whether the user is assigned the PS or not. Note: Custom permission check does not work because in that case the context user is Automated user, not the intended user. Reference:  https://salesforce.stackexchange.com/questions/387530/featuremanagement-checkpermission-not-returning-expected-result Attached are the screenshots.

Suppose we want to restrict all the users from querying and extracting data from the Account object. We can create a transaction security policy on the API event for the same. Attached are the screenshots.

Permission for a flow is checked only at the top level. For example, flow A calls flow B. User X has a profile that can access flow A but not flow B. User X can execute flow B, but only through flow A. User X can’t execute flow B directly. Reference:  https://help.salesforce.com/s/articleView?id=sf.flow_distribute_security.htm&type=5