Skip to main content

Salesforce Lightning Platform Security and Sharing

Salesforce Lightning Platform Security and Sharing

Motivation behind this


Many a times, I thought of having a single glance of Security and Sharing architecture, but over the net I couldn't find it as a simple single flow. I am trying to portray this flow on best of my knowledge.

In the below flow, I am trying to showcase what the different layers of Platform Security and when a user tries on login to Salesforce what are the various steps come to play. 

After successful login, if that user tries to access the record then how Object level, field level security comes into picture.

Obviously, in a private sharing model, data or record sharing is always in demand and how that can be achievable.

Finally, to showcase transport layer security, if the user wants to send data from Salesforce to external system how different steps occur is good to know.

The following picture might help those aspirants who are preparing for Admin, Sales Cloud and Integration Architecture certifications.

Comments

Post a Comment

Popular posts from this blog

How to Build a Basic Salesforce REST API (With Test Class)

How to Build a Basic Salesforce REST API (With Test Class) and Test with POSTMAN Salesforce : Creating Anonymous Apex REST APIs with Force.com The Force.com REST API lets you integration with Force.com applications using standard HTTP methods. This API provides a way to expose the data you have within your Force.com application to external applications – both mobile and non-mobile. A few useful bits of information related to these REST APIs: This sample Code you how to implement a simple REST API to fetch Account in Apex class: @RestResource(urlMapping='/Account/*') global with sharing class MyRestResource { @HttpGet global static Account doGet() { RestRequest req = RestContext.request ; RestResponse res = RestContext.response ; String accountId = req.requestURI. substring ( req.requestURI. lastIndexOf ( '/' ) +1 ) ; Account result = [SELECT Id, Name, Phone, Website FROM Account WHERE Id = : account...
Post a Comment
Read more

Salesforce Callout using Future Method

Hi All, Today's topic , Use of Future method in web services callout. Consider one scenario, Whenever ,We create one Account record or Edit a Account record using UI, Populate Billing city based on Billing Zipcode . Like Below image before save, After Press the save button,Billing city should auto populate. We want to populate Billing city based on Billing zipcode using below API endpoint. Postal PIN Code API Postal PIN Code API allows developers to get details of Post Office by searching Postal PIN Code or Post Office Branch Name of India. It has following format:         1. Get Post Office(s) details search by Postal PIN Code             http://postalpincode.in/api/pincode/{PINCODE}         2.Get Post Office(s) details search by Post Office branch name            http://postalpincode.in...
1 comment
Read more

Salesforce UNABLE_TO_LOCK_ROW: unable to obtain exclusive access to this record

Unable to lock row - Record currently unavailable errors Description When a record is being updated or created, we place a lock on that record to prevent another operation from updating the record at the same time and causing inconsistencies on the data. These locks normally last for a few seconds and when the lock is released, other operations can do whatever processing they are supposed to do on the record in question. However, a given transaction can only wait a maximum of 10 seconds for a lock to be released, otherwise it will time out. Resolution What and when records get locked depends on the operation you are performing and the main record you are working on. The  Force.com Record Locking Cheatsheet   provides detailed information on this and it's highly recommended that you familiarize yourself with its contents. Common Scenarios that prevent unlocking record a. Email-To-Case When an email is processed by email-to-case, triggers on the email mes...
Post a Comment
Read more