salesForce permissions Flashcards
Security Architecture Object Permissions
data request is evaluated against object permissions top of the funnel
Security Architecture Field Accessibility
the requesting users profile is consulted again to determine if fields are read-only or hidden
Security ArchitectureSharing Model
if the user is not the owner of the record the org-wide defaults are applied
Security ArchitectureSharing reasons
Sharing reasons override the org-wide defaults
Object Level Security
governed by the profile – standard or custom
Object permissions
Read; Create; Edit; Delete; View All; Modify All
Admin Permissions
View All; Modify All; Trump all Force.com security measures
2 License types Salesforce and Salesforce Platform
SF allows CRM; SFA; Oppty; and Case (biz domain specific) SFP only Force.com
Field-Level Security
Determined by profile and page layouts
Field Accessibility
Through page layout and profile;Setup->Security Controls->Field Acc.
Field Accessibility values
Required = for this rec to be saved needs a value; Editable modified by user;Read-Only;Hidden
Record-Level Security 3 Concepts
Record-Ownership; User Groups ;Sharing Model–org-wide defaults and Sharing reasons
User Groups
Public Groups a named list of users; Roles a hierarchical list
Sharing Model
how record-level privileges are granted org-wide defaults and sharing reasons
Org Wide Defaults List
Private; Public read-only; Public read-write; Controlled by parent
Org Wide Defaults Private
Recs belong to owner only data admin privileges can override
Org Wide Defaults Public Read-Only
all users can view
Org Wide Defaults Public Read/Write
all users can read/write; all newly created custom objects default to this value
Org Wide Defaults Controlled by Parent
option for child objects in lookup relationships
Sharing Reasons List
Manual; Sharing Rules; Procedural; Delegated Admin
Sharing Reasons Manual
owner can elect to share
Sharing Reasons Sharing Rules
allows records to be shared automatically by Force.com based on group membership or arbitrary criteria
Sharing Reasons Procedural
records shared programmatically via Apex
Sharing Reasons Delegated Admin
Data Admin View All and Mod All; exempt users from all sharing rules
Settings (what users SEE)
Apps;Tabs;Record Types;Page Layouts
Permissions (what the users DO)
Administrative (cuts app);Gen User(run reports mass email);Standard Object (create leads);Custom Objects(edit positions)
Base Level of Access (OWD)
all users
Role Hierarchy
Open up access (vertical access)
Sharing Rules
open up access (lateral access)
Manual Sharing
open up access (flexible)
WorkFlow has 2 elements
Rules and Action
MVC-Model
Metadata; SF Objects
MVC-View
Tabs;Forms;and VF pages
MVC-Controller
Workflows;Apex controllers;Triggers
3SandBox-Configuration Only
All metadata no prod data
3SandBox-Developer Sandbox
has metadata used for code and testing environment
3SandBox-FullCopy
all prod including data records and documents
