Salesforce Fact #954 | Transaction Security Policy on LoginAs event

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.




Comments

  1. NitaNovember 29, 2025 at 4:39 PM

    Great post! This Salesforce fact is insightful and highlights the importance of managing data effectively within the platform. For teams working across multiple CRMs, it’s equally useful to understand how to migrate data from Salesforce to Zoho CRM safely and efficiently. Thanks for sharing such valuable information — looking forward to more Salesforce tips like this!

    ReplyDelete

Post a Comment

Popular posts from this blog

Salesforce Fact #913 | Access selected record field values in screen flow lookup w/o Get Records

Image
Suppose we are using the Lookup element in the screen flow and once a record is selected, we would like to get the value from other fields. Now, Lookup provides record Id and record Name field values by default. So in order to get the other field value we need to use a Get Records. But hold on! There is an option to get the field values without using a Get Records element. We need to define a child sobject variable and then in the advanced section, set the parent field Id with the record Id of the selected record in Lookup. In this example, we have a lookup of Account record and we are using a Contact record variable and setting the AccountId field with the selected record Id and later on accessing the field values from account. Attached are the screenshots.
Read more