 A Sales Process contains the Stages that an Opportunity follows through its sales cycle.

 Users can be assigned to only 1 Profile in Salesforce. They can also be assigned to only 1
Role in the Role Hierarchy, as well. You can assign a user to multiple Permission Sets.
 In addition to the organization-wide Session Settings, which can be found in Setup, there is
also a Session Settings link under each Profile. The Session Settings you designate at the
Profile level override the Session Settings that are set organization-wide.
 Dynamic dashboards enable each user to see the data they have access to. With a dynamic
dashboard, you can control data visibility without having to create a separate dashboard,
with its own running user and folder, for each level of data access. Refer to
[Link]
id=dashboards_dynamic_overview.htm&type=0&language=en_US&release=206.18 for
more details
With dynamic dashboards, you can create just two dashboards and store them in a single
folder:
 Create a dynamic dashboard for sales reps with the following components:
o A gauge of total bookings
o A table of activities by meeting type
 Create a dynamic dashboard for managers and the VP with the following components:
o A gauge of total bookings
o A column chart of close rates by competitor
 Optionally, create filters that let viewers further refine their dashboard views. For
example, create a filter on key accounts to let viewers focus on bookings, activities, and
competitive threats for each account.
All users only see data that they can access. Sales reps see their own bookings and activities.
Managers see bookings and close rates for the reps they manage. The VP sees bookings and
close rates for the whole team. Because the metrics are the same for managers and the VP,
you can use the same dynamic dashboard for both roles. The dynamic dashboards feature
reduces the number of required dashboards from 45 to two!
 Validation rules do not fire on Chatter posts, but are fired during initial creation and
update of records in Salesforce - either manually, or in bulk.
 Validation rules fire, even for fields that a user can't see. Reasons that this may occur
would be if the Field Level Security isn't set for that user's profile to be able to see the
field. Another possibility is that the page layout that is assigned to the user does not
display the field. Turning off the Validation Rule may be a temporary fix until you can get
the data access and visibility issue resolved, but you want to find the root cause, as best
practice. The Role Hierarchy determined which records a user has access to for an
object, but doesn't control the visibility of individual fields on an object
 A product can only reflect pricing in a single currency. You may include the same
product in multiple currencies in a single price book, but each product must have
individualized records for each currency in the price book
 When sales reps convert qualified leads, the information from the standard lead fields
appears in standard fields for contact, account, and opportunity records. If you set up
custom lead fields, you specify how that custom information converts to custom fields in
accounts, contacts, and opportunities. Refer to [Link]
 id=customize_mapleads.htm&type=0&language=en_US&release=206.19 for more
details
 The four valid Report formats you can create in Salesforce are Summary, Matrix,
Tabular and Joined.
 Big Deal Alerts are ideal for this scenario. Refer to
[Link] for
more details on Big Deal Alerts. You can also accomplish this via a workflow rule and
email alert, so that whenever an opportunity reaches a probability of greater than 50%
and the amount is greater than $100,000, an email alert is sent to the Director
 If a user's profile does not grant the access to an object, they will not be able to access
that object or see/edit any of that object's records, even if the Org Wide Default is set to
Public Read/Write
 To change the language of the User Interface for an individual user in Salesforce, you
would change the Langauge setting on that user's user record. Changing the Locale will
potentially impact the format of certain fields, such as Date fields, but does not localize
the User Interface into a different language
 The four available actions via a Workflow Rule, whether Immediate or Time-Based are
Field Update, Email Alert, Outbound Message, and New Task. If you needed to create a
new object record, you would need to resort to a Process to accomplish this
 Converting an org to a multi-currency environment is an undertaking not to be taken
lightly, and cannot be reversed. You have to initiate this process by logging a Case with
Salesforce. You also have to confirm the understanding that this process cannot be
reversed, in addition to their being a lockout period for your organization
 For an approval process to start, it must first be submitted. This is the starting point at
which a record enters an approval process, and then it traverses through the various
steps, based on the processes settings and if criteria is met. Refer to
[Link]
id=approvals_getting_started.htm&type=0&language=en_US&release=206.18 for more
details.
 Bucketing lets you quickly categorize report records without creating a formula or a
custom field. For example, create a bucket field named Size based on the # Employees
field. Then, create buckets that group records into _Large,_ _Medium,_ or _Small_
ranges that you define. Bucket fields can be used like any other field to sort, filter, and
group your report. Refer to [Link]
id=reports_bucketing_overview.htm&type=0&language=en_US&release=206.19 for
more details
 You can create custom summary formulas for summary and matrix reports to calculate
additional totals based on the numeric fields available in the report. Refer to
[Link]
id=building_custom_summary_formulas.htm&type=0&language=en_US&release=206.1
8 for more detail
 Email-to-Case can be enabled and set up to automatically create a case in Salesforce
when a customer sends an email to a defined email address. Refer to
[Link] for
more details
 You cannot set field dependencies from the Page Layout Editor. You can make a field
visible, read-only, and/or required via the Page Layout Editor. Refer to
[Link]
id=customize_layoutcustomize_pd.htm&type=0&language=en_US&release=206.18 for
more details.
 Salesforce provides three primary types of Communities, which are Customer, Partner
and Employee Communities. Refer to
[Link] for more details.
Salesforce also offers other Cloud solutions, such as Government Cloud and Health
Cloud, but these are not Communities
 You can effectively make a field required by creating a validation rule where if the field is
left blank, an error displays, not allowing the record to be saved until that field is
populated. You can also set a field to Required on the Page Layout, as well as by
checking the Required checkbox on the actual field itself. Field Level Security is used to
set if a field is Visible and Read-Only, but isn't used to mark a field as required
 Prioritize, distribute, and assign records to teams who share workloads. Access queues
from list views. Queue members can jump in to take ownership of any record in a queue.
They're available for cases, leads, orders, custom objects, service contracts, and
knowledge article versions. Refer to [Link]
id=queues_overview.htm&type=0&language=en_US&release=206.18 for more details.
 Salesforce contains a multitude of Standard Profiles, such as Standard User, Chatter
Free User and System Administrator. If you go to Setup > Profiles, you can view a list of
all profiles in your own org. Note the Custom checkbox column, which denotes if a
profile is custom or standard
 There are many scenarios in which you can experience data loss when changing a
field's field type. Going from a picklist to a multi-select picklist won't wipe out existing
data. Also, going from a Number to Text will be ok because numeric values can be
displayed and represented in text fields. Think through the various scenarios logically
and test some of them out in your own org. Refer to
[Link]
id=notes_on_changing_custom_field_types.htm&type=0&language=en_US&release=20
6.17 for more details on changing custom field types and potential data loss.
 You can use master-detail relationships to model many-to-many relationships between
any two objects. A many-to-many relationship allows each record of one object to be
linked to multiple records from another object and vice versa. Refer to
[Link] for
more details

Junction Object
A custom object with two master-detail relationships. Using a custom junction object, you can
model a “many-to-many” relationship between two objects. For example, you create a
custom object called “Bug” that relates to the standard case object such that a bug could be
related to multiple cases and a case could also be related to multiple bugs
 Lightning Sync keeps Contacts and Events in sync automatically. You can learn more
about Lightning Sync by referring to this guide -
 [Link]
ync_user.pdf
 Your user account has not been locked, because in this scenario you confirmed your
account was ok by successfully logging in via the interface. Additionally, you don't
require a separate license for Data Loader - it is a free download, and you can use it to
connect to any Salesforce accounts with which you have an active user license for.
There are different versions of the Data Loader, and you can download and install
updates, but this won't affect your ability to log in to your Salesforce instance. If you do
find yourself in this scenario, you'll need to append your Security Token to the end of
your Password in the Password field in order to log in using the Data Loader. Refer to
[Link] for more
details on your Security Token and how to reset it.
 Profiles are used in order to grant or deny access to a custom app in Salesforce. Roles
control which records you have access to, but do not control App access. Page Layouts
control the user interface for individual records. Sharing Rules are made at the object
level, but not at the app level
 You would want to ideally deactivate the user, but can also freeze their user account if
they are still entangled with various administrative processes. This will effectively keep
them from logging back into Salesforce. You cannot delete a user account in Salesforce.
And changing their Role or Profile would not prevent them from logging back into their
existing account.
 The Sales Process is where you set which Stages are visible to users. Field Level
Security dictates whether a user can view and edit a field, but doesn't control to the level
of which specific picklist values display. Likewise, the Page Layout controls which fields
are displayed on a page, but don't control specific picklist values of a field. Whenever
you have to deal with specific picklist value visibility, the things that control this are
typically Record Type and Process related.
 Feature Licenses, such as Service Cloud, are assigned via the User record. You can
see how many Feature Licenses you have available in your org by visiting the Company
Information screen, but you cannot assign these licenses from there.
 The Global User Interface settings are a series of checkmarks that are available from
Setup > User Interface. These settings control a multitude of user interface functions
and it will serve you well to experiment with them in order to become more familiar with
what they do and how they impact the interface of Salesforce.
 It is very easy to forget to create a tab for a new custom object. If you forget to do so,
simply go to Setup > Create > Tabs and click New under the Custom Objects Tab
section of the page. You'll be prompted to select the Object that the tab is for, as well as
set the Tab Visibility for each Profile. The four possible answers for this question
represent the four types of tabs that you can create in Salesforce.
 You can select certain fields to track and display the field history in the History related
list of an object. The field history data is retained for up to 18 months. Refer to
[Link] for more
details. You could theoretically set up a workflow rule and email alert to email the Sales
Director, but this wouldn't be the optimal solution. You could actually likely accomplish
this through any of these available answers, but the point is that Field History Tracking is
 custom-made for this sort of situation and doing anything more complex wouldn't be as
suitable of a solution. You could also likely create a report to also give you this same
information.
 Custom Picklist fields and Multi-Select Picklist fields can be dependent picklists.
Standard Picklist fields cannot be dependent fields. Refer to
[Link]
id=fields_dependent_field_considerations.htm&language=en_US&type=0 for more
details.
 Profiles, Page Layouts and Field Level Security don't go down to the level of the
individual picklist selections. Whenever users report that certain picklist fields do not
contain certain selections, go to the Record Type menu for the object in question, and
then select the various Record Types for that object. Each Record Type for an object will
display Picklists Available for Editing. If you click Edit next to one of those picklists, it will
show you Available Values and Selected Values for the picklist field. From there, you
can also select a default selection.
 Both Revenue and Quantity scheduling are supported for products in Salesforce, once
Product Schedules have been enabled. Refer to [Link]
id=enabling_schedules.htm&type=0 for more details.
 Though multiple campaigns can be influential, you can designate only one campaign as
the primary campaign source on the opportunity. The campaign you designate as the
primary campaign source will always appear in the Campaign Influence related list.
Refer to [Link]
id=campaigns_influence_using.htm&language=en_US&type=0 for more details.
 Two primary pieces of Activity Management are Tasks and Events, which can be added
to your Home Page in Salesforce Classic (Events display in your Calendar, which can
be added to the Home Page, along with buttons for creating a New Event).
 Activities in Salesforce are your events, your tasks, calls you've made, and emails you
have sent. Salesforce gives you multiple ways to track your activities together for a more
complete picture of your progress on deals and accounts. Refer to
[Link]
id=[Link]&type=0&language=en_US&release=206.19 for more details on Activity
Management.
 A reporting snapshot lets you report on historical data. Authorized users can save
tabular or summary report results to fields on a custom object, then map those fields to
corresponding fields on a target object. They can then schedule when to run the report
to load the custom object's fields with the report's data. Reporting snapshots enable you
to work with report data similarly to how you work with other records in Salesforce. Refer
to [Link]
id=data_about_analytic_snap.htm&language=en_US&type=0 for more details.
Reporting Snapshots were previously known as Analytic Snapshots, so you may see
that mentioned online as well.
 Use a gauge when you have a single value that you want to show within a range of
custom values. For example, to create a dashboard that measures where your current
closed opportunity amounts fall within a range of values, set the Minimum Value,
Breakpoint #1 Value, Breakpoint #2 Value, and Maximum Value for the gauge. The
 ranges that you set can indicate poor, acceptable, and good performance. Set
appropriate colors for each of these ranges to visually indicate progress. To create a
gauge with only two ranges, leave Breakpoint #2 Value blank. Refer to
[Link]
id=dashboards_component_types.htm&type=0&language=en_US&release=206.19 for
more details on Dashboard components.
 A Visualforce Page is a valid dashboard component, along with Metric, Gauge, Chart,
and more. Refer to [Link]
id=dashboards_component_types.htm&type=0&language=en_US&release=206.19 for
more details on valid dashboard component types
 The Time-Based Workflow Queue shows pending actions and can be accessed by
going to Setup > Monitor > Time-Based Workflow. The View Setup Audit Trail reveals
what changes and customizations administrative users have made in your org. Refer to
[Link] for
more details on Time-Based Workflow.