Beruflich Dokumente
Kultur Dokumente
Object Level - CRED - Box of Records Create an object = Box that holds records, CRED = Object Sectary -
Who has access to any records in the is box. Default on new custom object is only Admins
When designing App design Schema - What is the Object security for any object I am using in the
App. Correspond to the People who use this app, which points to profile. Do Some profiles only need
Read only then give them R, If CRED is blank for Profile then they can't see any records. You can also
share via permission sets
Field level security - FLS- Block or open via Profile or Permission set. We can block certain fields on an
object
Record level: Sharing - OWD's set based level per objects, numerous ways to Open up access. So if the
Profile has CRED but may only be able to read some records, or Read, edit records.
OBJECT - MANDITORY
FIELD - OPTIONAL
RECORD - OPTIONAL
RECORDs: Sharing:
Role Hierarchy - makes records accessible to anyone Higher up in the Role Structure (Does not
necessary need to mimic your actual Org Structure) (vertical)
We can use them or not, even though Role is a required field there is a 'No Role" in the options
If using RH for Standard objects you can turn them off for custom objects
Team Sharing
Loose relationship
Many Look up
Junction Objects:
Recommend you don’t encrypt unless you have to for legal reasons
Salesforce Lighting - Modern Client - Letting the client (Browser) do some of the work, lets the 'Client" do some of the work. Client side Controls as well (Java script)
Validation rules:
Approval Processes:
Visualforce
Report Types:
Canvass: I frame