Salesforce Platform Basics

Get Started with the Salesforce Platform

Learning Objectives
After completing this unit, you’ll be able to:

 Define the Salesforce platform.

 Describe the DreamHouse scenario.
 Create a Trailhead Playground.
 Explain the difference between no code (declarative) and programmatic development.

Discover Use Cases for the Platform

Learning Objectives
After completing this unit, you’ll be able to:

 Describe sample use cases for the platform.

 Discover reasons for using the platform across multiple departments.

Understand the Salesforce Architecture

Learning Objectives
After completing this unit, you’ll be able to:

 Define key terms related to the Salesforce architecture.

 Find information related to trust.
 Explain at least one use case for Salesforce APIs.

Navigate Setup
Learning Objectives
After completing this unit, you’ll be able to:

 Locate Setup and identify its key elements.

 Identify important menus for customizing your org.
 Use Quick Find to access menu items.

Power Up with AppExchange

Learning Objectives
After completing this unit, you’ll be able to:

 Develop your own AppExchange strategy.

 Install an app from AppExchange.

Prepare Your Salesforce Org for Users

Set Up the Exchange Rate

Learning Objectives
In this project, you’ll:

 Activate multiple currencies with exchange rates.

 Adjust the exchange rate with advanced currency management.
 Build a unique home page for specific profiles.
 Construct a unique list view.
 Create Chatter groups.

Update the Exchange Rate with ACM

Another way to work with the exchange rate is through the advanced currency management tool.
You can manage rates with specific dates.

Customize the Home Page

The home page is what your users see first after logging in. This page can be customized to
highlight information specific to the user. Easy access to pertinent information = increased
efficiency. We customize the home page through the use of the Lightning App Builder.

Create a Unique Account List View

Sales users need quick access to accounts in two specific industries. Let’s customize a list view so
users can conveniently access these accounts.

Create Chatter Groups

Chatter is a great collaboration tool for your users. Through the use of Chatter groups, users can
communicate and share. Chatter groups are classified as either public or private. Public means
anyone can see and add posts, comments, and files. Anyone can join a public group. Private means
only group members can see and add posts, comments, and files. People must ask the
group's owner or managers to join a private group. But first, the groups need to be created.
User Management

Add New Users

Learning Objectives
After completing this unit, you’ll be able to:

 Describe a user account and the type of information it contains.

 Add a single user or multiple users.
 Use the Salesforce mobile app to manage users on the go.

Control What Your Users Can Access

Learning Objectives
After completing this unit, you’ll be able to:

 Describe the difference between object and field level security

 Describe how to set org–wide default sharing settings

Customize an Org to Support a New Business Unit

Manage User Access

Introduction
In this project, you’ll get hands-on practice setting up some of the basic but oh-so-useful functions
a business needs when implementing Salesforce—from adding users and creating Chatter groups
to modifying your data model to fit your business needs and automating processes for max
efficiency.

You’ll find step-by-step instructions on how to get some important functions going for team
members in your Customer Support department. By going through these exercises, you’ll learn
what's possible with the Salesforce platform and some of its specific applications. So let’s dive in.

Manage Chatter
Introduction
Chatter, Salesforce’s enterprise collaboration platform, is a great place for your customer support
team to communicate about things such as support cases and tasks. In this corporate social
network, they can follow both people and documents, and be a part of public, private, and unlisted
Chatter groups to collaborate with their teams and work together on projects.
Modify Your Data Model
Introduction
Salesforce offers lots of customization options that allow you to tailor your org to fit the needs of
your teams. Like a gearhead tricking out a muscle car, you can add some pretty sleek bells and
whistles—creating processes and record types, customizing fields, and creating picklists—all to suit
the needs of your business and keep its engine purring.

Configure an Email Letterhead and Template

Introduction
Having a consistent look makes correspondence from your teams instantly recognizable and
professional. Here, we’ll configure a template and letterhead that can be used by all team
members for their day-to-day email needs.

Automate Your Business Process

Create Assignment Rules
Assignment rules define conditions that determine how leads or cases are processed. You’ve been
asked by Customer Support team manager Kenya Collins to establish case rules so billing cases are
routed to the correct queue.

Start by creating a new Billing Support Agents queue.

Identity Basics

Get to Know Salesforce Identity

Learning Objectives
After completing this module, you’ll be able to:

 Describe how Salesforce Identity helps administrators.

 Understand how Salesforce Identity can benefit a business.
 Distinguish the difference between single sign-on (SSO) and social sign-on.
 Describe the benefits of My Domain.

Get To Know Your Salesforce Identity Users

Learning Objectives
After completing this module, you’ll be able to:

 Describe how employees benefit from Salesforce Identity.

 Describe how customers and partners benefit from Salesforce Identity.
 Describe what’s important when setting up user registration.
 Know which features of Salesforce Identity benefit employees, which benefit partners and
customers, and which benefit both.

Learn the Language of Identity

Learning Objectives
After completing this module, you’ll be able to:

 Identify the industry standards used for identity and access management.
 Know how SAML is related to XML.
 Know the difference between an identity provider and service provider.

Data Security

Overview of Data Security

Learning Objectives
After completing this unit, you'll be able to:

 Explain the importance of giving the right people access to the right data.
 List the four levels at which you can control data access.
 Describe a typical scenario for limiting data access at each of the four levels.

Control Access to the Org

Learning Objectives
After completing this unit, you'll be able to:

 Create, view, and manage users.

 Set password policies.
 Limit the IP addresses from which users can log in.
 Limit the times at which users can log in.

Control Access to Objects

Learning Objectives
After completing this unit, you'll be able to:

 View existing profiles and create new ones.

  Modify access to objects using profiles.
 View all assigned users in a profile.
 Create new permission sets.
 Assign permission sets to single and multiple users.

Control Access to Fields

Learning Objectives
After completing this unit, you'll be able to:

 List reasons to limit access to specific fields.

 View and edit field-level security settings.

Control Access to Records

Learning Objectives
After completing this unit, you'll be able to:

 List the four ways to control access to records.

 Describe situations in which to use each of the four record-level security controls.
 Explain how the different record controls interact with each other.
 Set org-wide sharing defaults to control access to records.

Create a Role Hierarchy

Learning Objectives
After completing this unit, you'll be able to:

 Explain how a role hierarchy is different from an org chart.

 View and modify a role hierarchy.
 Create and assign roles to simplify access to records.

Define Sharing Rules

Learning Objectives
After completing this unit, you'll be able to:

 Use sharing rules to extend access beyond the role hierarchy structure.
 Create a public group that includes users with different profiles and roles.

Permission Set Groups

Get Started with Permission Set Groups

Learning Objectives
After completing this unit, you’ll be able to:

 State what a permission set group is.

 Describe two use cases for using permission set groups.
 Explain how permissions are calculated in a permission set group.

Create a Permission Set Group

Learning Objectives
After completing this unit, you’ll be able to:

 Create a permission set group.

 Assign users to a permission set group.
 Analyze existing profiles and permissions and develop a model that includes permission set
groups.

Mute Permissions in Permission Set Groups

Learning Objectives
After completing this unit, you’ll be able to:

 Describe why you might mute a permission.

 Mute permissions in a permission set group.

Protect Your Data in Salesforce

Restrict Login Hours and IP Ranges

Learning Objectives
In this project, you’ll:

 Restrict when and where users can log in to an organization.

 Determine the levels of access users have to objects.
 Set up a data access model using the role hierarchy, sharing, and teams.
 Control the levels of access users have to fields.

Create New Users and Allow a User to Delete

Accounts
Introduction
You are attending a security and data access review meeting with the CEO and the Executive team.
The first item on the agenda is to ensure that all users have the appropriate object permissions for
their job roles. John Wiseman, CEO, wants to ensure users have access to the objects they need to
do their job, but wants to restrict the ability to delete records to just Executive Users and the
Support team. Noah Larkin, VP of Services, is helping to clean up records, and needs temporary
permission to delete Accounts

Create New Users and Allow a User to Delete

Accounts
Introduction
You are attending a security and data access review meeting with the CEO and the Executive team.
The first item on the agenda is to ensure that all users have the appropriate object permissions for
their job roles. John Wiseman, CEO, wants to ensure users have access to the objects they need to
do their job, but wants to restrict the ability to delete records to just Executive Users and the
Support team. Noah Larkin, VP of Services, is helping to clean up records, and needs temporary
permission to delete Accounts.

Set Organization-Wide Defaults and Create a

Role Hierarchy
Introduction
You have now assigned users to their correct roles. The meeting moves on to data access review,
and you discuss what individual records users should be able to view and edit in each object they
have access to on their profile. You have established a baseline level of access so that users have
the correct level of access to the records they need. However, the discussion now concerns how
this will impact the directors and VPs, who will no longer have all the access they need.

Create Sharing Rules

At present, information is visible only to its owners and users above them in the role hierarchy.
Create sharing rules for other users who also require access.

Set Up Account Teams

Introduction
Selling is a collaborative activity at AW Computing. In addition to sales reps, customer support
reps are also involved with customer accounts, and therefore need access to corresponding
opportunities, cases, and contacts. In this step, you’ll set up account teams to give sales reps,
engineers, customer support reps, and consulting reps access to the opportunities and cases
related to accounts that they are working on.

Data Modeling

Understand Custom & Standard Objects

Learning Objectives
After completing this unit, you’ll be able to:

 Describe the perks of using objects on the Salesforce platform.

 Explain the difference between standard objects and custom objects.
 List the types of custom fields an object can have.

Create Object Relationships

Learning Objectives
After completing this unit, you’ll be able to:

 Define the different types of object relationships and their typical use cases.
 Create or modify a lookup relationship.
 Create or modify a master-detail relationship.

Work with Schema Builder

Learning Objectives
 Describe the advantages of using Schema Builder for data modeling.
 Use Schema Builder to create a schema for a given object model.
 Use Schema Builder to add a custom object to your schema.
 Use Schema Builder to add a custom field to your schema.

Lightning Experience Customization

Set Up Your Org

Learning Objectives
After completing this unit, you’ll be able to:

 Describe the business value of custom objects and fields.

 Create and edit custom objects and fields.
 Create a custom tab for a custom object.

Create and Customize Lightning Apps

Learning Objectives
After completing this unit, you’ll be able to:

 Describe the benefits of Lightning apps.

 Create a Lightning app with custom branding.
 List two best practices for planning Lightning apps for your org.

Create and Customize List Views

Learning Objectives
After completing this unit, you'll be able to:

 Create a custom list view.

 Create a custom list view chart.
 Edit and sort list views.

Customize Record Highlights with Compact

Layouts
Learning Objectives
After completing this unit, you’ll be able to:

 Describe how compact layouts help your users.

 Create a custom compact layout.

Create Custom Buttons and Links

Learning Objectives
After completing this unit, you'll be able to:

 Create custom buttons and links.

 Add them to a page layout.
 Explain the difference between a custom button and a custom link.

Empower Your Users with Quick Actions

Learning Objectives
After completing this unit, you’ll be able to:

 Describe how actions help your users.

 Describe the difference between object-specific and global actions.
 Create an action and add it to a page layout.
Customize a Salesforce Object
Work with Standard and Custom Fields
Learning Objectives
In this project, you’ll:

 Create new custom fields to meet business requirements and facilitate accurate data entry
with formulas, picklists, and lookups.
 Ensure users have access to the right fields with page layouts.
 Manage multiple business scenarios with record types and business processes.
 Maintain data quality with history tracking and data validation.

Introduction
AW Computing has established a Salesforce environment with users set up, profiles assigned, and
access to records and fields configured. But they’re in need of further customization to ensure
users have the necessary fields to capture the business information they need. That’s where you,
the admin, come in.

To begin with, you have a request from Head of Sales Operations Yuko Ishikawa. Yuko says her
Sales Op team uses the Account Rating field for sales prospecting, but they’re concerned that
account owners aren’t capturing this information correctly because they don’t understand what the
field is for. To help her team use the field properly and capture all the data they need, change the
name of the field, provide guidance on how to use it, add an additional value, and restrict who can
edit it.

Create Picklists and Field Dependencies

Introduction
Sales Operations divides AW Computing’s sales territory into regions and zones. Yuko Ishikawa
would like to be able to identify each account record by its region and zone. Allison Wheeler, VP of
Global Sales, would like to track the reasons opportunities are being won or lost, ensuring that
users can select only the appropriate reasons, and only when the opportunity is at Closed Won or
Closed Lost. To accomplish what they want, you set up picklists and field dependencies.

Picklists offer a selection of options available for specific fields in a Salesforce object, such as a list
of regions. Users can then choose a single value from a list of options rather than make an entry
directly in the field, which cuts down on errors and helps keep data clean. Field dependencies are
filters that allow us to change the contents of a picklist based on the value of another field. Rather
than displaying every value for Region in a single picklist, you can limit the values that are
displayed based on a value for another field, like Zone. That way our users can find the appropriate
option more quickly and easily.

Yuko and Allison both provided the information you need via Chatter posts, so let’s get to it.

Create Lookup Filters

Introduction
Lookup filters limit the records available in the lookup. A lookup filter can reference other fields on
the same record (source); fields on the records of the lookup object (target); fields on the user's
record, profile, and role; and fields on records directly related to the target object.

You’ve gotten a request from Noah Larkin, VP of Services, who would like reps to be able to
capture the name of the backup rep on their cases when they are away from the office. He also
wants to ensure that new cases can only be associated to contacts from the same account. To get
this job done, create a lookup filter.

Create Formula Fields

Introduction
VP of Sales Allison Wheeler has requested your help in collecting additional information on
opportunities. First, she’d like sales and executive users to see their commission calculated for won
opportunities. She’d also like the regions and zones of accounts displayed on opportunities for all
to see. And, in an effort to enhance pipeline accuracy, she’d like to display the discounted amount
whenever a discount has been applied to an opportunity

Handle these requests by creating custom formula fields, which allow you to define calculations
that reference other fields to display new numeric, text, date, or checkbox values specific to
business requirements. Let’s get started.

Create Record Types

Introduction
Noah Larkin would like a few more things tweaked for his teams. He'd like you to set up some
page layouts (next step of this project), but first you need to lay the groundwork by creating
record types. Record types determine the business processes, page layouts, and picklist values
users have access to.

Setting up record types will ensure that when Noah's Consulting Team views customer accounts,
they won't also see the partner accounts. The team also has to scroll through a long list of values
in the industry field when they use partners for consulting or training. Creating record types will
allow them to simply choose from Consulting or Education in these cases. Let's get to it.
Create Account Page Layouts
Introduction
Noah Larkin, AW Computing’s VP of Services, is concerned that his Consulting team uses accounts
to record details of consulting partners, but some of the fields they see are not applicable to their
partner accounts—he would like all sales-related information removed.

Allison Wheeler also contacted you with a request. She's concerned that the new account fields
appear together in the top section of account record detail pages. She’d like them organized into
different sections to make it easier for her team to find the right information.

You can solve both of these issues using page layouts, which control the fields, sections, related
lists, and buttons that appear when users view or edit a record.

Enable Account Field History Tracking

Introduction
VP of Support Noah Larkin would like to know which accounts are being marked as having support
plans each week, so he can track which accounts don’t have a support plan expiration date.

To fulfill Noah’s request, enable history tracking, which allows you to track changes on up to 20
standard or custom fields on an object which can be viewed on a record’s History related list or
through History reports. For each field, tracking logs the date and time of change, the user making
the change, and old and new values.

Create Validation Rules

Introduction
Noah Larkin can now track which accounts don’t have a support plan expiration date, but he also
wants to ensure that, going forward, all users enter the support plan expiration date when the Has
Support Plan checkbox is selected on an account. Allison Wheeler has a similar request. She’d like
to ensure that sales reps enter a Close Reason whenever an opportunity is lost.

Take care of Noah’s and Allison’s requests by creating validation rules, which allow you to specify
your own criteria to prevent users saving invalid data in one or more fields.

Note: An important point to keep in mind when working with validation rules is the impact on
existing data. Validation rules apply to both future data and current data so the admin may need
to populate the required data of the existing records to ensure any future integrations aren't
blocked.
Lightning App Builder

Get Started with the Lightning App Builder

Learning Objectives
After completing this unit, you’ll be able to:

 Understand how the Lightning App Builder can help you build responsive apps and custom
pages for Lightning Experience and the mobile app
 Understand the layout of the Lightning App Builder user interface
 Describe the difference between a Lightning page and a Lightning component

Build a Custom Home Page for Lightning

Experience
Learning Objectives
After completing this unit, you’ll be able to:

 Create a custom Home page for your Lightning Experience users

 Assign different Home pages to different profiles
 Set the default Home page

Build a Custom Record Page for Lightning

Experience and the Salesforce Mobile App
Learning Objectives
After completing this unit, you’ll be able to:

 Create a customized object record page for Lightning Experience and the Salesforce mobile
app.
 Add visibility rules to a record page component.
 Activate the custom record page for your users.

Build an App Home Lightning Page

Learning Objectives
After completing this unit, you’ll be able to:

 Add components to a Lightning page

 Configure the properties of a Lightning page and a Lightning component
 Add actions to a Lightning page
 Add a Lightning page to Lightning Experience and the mobile app
Work with Custom Lightning Components
Learning Objectives
After completing this unit, you’ll be able to:

 Install a custom Lightning component

 Use your mobile device to preview your app in the Salesforce mobile app

Formulas and Validations

Use Formula Fields

Learning Objectives
After completing this unit, you'll be able to:

 Create a custom formula field and use the formula editor.

 Explain why formula fields are useful.
 Outline at least one use case for formula fields.
 Create simple formulas.

Implement Roll-Up Summary Fields

Learning Objectives
After completing this unit, you'll be able to:

 Describe what a roll-up summary field is.

 Create a roll-up summary field.
 Apply field-level security to your roll-up summary field.

Create Validation Rules

Learning Objectives
After completing this unit, you'll be able to:

 Describe two use cases for validation rules.

 List the elements of a validation rule.
 Create a validation rule.