Configuration and Set Up Flashcards
What are listed in Company Settings?
Company information, default language, default time zone, currencies, fiscal year settings, business hours, holidays and available languages
What is listed in Company Information?
Listed under Company Settings and tracks what’s important about the org, manage licenses and entitlements.
-SF Org ID
-Enable multiple currencies
Types of SF Licenses?
-SF; SF Platform; Permission Set License; Feature Set License; Usage-Based Entitlement
What are aspects of User Interface Settings?
Hover details, inline editing, navigation bar customization, printable list views
App Menu?
-Add/remove visibility of apps ; reorder
-“Visible” or “Hidden” in App Launcher to show or hide individual apps from the App Launcher for all users in the org.
App Manager?
-Create new Lightning apps and edit existing ones
-When you edit a Lightning app from the App Manager in Setup, you’re brought into the Lightning App Builder to manage the app’s settings. You can update the app’s branding, navigation, app options, and manage the Lightning pages assigned to that app all inside the Lightning App Builder.
Lightning App Builder?
-Create app page, home page, record page, embedded service page
—on my L.A.P. I have a H.A.R.E.
-refine appearance of org to make it easier and more accessible to users
-need to save and activate page to use
List Views?
-Filters so only records you want to see are shown
-Available for most objects, customizable, fields can be added/removed
-List, Split, Kanban
Types of Object Specific Actions?
You can add global quick actions to almost any page that supports actions. Use global actions to let users log call details, create or update records, or send email, all without leaving the page they’re on. Global create actions enable users to create object records, but the new record has no direct relationship with other records.
Multiple User Creation?
-up to 10 (Data Loader is 10+)
-must all have same type of license
-username is email
-required: last name, email/username, profile, role
SF License?
-users who require full access to standard CRM and App Exchange apps
-entitled to access any standard/custom app
-To enable specific Salesforce functionality for your users, you must choose one user license for each user e.g. Salesforce, Chatter Free, Chatter External. To grant additional functionality, you can assign permission set licenses e.g. Sales Console User and feature licenses e.g. Marketing User or Knowledge User to your users.
SF Platform License?
-users who need access to custom apps but not to standard CRM functionality
-can use core platform functionality : accts, contacts, reports, dashboard, docs and custom tabs
-not entitled to some user perms and standard apps (including standard tabs and objects such as forecasts, leads, campaigns and opps)
Permission Set License?
-give access to various tools and functions not included in user license ; extends access without changing their profiles
-can have multiple permission sets licenses (ex: CRM user)
Feature Set License?
-allows users to access feature that may not be included w/ licenses
-ex: Marketing License
-can have multiple feature set sets
-ex: Knowledge user
Set Up Audit Trail?
-used to track any meta-data changes that have been made to your org
-can see last 20 changes to org
Login Hours?
-set when users can login to SF
-set at profile level
-used to prevent users from logging in when they shouldn’t
Login IP Ranges?
-used to restrict access to SF org through designated approved IP locations
-set at profile level
-https://salesforce.vidyard.com/watch/bCN1I-5LGbzPMQRDLlD4hw
Trusted IP Addresses?
-allow users to login from those locations without any login challenge or verification request
-network access/security –> set at org level
-when you define IP address restrictions for profile, login from any other IP address is denied
-Trusted IP Ranges can be set from “Network Access” page in SetUp to force users to verify identity if they log in outside the range
Password Policies?
-set at profile level and override O.W. password policies
Security Health Check
-helps pinpoint any fixes that will help improve security
-compares to SF baseline
-Excellent: 90% +
-Very Good: 80-89%
-Good: 70-79%
-Poor: 55-69%
-Very Poor: below 54%
-high, med, low, informational settings
Standard Object Permissions
-can control whether user can read, create, edit, delete (CRED), view all, modify all (–> these two will give access to all records of this object regardless of sharing setting of org)
–I OBJECT!!! Dude he seems CREDible and I have to P.P. (perms and profile)
Object Access
-control what objects users have access to
-tab hidden: users can’t see tab and can’t access at all
-default off: not appear in nav bar but can add/find in app launcher
-default on: appears in nav bar as standard
Record Access
-controls which records users have access to and level of access
-ex: org wide defaults (set most restrictive baseline of access), role hierarchy, sharing rules (owner and criteria based), manual sharing, team access (share records based on team - need to have teams enabled and can only have access to object if it’s visible to user)
Field Level Security/Access
-most granular way to control what fields users can see/edit
-set at profile level or object level
Grant Access Using Hierarchies
-only available for editing custom objects
-default on for standard objects and cannot be changed
To View Health Check
-View Health Check
-View Setup and Configuration
-Enabling View Health Check automatically enables View Setup and Configuration if it’s not already enabled
Delegated Administrator?
Users in a delegated administrative group can support the Salesforce Administrator by completing specific administrative tasks. Some of these include:
Create and edit users in specific roles and all subordinate roles
Unlock and reset passwords for users in specific roles
Assign users to specified profiles
Assign or remove permission sets for users
Create public groups and and manage membership in specified public groups
Manage custom objects
Record Sharing
The features that control record sharing are: Role Hierarchy, Organisation-Wide Defaults and Sharing Rules
–if you are a DJ (RECORD), your arm will be S.O.R.
Chatter External vs Chatter Free Licenses
Chatter External licenses provide the access required. Chatter External licenses enable you to invite customers to collaborate in specific groups; most importantly, unlike Chatter Free licenses, customers will only have access to users and information shared within those groups. Chatter External licenses do not grant access to Salesforce objects or data which suits our requirements.
One to Many Relationship
Account object has a one to many relationship with Opportunity and Case objects
—Product and Price Book Entry objects are not related to the Account
Profile Object Settings
- Tab Settings
- Record types and page layout settings
- Object permissions
- Field permissions
Lightning Record Page
-must be activated
-can be assigned to by : Org default, App default, combo of App, Record Type and Profile
Master Detail
-standard objects must be on master side with custom object
-child record inherits sharing settings from parent
-master detail can be created between custom objects (NOT standard)
Scoping Rule
-used to control records users see in list views, reports, and SOQL, based on selected criteria
-flexible and can be enabled and disabled on a query-by-query basis
-don’t restrict access that users have to records
-available for : Acct, Case, Contact, Event, Lead, Opp, Task and for custom objects
Restriction Rule
-applied to a user to filter the records that the user is granted access to via org-wide defaults, sharing rules, and other sharing mechanisms
-used to prevent access to certain records (sensitive data or info that isn’t important to their work)
-available for custom objects, external objects, contracts, tasks and events
Controlled by Parent
-access to contacts will be controlled by access user has to the parent
Public Read/Write
-grant read/write access to all contacts for all users
Private
-if sharing setting is set to private, criteria-based sharing rule would need to be used to give access based on the owner of the contact account
Public Read Only
-gives view access, not edit access
