Video 1 : "What is Salesforce | Introduction to Salesforce”

What is Salesforce?
●​ Salesforce is a cloud-based software that helps businesses manage their relationships with customers.
●​ It is mainly used for sales, customer service, marketing, managing data, and running business
operations online.
●​ Everything runs on the internet—no need to install or maintain complex servers.

Key Concepts Explained

●​ Cloud Computing: Running software and storing data on the internet (“the cloud”) instead of on your
own computer.
●​ CRM (Customer Relationship Management): A system that keeps track of customers, sales, and
service, making it easier for companies to grow and support customers effectively.
●​ Salesforce is a CRM—but more powerful, because you can customize and automate processes as
your business grows.

Classic vs Lightning Experience

●​ Classic: The old look of Salesforce.
●​ Lightning: The newer version with a modern look, more features, and is easier to use.

Multi-Tenant Architecture
●​ Salesforce uses a system where multiple businesses use the same software and hardware but their
data is kept separate and safe—like many tenants living in the same building but in different apartments.

Question Answer
Salesforce is a cloud-based Customer Relationship Management (CRM)
What is Salesforce? platform used to manage sales, service, marketing, and business operations, all
through the internet.
CRM stands for Customer Relationship Management. It helps businesses
What is CRM and why is it
organize and track customer information, improve relationships, and grow sales
important?
by centralizing all customer data and interactions.
What is the difference between Classic is the older version of the Salesforce interface, while Lightning is the
Salesforce Classic and newer, more modern interface with better features, a cleaner look, and an easier
Lightning Experience? user experience.
What does "cloud computing" It means Salesforce software and data are accessed via the internet rather than
mean in the context of installed on local computers, making everything easier to maintain, access, and
Salesforce? update.
It means many companies use the same shared Salesforce platform and
What does multi-tenant
infrastructure, but their data is securely kept separate, just like separate
architecture mean?
apartments in a building.
"Model your Salesforce Data" (Salesforce Admin Training EP-2)
This beginner-friendly video explains how Salesforce organizes data using objects, fields, and relationships.
You’ll understand the pieces that make up the Salesforce database and how they connect, so you can set up
your own data model and customize Salesforce for different business needs.

Key Concepts Explained

 ●​ Objects: Think of objects as tables in a database (like “Accounts,” “Contacts,” or “Invoices”). They store
information about different things.
○​ Standard Objects: Built-in Salesforce tables (e.g., Account, Contact).
○​ Custom Objects: Tables you create for your own business needs.
●​ Fields: Columns in a table. Each object has fields (like “Name,” “Phone Number”).
○​ Various field types: text, number, date, currency, picklist (dropdown), etc.
●​ Relationships: Ways to connect objects so data is linked.
○​ Lookup Relationship: A loose link—useful when the connection isn’t required.
○​ Master-Detail Relationship: A tight link—child records can’t exist without the parent.
●​ Dependent Picklist: Dropdown menus that change based on choices—useful for guiding users to valid
options.
●​ Schema Builder: A graphical tool in Salesforce that lets you see and design all your objects, fields, and
relationships visually.

Step-By-Step Practical Instructions Demonstrated in the Video

1. Creating a Custom Object

●​ Go to Setup.
●​ Select “Object Manager.”
●​ Click “Create,” then “Custom Object.”
●​ Fill out the details (e.g., “Invoice”).
●​ Save the object.

2. Adding Fields to Objects

●​ Within your custom object, select “Fields & Relationships.”
●​ Click “New Field.”
●​ Choose a field type (Text, Number, Picklist, etc.), give it a name, and save.

3. Creating Relationships Between Objects

●​ Choose “New Field.”
●​ Select either “Lookup Relationship” or “Master-Detail Relationship.”
●​ Pick the related object (e.g., connecting “Invoice” to “Account”).
●​ Fill out the required details and save.

4. Setting Up a Dependent Picklist

●​ Create two picklist fields—one as “controlling,” one as “dependent.”
●​ Set field dependencies in the object to control which options show based on the previous choice.

5. Using Schema Builder

●​ Find Schema Builder under Setup.
●​ Drag and drop to create new objects or fields visually.
●​ View relationships between objects as a diagram.

5 Possible Interview Questions and Answers

 Question Answer
An object is like a table in a database. It stores records of a particular type, such
What is an object in Salesforce?
as “Account,” “Contact,” or a custom object like “Invoice.”
What is the difference between Standard objects are provided by Salesforce out of the box (e.g., Account,
a standard object and a custom Contact), while custom objects are created by users to store information specific
object? to their organization’s needs.
What types of relationships
The main types are Lookup (a loose connection) and Master-Detail (a strong
exist between Salesforce
parent-child connection where the child record relies on the parent).
objects?
What is a dependent picklist in A dependent picklist is a dropdown field where the available options change
Salesforce? based on the value selected in another (controlling) picklist.
Schema Builder is a visual tool that lets users create, modify, and view objects,
What is Schema Builder used
fields, and relationships in Salesforce in a diagram format, making it easier to
for in Salesforce?
understand the data model.
Episode 3: Customizing the Salesforce User Interface
This video from the "Salesforce Admin Training" playlist explains how to make Salesforce's user experience
better for your team by customizing apps, page layouts, and data views. The goal is to help you organize
information in a way that's easy to use and fits your business needs.

Key Concepts Covered

●​ Salesforce Apps: Collections of tabs and features, grouped for different business tasks.
●​ App Manager: Where you can create or edit apps.
●​ Custom Tabs: Allow users quick access to objects or web content.
●​ Record Types: Let you show different business processes or page layouts to different users.
●​ Page Layouts: Control what fields and sections users see on a record's detail page.
●​ Related Lists: Show records related to what you're viewing (e.g., all contacts for an account).
●​ List Views: Help filter and display records based on specific criteria.
●​ Compact & Mini Layouts: Show key details at the top of a record or in pop-up previews.
●​ Lightning App Builder: A drag-and-drop tool to visually design custom pages.

Step-by-Step Instructions Highlighted in the Video

1. Build Your Own Salesforce App

●​ Go to App Manager in Setup.
●​ Click New Lightning App.
●​ Enter the app details (name, logo, etc.).
●​ Choose which tabs (objects) you want in the app.
●​ Assign the app to specific profiles if needed.
●​ Save and finish. The new app will show on the App Launcher.

2. Create a Custom Tab

●​ From Object Manager, choose the object you want a tab for.
●​ Click Tabs in the left panel.
●​ Click New.
●​ Fill in details (tab label, style, etc.).
●​ Save the tab.

3. Set up Record Types and Page Layouts

 ●​ In Object Manager, select the object (e.g., Accounts).
●​ Click Record Types > New to create a new one.
●​ Name it and assign to the relevant profiles.
●​ Select or create Page Layouts that display the right fields and sections.
●​ Assign layouts to the record type as desired.

4. Customize Related Lists & List Views

●​ Edit the Page Layout for your object.
●​ Drag Related Lists onto the layout for visibility.
●​ For list views, open an object tab (e.g., Accounts) and click Create New View.
●​ Choose filters and fields to display in your custom view.

5. Use Lightning App Builder

●​ Go to Lightning App Builder in Setup.
●​ Click New and select a page type (e.g., record page).
●​ Use drag-and-drop tools to add, arrange, or remove components.
●​ Save and activate your custom page.

5 Possible Interview Questions and Answers

Question Answer
What is a Salesforce App, and A Salesforce App is a group of tabs and features tailored for a specific
why are they important? business purpose, helping users focus only on what they need to do.
How do Record Types and Page Record Types let you offer different business processes, and Page Layouts
Layouts work together? control what fields or sections users see for each record type.
What is the Lightning App Builder It’s a visual drag-and-drop tool for building and customizing record, app, or
used for? homepage layouts in Salesforce Lightning Experience.
What is a Related List in It’s a section on a record’s page showing all related records from another
Salesforce? object (like all contacts for a specific account).
How can you create a custom Go to an object tab, click “Create New View,” choose filter criteria and fields,
List View in Salesforce? then save to display the records that match your conditions.

Episode 4 : Aggregating & Validating Data in

Salesforce
This video introduces simple but powerful tools that help you keep data accurate and organized in Salesforce. As
a beginner, you will learn how formula fields, roll-up summary fields, validation rules, and duplicate rules
work and why they are important for a successful Salesforce admin.

Key Concepts Explained

Formula Fields
●​ What: Calculation fields that update automatically based on values in other fields (like formulas in
Excel).
●​ Why: Useful for automatically displaying totals, checks, or custom logic without manual updates.

Roll-Up Summary Fields

 ●​ What: Fields that aggregate (sum/count/min/max) values from related child records.
●​ When: Only available when two objects have a Master-Detail relationship.
●​ Example: Showing the total amount from all related invoices on an Account record.

Validation Rules
●​ What: Rules that prevent users from saving incorrect or incomplete data.
●​ How: Checks the data when a user saves a record; shows an error message if the data doesn’t meet
your rule.

Duplicate Rules
●​ What: Prevent or warn users about duplicate records.
●​ How: Checks for existing records with the same key information and either blocks the save or warns the
user.

Practical Step-by-Step Instructions

A. Creating a Formula Field

1.​ Go to Setup → Object Manager.
2.​ Choose your object (e.g., Account).
3.​ Select Fields & Relationships.
4.​ Click New Field and select "Formula."
5.​ Enter the field name, pick a data type, and write your formula.
6.​ Save, set field security, and add it to the page layout.

B. Creating a Roll-Up Summary Field

1.​ In Object Manager, select the parent object (must have a Master-Detail relationship).
2.​ Choose Fields & Relationships.
3.​ Click New Field and select "Roll-Up Summary."
4.​ Name it, choose summary type (SUM, MIN, MAX, COUNT), and select the child object/field to
summarize.
5.​ Add filter criteria if needed.
6.​ Save and add to the layout.

C. Creating a Validation Rule

1.​ In Object Manager, select the object.
2.​ Click Validation Rules, then New.
3.​ Name your rule and write a formula (e.g., ISBLANK(Website) to prevent blank websites).
4.​ Write an error message for users.
5.​ Save and test the rule.

D. Creating Duplicate Rules

1.​ Go to Setup and search for "Duplicate Rules."
2.​ Create a Matching Rule to define duplicate criteria.
3.​ Activate the Matching Rule.
 4.​ Create a Duplicate Rule tied to your Matching Rule, decide to block or warn on duplicates.
5.​ Activate and test.

Quick Reference: Key Terms

Concept Description
Formula Field Auto-calculates its value based on other fields.
Roll-Up Summary
Aggregates (sum, min, max, count) data from related records.
Field
Validation Rule Prevents or warns about incorrect data using custom logic and messages.
Stops or alerts users when entering duplicate records, using matching rules to check for
Duplicate Rule
duplicates.
Matching Rule Criteria that define when something counts as a duplicate.
5 Interview Questions & Sample Answers
Question Sample Answer
What is a formula field in It’s a custom field that calculates and displays a value automatically using a
Salesforce? formula referencing other fields in the record.
When would you use a When you want to show a total, minimum, maximum, or count of related child
roll-up summary field? records on the parent record, but only if they have a Master-Detail relationship.
How does a validation rule It ensures that users enter correct or complete data by checking conditions and
help maintain data quality? showing an error if the rule isn’t followed, stopping bad data from being saved.
A duplicate rule either blocks or warns users when they try to add a record that
What is a duplicate rule?
matches one already in Salesforce, helping prevent duplicate data.
First, create a matching rule that defines what counts as a duplicate. Then, create
What do you need to do to
a duplicate rule that uses the matching rule and decides what action to take on
set up duplicate prevention?
matches.

Episode 5 : Salesforce Automation Tools (Workflow

Rule & Process Builder)
This beginner-friendly video explains how to automate common business processes in Salesforce using tools
that require no coding. You will learn about Workflow Rules, Process Builder, and Email Templates—essential for
new admins who want to save time and reduce mistakes.

Key Concepts

1. What is a Business Process?

A business process is a set of steps involving several people or teams to achieve a goal (like onboarding an
employee or processing a sales order). In Salesforce, you can automate many of these steps.

2. Workflow Rules
Workflow Rules automatically trigger actions (like sending emails, updating fields, or creating tasks) when certain
conditions are met. They help you respond to changes in your data without manual effort.

3. Process Builder
This is a more powerful tool than workflow rules, allowing you to:

●​ Use point-and-click steps to build automations.

 ●​ Trigger actions based on more than one condition or across multiple objects.
●​ Run immediate or scheduled actions like updating records, posting to Chatter, or launching other
processes.

4. Email Templates
Reusable email drafts that save time and ensure all outgoing emails look consistent. You can insert merge fields
(like customer names) to personalize each message.

Step-by-Step: How to Automate with Workflow Rules

1.​ Go to Setup and search for “Workflow Rules.”
2.​ Click New Rule and pick the object (e.g., Account or Opportunity) you want to monitor.
3.​ Set the rule criteria (what triggers your automation).
4.​ Choose the actions (send an email alert, update a field, create a task, etc.).
5.​ Activate the rule. Now, it runs automatically whenever the criteria are met.

Step-by-Step: How to Build Automation with Process Builder

1.​ Go to Setup and find Process Builder.
2.​ Click New to start a new process.
3.​ Name your process and set when it should start (like when a record is created or edited).
4.​ Add criteria—the conditions for your automation.
5.​ Add actions—what you want Salesforce to do (send an email, update data, etc.).
6.​ Save and activate your process. It will now run automatically as defined.

Step-by-Step: Creating and Using Email Templates

1.​ Go to Email Templates in Setup.
2.​ Click New Template.
3.​ Choose a type (Text, HTML, etc.), give it a name and subject.
4.​ Type your message, using merge fields to add details (like client names).
5.​ Save the template. It is now ready to use in automations or manual emails.

5 Possible Interview Questions and Answers

Question Answer
What is a Workflow Rule in It’s an automation tool that performs actions like sending emails or
Salesforce? updating records when specific criteria are met.
What are the main differences Process Builder is more powerful; it can handle more complex logic and
between Workflow Rule and Process automate multiple actions or objects, while Workflow Rules are simpler
Builder? and support fewer actions.
When would you use an Email When you need to send consistent, reusable emails, especially for
Template in Salesforce? automated processes like alerts or approvals.
How do you build a basic Workflow By defining the object, setting criteria for when it runs, picking the actions
Rule? (like email alerts or field updates), and activating the rule.
What can you automate using
Actions like creating records, posting to Chatter, or launching other
Process Builder that is not possible in
processes, and using more flexible conditions across different objects.
Workflow Rules?
Episode 6 : Automating Business Processes with
Flow & Assignment Rules
Key Concepts in Simple Terms
1. Business Process:​
A set of steps that a company follows to get work done. Examples: assigning leads to sales reps, approving leave
requests, following-up on customer support tickets.

2. Workflow Rule:​
A basic (older) automation tool—triggers basic actions (like sending emails or updating records) when set
conditions are met.

3. Process Builder:​
More powerful than Workflow Rules. It lets you automate multiple steps and create more complex logic—still
using easy point-and-click, no code needed.

4. Flow / Flow Builder:​

The most powerful admin automation tool in Salesforce. Lets you build “flows” (like flowcharts) for capturing data,
updating records, sending emails, and guiding users—all in a visual, drag-and-drop editor.

5. Assignment Rules:​
These automatically assign records (like leads or cases) to the correct user or queue based on specific criteria
(for example, geographic region or priority).

Step-by-Step: How to Build an Automation with Flow Builder

1.​ Go to Setup and search for “Flow”.
2.​ Click New Flow.
3.​ Choose the type of flow (e.g., Record-Triggered, Screen Flow).
4.​ Drag elements (like Get Records, Assign, Update, Create, Decision) into the flow canvas.
5.​ Set criteria and actions for each step—decide what happens and when.
6.​ Click Save, give your flow a name.
7.​ Click Activate to make it run.
8.​ Test your flow using a sample record to ensure it works as expected.

Practical Example from the Video

●​ The video includes a demo walking you through creating a Lightning Flow that automates updating
fields or sending alerts when certain conditions are met on a record.

Step-by-Step: How to Set up an Assignment Rule

1.​ Go to Setup and search for “Assignment Rules”.
2.​ Select the object (e.g., Lead or Case) you want to create an assignment rule for.
3.​ Click New Rule, name it, and activate.
4.​ Add rule entries specifying criteria (e.g., if Country = USA, assign to John).
5.​ Set assignment order and save.
6.​ Test by creating a record and confirming it’s assigned correctly.

5 Possible Interview Questions & Answers

 Interview Question Sample Answer
Salesforce Flow is a powerful automation tool that allows admins to visually
What is Salesforce Flow, and how
design and automate complex business processes using a drag-and-drop
is it used?
interface.
How does Flow Builder differ from Flow Builder is more advanced, supporting multi-step logic, interactions with
Workflow Rules and Process users, and complex decision-making, while Workflow Rules are simpler and
Builder? older.
When leads are captured from a website, an assignment rule can
Give an example of when you’d use
automatically allocate them to specific sales reps based on region, ensuring
an Assignment Rule.
fast and fair handling.
In Flow Builder: create a new flow, choose the trigger (e.g., record change),
What steps do you follow to create
add elements (Get, Decision, Update), connect them, save, and activate the
a flow that updates a record?
flow.
They help reduce manual work, eliminate mistakes, speed up processes,
Why are automation tools important
and ensure consistent handling of tasks—making organizations more
in Salesforce?
efficient.

Episode 7 : Approval Processes in Salesforce

This video introduces Approval Processes in Salesforce—a powerful way to automate how records (like
requests or opportunities) are reviewed and approved before moving forward. As a total beginner, you’ll learn
what an approval process is, when and why to use it, and how to create one to simplify your business workflows.

Key Concepts Explained

●​ Approval Process: An automated workflow that routes records for review and approval based on rules
you set. Great for managing things like discounts, expense approvals, or hiring requests.
●​ Approver: The user or group that decides whether a record should be approved or rejected.
●​ Approval Steps: The stages a record passes through. Each has its own criteria and designated
approver.
●​ Entry Criteria: Conditions that define when a record enters the approval process (for example, when a
discount is above a certain amount).
●​ Approval/ Rejection Actions: Automated tasks that happen when a record is approved or rejected (like
sending an email or updating a field).
●​ Record Locking: When a record is in approval, it is locked so only approvers can change it.

Step-by-Step: How to Create an Approval Process

1.​ Go to Setup and search for "Approval Processes."
2.​ Choose the Object you want the approval process for (e.g., Opportunities, Cases).
3.​ Click Create New Approval Process and use the wizard to define details:
○​ Process name, entry criteria, and description.
1.​ Define Approval Steps:
○​ Add steps, set who the approver will be (user, manager, role, or queue).
○​ Set criteria for each step if needed.
1.​ Select Actions:
○​ Set what happens when a record is submitted, approved, or rejected (e.g., send an email,
update a field).
1.​ Activate the Approval Process.
2.​ Test the Process:
○​ Submit a record to make sure it follows the approval path as expected.

5 Common Interview Questions & Answers

 Question Sample Answer
What is an approval process in An approval process automates how records are reviewed and approved,
Salesforce? routing them to the right people and triggering actions based on decisions.
What are approval steps, and Approval steps are the stages a record goes through for review, each with its
why are they important? own criteria and approver, ensuring proper checks before approval.
How do you set up entry criteria Entry criteria are the conditions a record must meet to enter the process, set
for an approval process? during creation (e.g., field value is above a threshold).
What happens when a record is Approval actions (like sending an email or updating a status) run on approval;
approved or rejected? rejection actions (like notifying the user) run on rejection.
Why is record locking important It prevents unauthorized changes while a record is pending approval, ensuring
in an approval process? data is accurate and review isn’t bypassed.

Episode 8 : Salesforce Approval Processes (Part 2)

This video focuses on advanced features of Salesforce Approval Processes, showing how to handle
multi-level, team-based, and automated approvals. It is ideal for beginners wanting to automate complex
business approvals—such as when discounts, leaves, or requests require one or more people to review before
approval.

Key Concepts Explained

●​ Approval Process: A setup in Salesforce that manages how records (like requests or discounts) are
reviewed and approved, routing them to the right people based on rules.
●​ Approval Steps: Multiple review stages, each with its own approvers and criteria.
●​ Multi-Level/Team Approval: The ability to request approval from several users, either sequentially (one
after another) or simultaneously (at the same time).
●​ Unanimous vs. First Response: Choose if all approvers must agree (unanimous) or if a single
approval/rejection is enough (first response).
●​ Automated Submission: Submitting records for approval automatically based on certain conditions,
reducing manual effort.

Step-by-Step Practical Instructions from the Video

Multi-Step, Multi-User Approval Process

1.​ Go to Setup:​
Search for "Approval Processes" in the Quick Find box.
2.​ Select the Object:​
Choose the Salesforce object (like Leave Request, Opportunity) that needs an approval process.
3.​ Create a New Approval Process:
○​ Use the wizard to set the process name and entry criteria (e.g., discount > 10%).
1.​ Add Approval Steps:
○​ For each step, specify the conditions and assign one or more approvers (by user, role, or
queue).
○​ Decide if approval is based on first response or requires unanimous consent.
○​ You can assign multiple users to a step and choose how their responses determine the
outcome.
1.​ Define Step Actions:
○​ Set up actions for approval, rejection, or when extra information is needed (like sending emails
or updating fields).
1.​ Automated Triggers:
○​ Use formulas or process builders to automatically submit records for approval under certain
conditions (e.g., leave days > 10).
1.​ Activate and Test:
 ○​ Activate your process, then test by creating a record to ensure it goes through all steps
correctly.

Example Scenario from the Video

●​ For a leave request:
○​ If the leave is more than 10 days, it requires the manager and HR approval (unanimous).
○​ If the leave is 3 days or less, the manager’s approval alone is enough (first response).

5 Interview Questions and Answers

Question Sample Answer
It involves more than one stage, where each step can have different
What is a multi-step approval process
approvers and criteria. A record may move through several levels of
in Salesforce?
review before approval.
How can you assign multiple You can add several users or roles as approvers in a single step. You can
approvers to a step, and what are the require unanimous approval or accept the first responder’s decision for the
options? outcome.
What is the difference between Unanimous means every assigned approver must approve for the record
unanimous and first response to progress; first response means one decision (approval or rejection)
approval logic? finalizes the step.
By using criteria in the approval process or with automation tools like
How can approval processes be
Process Builder, you can submit records for approval without the user
triggered automatically in Salesforce?
clicking a button.
It ensures the process works as intended—records follow the correct path,
Why is testing an approval process
notifications are sent, and actions are triggered for each step and
important in Salesforce?
outcome.
Episode 8 : Managing Data Access in Salesforce | Profiles |
Permission Sets | Role | FLS
This video explains how data access is managed in Salesforce, especially focusing on three major tools:
Profiles, Permission Sets, and Roles. It covers how these tools control what users can see and do in
Salesforce, including setting up restrictions so that only the right people have access to particular data. You’ll also
learn about Field Level Security (FLS), which lets you control access to specific fields in your Salesforce
records, and about basic user management features.

Key Step-by-Step Practical Instructions

1. Managing Profiles
●​ Profiles decide what a user can do (like view, edit, or delete information).
●​ To edit a Profile:
1.​ Log in to your Salesforce account.
2.​ Click the gear icon → Setup.
3.​ In the Quick Find box, type “Profiles.”
4.​ Select the Profile you want to change, then update permissions as needed.

2. Using Permission Sets

●​ Permission Sets add extra permissions to a user, without changing their overall Profile.
●​ To create and assign a Permission Set:
1.​ In Setup, search for “Permission Sets.”
 2.​ Click New to create a new set.
3.​ Assign the Permission Set to users who need extra access.

3. Understanding Roles
●​ Roles control what records a user can see based on their place in the company hierarchy.
●​ Example: A manager may see records their team creates.

4. Setting Field Level Security (FLS)

●​ FLS decides if a user can view or edit a specific field in a record.
●​ To set:
1.​ Go to Setup, type “Profiles” or “Permission Sets” in Quick Find.
2.​ Select the relevant profile or set.
3.​ Go to “Field Level Security” section.
4.​ Choose which fields the user can “Read” or “Edit.”
5.​ Click Save.

5. User Management Basics

●​ Add or edit users by navigating to Setup → Search “Users.”
●​ Assign the correct Profile and, if needed, a Role and Permission Sets.
●​ Users can only have one profile but may have multiple permission sets.

5 Interview Questions and Answers

Question Sample Answer
1. What is the difference
A Profile sets the basic permissions for what a user can do, like access objects
between a Profile and a
and fields. A Permission Set adds extra permissions on top of the profile, without
Permission Set in
changing it.
Salesforce?
2. How do Roles affect what Roles control record-level visibility, so users higher in the role hierarchy can see
users see in Salesforce? records owned by users below them, useful for managers or team leads.
3. What is Field Level Field Level Security lets you control who can see or edit certain fields in an
Security, and how do you set object. Set it by editing the profile or permission set, locating the Field Level
it? Security section, and choosing Read/Edit access for each field678.
4. Can a user have more than
Each user can have only one Profile but can be assigned multiple Permission
one Profile or Permission
Sets to give them extra access they need.
Set?
5. What are some common
Creating/editing users, assigning profiles/roles/permission sets, resetting
user management tasks for
passwords, freezing or deactivating users if needed, and managing login access.
Salesforce Admins?
Episode 9 : Who Sees What in Salesforce OWD & Sharing Settings |
Profiles Vs Roles | Record Sharing
This video explains how Salesforce controls who can see and do what with data, using security settings and
sharing tools. It covers the basics of Salesforce data access: who owns records, who can share data, and how
settings are used to keep data secure but accessible to the right people. The main features discussed are
Organization Wide Defaults (OWD), record sharing, profiles, and roles.

Key Step-by-Step Processes and Practical Instructions

1. Understanding OWD (Organization Wide Default)
●​ OWD sets the baseline access for records in Salesforce.
●​ For each object (like Accounts or Opportunities), set the default level: Private, Public Read Only, or
Public Read/Write.
○​ Private: Only the record owner and their managers can access.
○​ Public Read Only: Everyone can read, but only owners/editors can change.
○​ Public Read/Write: Everyone can read and change.

2. Record Ownership
●​ The person who creates a record is its owner.
●​ Owners can view, edit, delete, and share their records.

3. Record Sharing
●​ Even if OWD is Private, you can share individual records with others by:
1.​ Opening the record.
2.​ Selecting “Sharing.”
3.​ Adding the user or group to share with.
4.​ Choosing what level of access (Read/Write).
5.​ Saving changes.

4. Using Profiles vs. Roles

●​ Profiles decide what users can do: access objects, fields, or actions.
●​ Roles decide what users can see (at record level) based on their position in the company.
○​ Users higher in the role hierarchy see data owned by their subordinates.

5. Scenario Example
●​ If OWD for Opportunity is Private, a manager can still see team members' opportunities if the manager
is higher in the role hierarchy.

5 Interview Questions & Answers

Question Sample Answer
OWD stands for Organization Wide Default. It sets the baseline
1. What is OWD in Salesforce? level of access that users have to each other's records in
Salesforce.
A profile controls what a user can do (permissions), while a role
2. What is the difference between a Profile
controls which records a user can see, mainly by where they are in
and a Role?
the company's hierarchy.
You can use “Manual Sharing” by going to the record, clicking
3. How can you share a single record with
"Sharing," and granting access to a user or group for that specific
another user if the OWD is Private?
record.
4. Who is considered the owner of a
The person who creates or is assigned a record is its owner. The
record in Salesforce, and what can they
owner can read, edit, delete, and manually share the record.
do?
5. Can a user higher in the role hierarchy Yes, as long as the "Grant Access Using Hierarchies" setting is
see data owned by people below them if enabled, users higher up can see records owned by their
OWD is Private? subordinates.12
Episode 10 : Ep 10 – Audit & Troubleshoot Salesforce Data | Debug
Logs | Email Logs | Login History
This video from the "Salesforce Admin Training" playlist explains how Salesforce admins can audit, monitor, and
troubleshoot activities and issues in their Salesforce organization. The session covers practical tools and
features—like debug logs, audit trails, field history tracking, email logs, login history, and IP
whitelisting—that help you understand what happened in your Salesforce environment and who made those
changes. The video gives step-by-step guidance on how to use these tools, helping even complete beginners
gain confidence in maintaining a secure and well-functioning Salesforce setup.

Key Concepts Explained (In Detail)

●​ Debug Logs:​
A tool for recording every step, error, and process that runs in Salesforce—useful to diagnose problems
when things aren't working as expected.
●​ Audit Trail:​
Tracks administrative and setup changes in Salesforce, letting you see which admin changed what and
when.
●​ Field History Tracking:​
Lets you keep a record of changes to specific fields on standard or custom objects—helpful to
investigate data changes or undo mistakes.
●​ Email Logs:​
Provide records of every email sent from Salesforce, so you can investigate delivery issues, confirm
communication, or troubleshoot email failures.
●​ Login History:​
Shows detailed information on all login attempts—successful and failed—including the user, IP address,
and login time.
●​ IP Whitelisting:​
Enhances security by restricting access only to approved IP addresses, helping prevent unauthorized
logins.

Step-by-Step Practical Instructions

1. How to Enable and Use Debug Logs

●​ Go to Setup in Salesforce.
●​ Use the Quick Find to search for Debug Logs.
●​ Click New to add a log for a specific user.
●​ Set the duration, user, and debug level (what should be tracked: Apex, workflows, etc.).
●​ Save your settings.
●​ Perform the action in Salesforce you want to monitor.
●​ Return to Debug Logs to review what happened step by step.

2. How to Request Email Logs

●​ Open Setup and search for Email Log Files.
●​ Enter the date range you want to review (up to 30 days in the past).
●​ Provide your email address and submit the request.
●​ Check your email for a CSV file you can download, open, and review.
3. How to Check the Setup Audit Trail
●​ In Setup, search for View Setup Audit Trail.
●​ See the 20 most recent changes made by users/admins.
●​ Download the CSV file for older changes and detailed logs.

4. How to Enable Field History Tracking

●​ In Setup, visit the object (like Account or Opportunity) whose fields you want to track.
●​ Click Fields & Relationships, then Set History Tracking.
●​ Choose which fields you want to track and save.
●​ On the object's page layout, add the Field History related list so users can see tracked changes on
records.

5. How to Set Up IP Whitelisting

●​ Go to Setup and search for Network Access.
●​ Click New to add an IP range.
●​ Enter the start and end IP addresses allowed to connect.
●​ Save—only users connecting from these IPs can log in.

5 Potential Interview Questions & Answers

Interview Question Suggested Answer
Debug Logs record all actions, processes, and errors for a user, which
1. What is the use of Debug Logs in
helps admins troubleshoot bugs, errors, and workflow issues in their
Salesforce?
Salesforce org.
2. How can you track who made a
Use Field History Tracking to see who changed specific data fields, and
change to a record or setup in
the Setup Audit Trail to track configuration and administrative changes.
Salesforce?
3. What is the purpose of Email Email Logs show all emails sent from Salesforce with delivery details. You
Logs, and how do you access request them from Setup by specifying a date range and receiving a CSV
them? file via email.
4. How does IP Whitelisting It restricts logins so only users from specified IP addresses can access
improve Salesforce security? Salesforce, blocking unauthorized users not on the whitelist.
5. What information can you find in Login History provides records of all logins and attempts, showing the
Salesforce Login History? username, time, IP address, and whether the login succeeded or failed.
Episode 11 : Data Management in Salesforce | Dataloader Vs import
wizard | Uploading Relational Data
This video is about data management in Salesforce, focusing on two main tools: Data Import Wizard and Data
Loader. It explains how to import, update, and export data and discusses the differences between these tools.
The video also covers how to manage connected (relational) data and important points to remember when
handling data in Salesforce.

Step-by-Step Processes and Key Practical Instructions

1. Importing Data Using the Data Import Wizard

●​ Go to Setup in Salesforce.
●​ Search for “Data Import Wizard.”
 ●​ Start the Wizard and choose the standard or custom object you want to import (e.g., Accounts,
Contacts).
●​ Upload your CSV file with the data.
●​ Map the fields in your file to Salesforce fields.
●​ Review and confirm the mappings.
●​ Start the import and wait for confirmation.

2. Updating Records Using Data Loader

●​ Install Data Loader on your computer.
●​ Log in with Salesforce credentials.
●​ Choose the operation (Insert, Update, Upsert, Delete, Export).
●​ Select the object to modify (e.g., Accounts).
●​ Upload the CSV file (for updating, must include Record IDs).
●​ Map the fields between CSV and Salesforce.
●​ Run the update and check success/error files generated.

3. Exporting Data
●​ Use either Data Export Wizard (from Setup in Salesforce) or Data Loader to extract your data for
backup or analysis.

4. Importing Relational Data

●​ Import parent records first (e.g., Accounts).
●​ Note the Salesforce Record IDs for parent records after import.
●​ Add parent Record IDs to child data file (e.g., Contacts, referencing parent Account IDs).
●​ Import the child records using Data Loader or Import Wizard.

Key Concepts Explained

●​ Data Import Wizard: A browser-based tool in Salesforce to import simple data (like leads or contacts)
and is easy for beginners. It does not require installation.
●​ Data Loader: An advanced, downloadable tool suitable for large volumes of data and more complex
operations (like updating and deleting).
●​ Record ID: A unique identifier for each record in Salesforce, vital for updating existing records and for
handling relational data imports.
●​ Soft Delete vs. Hard Delete:
○​ Soft Delete: Deleted records go to the Recycle Bin and can be recovered.
○​ Hard Delete: Records are permanently removed and cannot be recovered.
●​ Best Practices: Always back up data before making changes, understand field mappings, and check
for errors after import or updates.

5 Interview Questions & Answers

Interview Question Sample Answer
1. What is the difference Data Import Wizard is a web-based tool for simple data imports, suitable for
between Data Import standard objects and up to 50,000 records. Data Loader is a desktop tool for
Wizard and Data Loader in handling larger data sets (up to 5 million records), allows updates and deletes,
Salesforce? supports all objects, and is used for more complex tasks1.
2. How do you ensure data
Import the parent records first, get their Salesforce Record IDs, then use those IDs
relationships are
as references (foreign keys) in the child records' CSV file before importing the child
maintained when importing
data1.
related records?
3. Why is the Record ID
The Record ID uniquely identifies each record. When updating data, including the
important during data
Record ID ensures the correct record is updated and avoids creating duplicates1.
updates in Salesforce?
4. What’s the difference A soft delete sends the record to the Recycle Bin, enabling recovery if needed. A
between soft delete and hard delete permanently removes the record from Salesforce and it cannot be
hard delete in Salesforce? restored1.
5. What steps do you follow
Install and open Data Loader, log in, choose the Update operation, select the object,
to update records in
upload your CSV file with Record IDs, map the fields, run the update, and review
Salesforce using Data
results for success and errors
Loader?

Episode 12 Salesforce Admin Training: Reports &

Dashboards (Beginner Summary)
Simple Video Summary
This video teaches beginners how to use Salesforce Reports and Dashboards to analyze and present data. It
explains different report types, demonstrates creating and customizing reports, shows how to build dashboards
for visual summaries, and covers sharing and scheduling these for regular updates. The session is
beginner-friendly and uses simple, clear examples to help you understand the basics1.

Step-by-Step Processes and Practical Instructions

1. Understanding Report Types

●​ Standard Report Types: Predefined by Salesforce, available for standard objects like Accounts and
Opportunities.
●​ Custom Report Types: Created when you need specific fields or want reports on custom objects or
unique relationships.

2. Creating a Basic Report

●​ Go to the Reports tab.

●​ Click "New Report".
●​ Select the object (e.g., Opportunities).
●​ Choose the report type (tabular, summary, matrix, or joined).
●​ Add or remove columns as needed.
●​ Use filters (e.g., "All Opportunities", by date range, or by status).
●​ Click “Run” to view data.

3. Grouping and Summarizing Data

●​ To group by a field (e.g., Stage):

○​ Edit the report and drag the field to the grouping area.
○​ Summarize by count, sum, average, min, or max.
●​ Add charts (bar, line, donut) for visual analysis.

4. Creating and Using Report Folders

●​ Reports can be saved in folders:

 ○​ Private (only you) or
○​ Public/shared (for teams).
●​ Organize folders and use subfolders for neat management.

5. Creating Custom Report Types

●​ Go to Setup > Report Types.

●​ Click “New Report Type”.
●​ Select the primary object.
●​ Optionally add related objects.
●​ Configure which records and fields are available.
●​ Deploy and use this new report type for more customized reports.

6. Using Join Reports

●​ Allows you to pull data from multiple, related objects into one report (e.g., Accounts + Opportunities +
Cases).

7. Sharing and Scheduling

●​ Reports and dashboards can be shared with users or teams.

●​ You can schedule reports/dashboards to be sent automatically via email (e.g., daily, weekly).

8. Practical Tips

●​ You can display up to 2,000 records in the UI; export to CSV/Excel for up to 20,000.
●​ Use filters, grouping, and bucketing to tailor reports to your needs.
●​ Bucketing lets you categorize values for easier reporting.

Key Concepts (Explained for Beginners)

●​ Reports: Tools to display data from Salesforce objects in formats such as tables, summaries, matrices,
and joins.
●​ Dashboards: Visual displays (charts, graphs) that show one or more reports in a single view for easy
analysis.
●​ Standard vs Custom Report Types: Standard are out-of-the-box; Custom are for tailored needs
across multiple/related objects.
●​ Filter: Customize which records appear in your report using criteria like date or status.
●​ Grouping: Organize rows in a report based on a specific field (e.g., by Stage, by Account).
●​ Bucketing: Create categories for report values (e.g., group opportunity stages into “Open,” “Closed”).
●​ Join Reports: Combine multiple related reports into one view.
●​ Sharing/Scheduling: Make sure the right people see your reports/receive emailed updates regularly.

5 Interview Questions & Sample Answers

Interview Question Sample Answer
What are the different Salesforce provides Tabular, Summary, Matrix, and Join reports. Tabular is simple
Salesforce report types, listing data; Summary allows grouping and subtotals; Matrix enables grouping rows and
and when would you columns; Join combines data from different objects. Use Summary for group analysis,
use each? Matrix for cross-tab views, and Join for multi-object data1.
How do you create a
Go to Reports, choose Opportunities, select Summary format, drag the “Stage” field to
summary report to show
grouping, and add “Amount” to the table. You’ll see totals for each stage. Add a chart
Opportunity amounts by
for visual analysis if needed1.
Stage?
A Custom Report Type is user-defined and lets you pull fields from parent and child
What is a Custom
objects not available in standard types. Create one when you need fields or
Report Type, and why
relationships not available in the standard selection, such as showing Accounts with or
would you create one?
without Contacts1.
How do you share a
After creating or running a report, save it in a shared folder. Use the “Subscribe” or
report with your team
“Schedule Future Runs” feature, choose timing (e.g., weekly), and add team members’
and schedule it to run
emails. They’ll get the report automatically at the set intervals1.
automatically?
What is bucketing in Bucketing lets you categorize field values into named groups right in the report builder
Salesforce reports and (e.g., group various Opportunity stages into “Active,” “Closed”). This makes reports
how is it used? easier to read and analyze without changing the underlying data1.
Episode 13 : Salesforce order of execution
This video explains the Salesforce Order of Execution, which is the sequence in which Salesforce processes
actions, automation, and rules when a record is created or updated. The presenters use easy-to-follow examples
(like painting a house with different colors) to show how each automation (triggers, workflow rules, processes,
and flows) affects the record and how they interact. You’ll learn why records sometimes update unexpectedly or
run into errors, and why understanding these steps is critical for anyone who works with Salesforce—even
beginners.

Key Concepts (Explained Simply)

What is "Order of Execution"?

●​ It’s the specific order Salesforce follows when saving a record—like a checklist.
●​ It covers how validations, triggers, workflows, process builders, and flows are run and can affect the
same record.
●​ Knowing this order helps you predict and control what happens when you or others automate things in
Salesforce.

Why Does It Matter?

●​ If you don’t know the order, your automations can interfere with each other.
●​ Problems like records duplicating, being deleted, or hitting platform limits (errors) often relate to this
order.

Most Important Steps in Order of Execution

●​ Validations: Salesforce checks if the data entered is correct.
●​ Before Triggers: Custom code runs before the record is saved.
●​ Workflows/Process Builders/Flows: Automated rules and actions that can update the record again,
sometimes cycling back (recursion).
●​ After Triggers: More custom code can run after workflows/processes.
●​ Commit: Finally, all changes are saved in the database.

Special Considerations
●​ Recursion: Automations can trigger each other multiple times, causing loops or "ping-pong" effects.
 ●​ Platform Limits: Salesforce has limits on how many times an automation can run (like CPU time or
records processed) to stop runaway processes.
●​ Error Handling: If something fails at the end of the process, all changes are rolled back—nothing is
saved.

Step-by-Step Practical Instructions & Process Highlights

1.​ When you save a record:
○​ Salesforce runs system validations (checks the data).
○​ Custom validations and "before" triggers are executed.
○​ Workflows, Process Builders, and Flows that act on the record are processed.
○​ These automations might trigger additional “before” or “after” triggers.
○​ The record is finally saved ("commit"), and post-commit actions like sending emails happen.
1.​ Working with Automations:
○​ If you set up multiple automations (triggers, workflows, etc.), remember that:
■​ Each can fire the other, sometimes creating an endless loop.
■​ Use options in Process Builder and Workflow rules (like "re-evaluate") carefully.
○​ You can check how your automations run by viewing the Salesforce debug log (set to "finest" or
"finer" to see all the details).
1.​ Best Practices:
○​ Use one trigger and one process per object if possible—simplifies debugging and reduces
complexity.
○​ Avoid mixing too many automations (especially old workflows with new flows/processes) on the
same object.
○​ Test with lots of data—even if it works for a few records, problems can appear later with more
data or more automations.

Detailed Key Concepts

●​ Triggers: Custom code that runs before or after a record is saved.
●​ Workflows and Process Builder: Point-and-click tools for automation; can update records, send
emails, or create tasks.
●​ Recursion: When an automation causes another automation to run again on the same record,
sometimes endlessly.
●​ Order of Execution: The sequence in which Salesforce applies rules, checks, automations, and saves
changes. Not knowing this order is a major source of bugs and unexpected behavior.
●​ Debugging: Use the Developer Console and debug logs to visualize and troubleshoot how automations
interact.
●​ Platform Events: Some automations (like Platform Events) can fire after commit, meaning they happen
after the record is saved and sometimes don’t roll back if there’s an error.
●​ Limits: Automations can run into platform limits (like maximum CPU time or records processed). These
are there to protect system performance.

5 Possible Interview Questions and Model Answers

Interview Question Model Answer
The Salesforce Order of Execution is the fixed sequence Salesforce follows to
1. What is the Salesforce
process automations, validations, and data changes when a record is saved. It's
Order of Execution, and
important because if you don't understand it, your automations might conflict, cause
why is it important?
errors, or lead to unexpected results1.
Recursion happens when an automation (like a workflow or process) causes another
2. Can you explain what
automation to run again on the same record—sometimes multiple times, creating a
recursion is in the context
loop. This can cause records to be updated many times or hit system limits, resulting
of Salesforce automations?
in errors or slow performance1.
3. What are best practices
The best practice is to have only one trigger and one process per object, if possible.
for combining triggers and
Avoid mixing too many types of automations on one object, as this makes it hard to
process builders or
predict the order in which things happen and much harder to debug1.
workflows?
Use the Developer Console to view debug logs, set the profiling log level to "finer" or
4. How would you debug
"finest," and review the order and timing of automation steps. Look for repeated
an automation issue in
steps (loops) or conflicts. This helps find where automations are causing unexpected
Salesforce?
results or hitting limits1.
If an error happens at any stage before the commit, Salesforce rolls back all
5. What happens if an error
changes—nothing is saved, and error messages are shown. Auto-number fields are
occurs during the Order of
also reset. This ensures data integrity, but you need to debug to find out what went
Execution?
wrong1.
Episode 14 : Sharing and Visibility With Salesforce
This video explains how sharing and visibility work in Salesforce—who can see what records, and how you
control access to information. The presenter uses clear examples and easy instructions, making it
beginner-friendly. You’ll learn what record ownership means, how roles and settings influence visibility, and how
sharing rules allow you to give users access when they need it. The session goes through both the concepts and
practical steps, so you can try them out in your own Salesforce setup.

Key Concepts (Explained Simply)

1. Record Ownership
●​ Every record in Salesforce has an owner. The owner can view and edit the record.
●​ Ownership is central to how sharing works—think of it like "owning" a document in Google Docs.

2. Organization-Wide Defaults (OWD)

●​ Sets the baseline level of access to records for everyone.
○​ Public Read/Write: Everyone can view and edit.
○​ Public Read Only: Everyone can view, only owners/editors can change.
○​ Private: Only the owner and people above them (like managers) can view/edit.

3. Role Hierarchy
●​ Think of a company org chart. People higher in the role hierarchy can see what their team owns.
●​ Good for managers to see their team's work, but not vice versa.

4. Public Groups
●​ A way to bundle users together by department or role so you can share records with a group
instead of one-by-one.

5. Sharing Rules
●​ Extra rules to open up access based on criteria, like sharing all “Customer” accounts with the
Finance team.
●​ There are two main types:
○​ Owner-based: Share records owned by certain users or roles.
○​ Criteria-based: Share records that meet certain conditions.
6. Manual Sharing
●​ Letting users share a single record with specific people, just for that one case.

7. Team Sharing
●​ Account Teams, Opportunity Teams, or Case Teams allow collaboration—think of adding teammates
to a project so they can see/edit the same info.

8. Territory Management
●​ Used by larger organizations to designate territories (regions, teams) and share records accordingly.

9. Other Sharing Tools (Advanced)

●​ Permission Sets, Profiles, and Apex Sharing: Give access at a very detailed level or using code
(most useful for advanced admins).

Step-by-Step Practical Instructions & Processes Highlighted

To Set Organization-Wide Defaults (OWD)

1.​ Go to Setup.
2.​ Search for "Sharing Settings".
3.​ Set the OWD for each object (like Accounts, Opportunities, etc.) to Public, Private, or Read Only
depending on your needs.

To Create a Role Hierarchy

1.​ In Setup, search for "Roles".
2.​ Create new roles for your organization (like Sales, Support, CEO).
3.​ Assign users to appropriate roles.
4.​ Remember: Only managers should be able to see everything below them.

To Create Public Groups

1.​ In Setup, search for "Public Groups".
2.​ Create a new group, add users, and assign roles or other groups.
3.​ Use these in sharing rules to make access granting easier.

To Add Sharing Rules

1.​ Go to "Sharing Settings".
2.​ Under the object, click "New" next to “Sharing Rules.”
3.​ Choose owner-based or criteria-based.
4.​ Set which users/groups will gain access and what type of access (read, edit).
Manual Sharing (Single Records)
1.​ Open the specific record in Salesforce.
2.​ Click the "Sharing" button.
3.​ Select users or groups you want to share with and define their access level.

Account/Opportunity Teams
1.​ Enable account/opportunity teams in Setup.
2.​ On a record, add users to the team, set their roles, and choose their access.

5 Possible Interview Questions with Model Answers

Interview Question Model Answer
What is record ownership in Record ownership means a specific user (or queue/territory) is responsible for a
Salesforce, and why is it record. Owners have unique rights—like editing and sharing—making ownership
important? crucial for security and collaboration.
How do Organization-Wide OWD set the minimum level of record access across the company. For example, if
Defaults (OWD) affect data OWD is set to Private, only owners and managers can see those records, unless
visibility? rules or sharing open it up.
What’s the difference Sharing rules automate access for groups based on ownership or criteria, while
between sharing rules and manual sharing is when a user gives access to a single record on a case-by-case
manual sharing? basis.
Users at higher roles automatically get access to records owned by users in roles
How does the role hierarchy
beneath them, allowing managers to oversee their teams’ work. It’s about upward
control data access?
visibility.
When should you use a Public groups help you grant access to multiple users at once, making sharing
public group in Salesforce rules scalable—such as sharing all customer accounts with the entire Finance
sharing? department.
Episode 15 : Sandbox Design Strategies for Enterprise
Implementations
This video explains Salesforce Sandboxes—what they are, why they’re important, the different types, and
strategies for using them in real-world Salesforce projects. Imagine a sandbox as a safe playground where you
can build, test, and experiment without harming your actual live data. The speakers use simple analogies and
examples to help beginners understand how to use Sandboxes effectively, especially as your team or project
grows.

Key Concepts Explained Simply

What Is a Salesforce Sandbox?

●​ Sandbox = Safe Copy of Salesforce: It’s like a test version of your Salesforce where you can try things
out, build, and practice without affecting the real (production) Salesforce system.
●​ Used for: Development, testing, and training.

Types of Sandboxes
●​ Developer Sandbox: Small, for building and unit testing by individuals.
●​ Developer Pro: Like Developer, but allows more data—useful for teams needing more storage for
testing.
 ●​ Partial Copy Sandbox: Contains some real data—good for training or more realistic testing.
●​ Full Copy Sandbox: Complete copy of your live (production) system—best for big testing, staging, or
simulating ‘the real thing’ before launching changes.

Sandbox Key Features

●​ Sandbox Templates: Let you choose which data or objects to copy into your sandbox—saves space
and targets testing.
●​ Sandbox Cloning: Lets you copy an existing sandbox setup quickly.

Sandbox Quotas
●​ Salesforce gives you a set number of sandboxes based on your edition (e.g., Professional, Enterprise)
and licenses.

Agile Development Life Cycle in Salesforce

1.​ Start with an Idea: Convert business needs into user stories.
2.​ Development: Build and test in a sandbox.
3.​ QA & User Testing: Move changes to bigger sandboxes for more realistic testing.
4.​ Staging: Place fully tested changes here before sending to your live Salesforce (production).
5.​ Production Release: Launch final changes to the real system.

Typical Sandbox Use Cases

●​ Development: Small sandboxes for individual developers.
●​ Integration Testing: Medium sandboxes where teams combine work and test together.
●​ User Acceptance Training (UAT): Larger sandboxes to mimic the real world for end-users to test.
●​ Performance & Load Testing: Full sandboxes to test with large amounts of data.
●​ Staging: Final step before going live.

Sandbox Strategies
Depending on your team/project size:

●​ Small teams: Use a couple of sandboxes, simple flow.

●​ Larger/Enterprise teams: Multiple sandboxes for various teams, parallel development, integration, and
data migration—helps avoid mistakes and keep processes smooth.

Step-by-Step Practical Instructions & Highlights

How to Use Sandboxes in a Project

1.​ Development:
○​ Assign small (Developer) sandboxes to each developer for building and initial testing.
1.​ Integration:
○​ Combine and test everyone’s changes in a larger sandbox (Developer Pro or Partial Copy).
1.​ UAT & Training:
○​ Use Partial Copy or Full Copy sandboxes to mimic live data for business user testing and
training.
 1.​ Staging:
○​ Move all tested features into a Full Copy sandbox before “going live.”
1.​ Release:
○​ Move changes from staging (Full Copy sandbox) into production when everything is ready.

Best Practices
●​ Never build or test directly in production.
●​ Refresh sandboxes regularly to keep data updated, but be mindful of refresh limits.
●​ Use sandbox templates to include only needed data, saving space and time.
●​ Give each team or developer their own sandboxes to avoid conflicts.
●​ Test all changes step-by-step in larger sandboxes before release.

5 Possible Interview Questions & Answers

Interview Question Model Answer
What is a Salesforce A Salesforce sandbox is a safe test environment that lets you experiment, develop,
Sandbox and why is it and test new features or changes without affecting live data. It helps prevent errors in
important? the real system and supports smooth releases.
Name and briefly describe - Developer: Small, for individual use; Developer Pro: More storage for bigger team
the main types of testing; Partial Copy: Includes a subset of real data for realistic testing and training;
sandboxes in Salesforce. Full Copy: Complete copy of production for full testing and staging.
Use a Full Copy sandbox when you need to test features using real data, do
When should you use a
performance checks, or run final tests (staging) before releasing to production—it’s
Full Copy sandbox?
best for simulating the real environment.
What are sandbox Sandbox templates let you choose which objects and data to copy into your sandbox.
templates and why are This helps you save space and time by copying only what you need for specific testing
they useful? or training tasks.
Describe a typical For large projects, give each developer or team their own sandbox, use integration
sandbox strategy for a sandboxes to combine and test, perform user testing in Partial or Full Copy
larger Salesforce project. sandboxes, and use staging sandboxes before finally moving features into production.
Episode 16 : Formulas & Admin Life Hacks
This video, “Formulas & Admin Life Hacks with Steve Molis,” is a practical guide focused on making everyday
tasks much easier for Salesforce administrators—especially if you’re just getting started. The presenter shares
easy, beginner-friendly explanations and clever tips about using formulas in Salesforce to automate calculations,
simplify processes, check data quality, and solve common business needs. Steve also discusses useful shortcuts
(“life hacks”) that save time and reduce mistakes in your Salesforce org1.

Key Concepts Explained Simply

1. What is a Formula in Salesforce?

●​ A formula is like a math or logic equation you add to a field. It can do calculations automatically, create
custom data, or check if information is entered correctly.
●​ You can use formulas in formula fields, validation rules, workflow rules, and more.

2. Types of Formula Fields

●​ Simple Math: Add, subtract, multiply, or divide number fields.
●​ Text Manipulation: Combine names, dates, or text automatically.
●​ Logical Checks: Use IF/ELSE logic to control what shows.
 ●​ Date Calculations: Work out days between dates, due dates, or ages.

3. Real-World Use Cases

●​ Automatically calculate discounts or commissions.
●​ Show a colored warning if information is missing or incorrect.
●​ Combine names to create custom record labels.
●​ Calculate how many days a case has been open.

4. Life Hacks for Admins

●​ Copy/Paste Efficiency: Use template formulas and adapt them for different needs.
●​ Testing: Always test your formula in a sandbox before adding it to production.
●​ Commenting: Add comments in formulas so others know how they work.
●​ Troubleshooting: Use error messages that explain what users need to fix.
●​ Learning Resources: Use Salesforce Trailhead and the help community for inspiration.

Step-by-Step Practical Instructions Highlighted

1.​ Creating a Formula Field
○​ Go to the Object Manager in Setup.
○​ Choose or create a new custom field and select "Formula" as the type.
○​ Pick what kind of output you want (Number, Text, etc.).
○​ Enter your formula using field names and functions.
○​ Test your formula using the preview feature.
○​ Save and add it to page layouts.
1.​ Sample Formula—Using IF Logic
○​ Example: Show "YES" if Opportunity > $10,000, "NO" otherwise:​
​
​
​
text​
​
IF(Amount > 10000, "YES", "NO")
○​ ​
​
​
​

1.​ Creating Validation Rules

○​ Go to the object (like Account or Opportunity).
○​ Click "Validation Rules" and then "New."
○​ Enter the logic (for example, check if a field is blank).
○​ Add an error message that clearly tells users what to fix.
1.​ Common Formula Functions
○​ ISBLANK(): Checks if a field is empty.
○​ LEN(): Counts how many characters are in a field.
○​ CONCAT(): Joins pieces of text together.
○​ TODAY(), NOW(): Inserts the current date/time.

Detailed Key Concepts

 ●​ Formula Syntax: Careful use of parentheses, operators (+, -, *, /), and functions.
●​ Testing and Error Handling: Always double-check formulas and include friendly error messages.
●​ Reusability: Create templates you can tweak for similar requirements.
●​ Documentation: Writing notes straight in your formula fields.
●​ Sandbox Testing: Try all changes in a test environment before moving to your live org.

5 Possible Interview Questions and Model Answers

Interview Question Model Answer
A formula field is a custom field that automatically calculates values using
1. What is a formula field in
other fields, math, logic, or text functions—saving time and ensuring data
Salesforce and how is it used?
stays accurate.
2. Give an example of how you’d I’d use a validation rule with a formula like ISBLANK(Field) to stop users
use a formula to improve data entry from saving records if important information is missing, ensuring all data is
quality. complete.
3. What’s a best practice when
Always write clear, commented formulas and test them in a sandbox first to
writing formulas as a Salesforce
prevent errors in the live system. Include helpful error messages for users.
admin?
4. Name two useful formula ISBLANK(): Checks if a field is empty; CONCAT(): Combines multiple text
functions and their purpose. fields into one value. Both simplify and automate checks or labeling.
Create or change the formula in a sandbox, use test records to confirm it
5. How do you troubleshoot or test
behaves as expected, and read any system error messages to fix issues
a new formula?
before going live.
Episode 17: Salesforce Lightning Flow & Flow Builder —

What This Video Covers

This video is an introduction to Salesforce Flow Builder. It’s designed to help beginners understand how to
automate business processes in Salesforce using a codeless, drag-and-drop tool called Flow. The instructor
explains the purpose, types, and best practices of building flows, and demonstrates step-by-step how to create
two common types: Auto-Launched Flows and Screen Flows.

Key Concepts Explained (In Simple Terms)

●​ What is a Flow?
○​ A Flow is like a smart visual recipe that automates tasks in Salesforce without writing any
code.
○​ It helps in handling complex business logic: update records, make decisions, collect
information, and more.
●​ Types of Flows:
○​ Auto-Launched Flow
■​ Runs in the background automatically when a change happens (like a record is
created or updated).
■​ No user interacts directly with it.
○​ Screen Flow
■​ Involves user input; users see screens to fill in forms or step through processes.
●​ Process Automation Tools Hierarchy (from simple to advanced):
○​ Workflow rules: Basic “if this, then do that” steps.
○​ Process Builder: For more complex automation.
○​ Flow: Most flexible and powerful—all via clicks, not code!

Step-by-Step Practical Instructions Demonstrated

A. How to Create a Simple Auto-Launched Flow:

1.​ Access Flow Builder:

○​ Go to Salesforce Setup.
○​ Search for "Flows" and click "New Flow."
1.​ Select Flow Type:
○​ Choose "Auto-Launched Flow."
1.​ Set a Trigger:
○​ Configure the flow to start when an Account record is created or updated.
1.​ Add a Decision Element:
○​ Drag the Decision block to the canvas.
○​ Set the condition to check "If Account Phone Number is filled in (not empty)."
1.​ Add Assignment:
○​ If the phone number exists: Set the “Active” flag to TRUE.
○​ If not, leave the flag as FALSE.
1.​ Connect Elements:
○​ Link the steps to indicate the sequence: Start → Decision → Assignment(s).
1.​ Save, Activate, and Test:
○​ Save your flow and activate it.
○​ Test by updating an account’s phone number: Active flag should change automatically.

B. How to Create a Simple Screen Flow (With User Input):

1.​ Start a New Screen Flow:

○​ Go to “New Flow,” select “Screen Flow.”
1.​ Create a User Input Form:
○​ Drag a “Screen” element onto the canvas.
○​ Add fields like “Customer Name,” “Contact Name,” “Phone Number,” etc.
○​ Mark required fields as necessary.
1.​ Create Records:
○​ Use the "Create Records" element to generate new Account, Contact, and Opportunity records
based on user input.
○​ Carefully map form fields to Salesforce fields.
1.​ Link Records:
○​ Save the created Account ID.
○​ Use it to link the Contact and Opportunity to the right Account.
1.​ Add Success Screen or Redirect:
○​ Display a “Congratulations” message on completion.
○​ Provide a clickable link to the newly created Account for easy navigation.
1.​ Save, Debug, and Activate:
○​ Test the flow in debugging mode to check each step works as expected.
○​ Activate for real users.

Detailed Key Concepts

●​ Elements in Flow Builder:
○​ Variables: Store temporary information to use later in your flow.
○​ Decision: Like “if...then” logic to choose different paths.
○​ Assignment: Sets or changes the value within a variable or field.
○​ Get Records/Loop: Retrieve or repeat over several records (more advanced).
●​ Best Practices:
○​ Always write clear descriptions for each Flow element (helps you or others later).
○​ Give meaningful names to elements for easier future edits.
○​ Test flows before activating them to catch any errors early.
●​ Use Cases:
○​ Automating status changes (like the Active flag).
 ○​ Guiding users through multi-step forms (like onboarding a new customer).

Example Interview Questions (With Clear Answers)

Question Answer
1. What is the difference An Auto-Launched Flow runs in the background and is triggered automatically
between an Auto-Launched by certain actions (like record creation or updates) without user interaction. A
Flow and a Screen Flow in Screen Flow interacts with users, presenting forms and collecting input before
Salesforce? performing actions.
2. How would you automate a Create an Auto-Launched Flow triggered on Account creation or update. Use a
flag on an Account when a Decision element to check if the phone number field is filled. If it is, set the
phone number is entered? Active flag to TRUE using an Assignment element.
3. Why are meaningful names Names and descriptions keep the flow understandable and maintainable; they
and descriptions important help both the original builder and future admins or developers quickly grasp the
when building Flows? purpose of each element.
Flow elements include: Input screens, Decision branches ("if...then" logic),
4. What kinds of elements
Assignments (set values), Create/Update/Get Records elements (interact with
can you use inside a Flow?
Salesforce data), and Loop (for repeating over records).
After building, use the Debug feature in Flow Builder to step through the flow
5. How do you test if your
and check each action. For Auto-Launched Flows, test by performing the trigger
Flow works properly in
action in Salesforce and verifying the result. Activate the flow after confirming it
Salesforce?
works as expected.
Episode 18 : Outbound Message in Salesforce Workflow
This video explains how Salesforce can automatically send information to another system (like a different website
or app) using something called an Outbound Message through Workflow Rules. Outbound Messages help
keep two systems in sync or transfer data between them without any manual work, which is super helpful for
businesses.

Step-by-Step Process: How to Set Up an Outbound Message

1.​ Go to Salesforce Setup
○​ Log in to your Salesforce account.
○​ In the Setup area, search for “Workflow Rules”.
1.​ Create a New Workflow Rule
○​ Choose the object you want to work with (for example, “Account”).
○​ Click to create a new rule.
○​ Give your rule a name and (optionally) a description for clarity.
1.​ Set Evaluation Criteria
○​ Decide when the rule should run:
■​ Only when a record is created.
■​ Every time it is edited.
■​ When it changes to meet specific criteria.
1.​ Define Rule Criteria
○​ Set your rule to run only if certain conditions are true (e.g., “Account Name” is not blank).
1.​ Configure Workflow Actions
○​ Choose Immediate Workflow Action (runs instantly when the rule is triggered).
○​ Select Outbound Message from the available action options.
1.​ Configure the Outbound Message
○​ Enter details:
■​ Name of the outbound message.
■​ (Optional) Description.
■​ Endpoint URL: Where should Salesforce send the data? (Needs to be a real API
endpoint that can receive requests.)
 ○​ Pick which fields from the Salesforce object you want to send (e.g., Account Name, Account
Number, Salesforce ID).
1.​ Activate the Workflow Rule
○​ Save the rule and activate it so it starts working.
○​ Now, every time the criteria are met (like when a new account is created with a non-blank
name), Salesforce will automatically send the chosen information to the endpoint.
1.​ Test the Setup
○​ Create a sample record (e.g., a new Account).
○​ Verify if the data was sent to the endpoint.
1.​ Monitor Outbound Messages
○​ Use Salesforce’s monitoring tools to track if messages were sent successfully or failed.
○​ Note: Salesforce expects the endpoint to send back a special “acknowledgement” response. If
not received, Salesforce may mark the message as failed and try to send it again.

Key Concepts Explained for Beginners

●​ Workflow Rule: An automation in Salesforce that runs certain actions when records meet criteria.
●​ Outbound Message: Sends data automatically from Salesforce to another system by calling a URL (an
API endpoint).
●​ Endpoint URL: The address of the system you want to send data to. Must be able to receive messages
(not just any website).
●​ Immediate vs. Time-Dependent Actions: Immediate runs right away; time-dependent can be set to
run after a delay.
●​ Monitoring Outbound Messages: Salesforce shows a log of all such messages and whether they
succeeded or failed, helping you troubleshoot.
●​ Acknowledgement: The receiving system must respond correctly, or Salesforce thinks the delivery
failed.

5 Interview Questions and Answers

Question Answer
An Outbound Message is an automated way to send information from
1. What is an Outbound Message
Salesforce to another system, triggered by a workflow rule. It sends
in Salesforce Workflow?
selected Salesforce data to a specified endpoint (URL).
2. What are the key steps to create Steps are: Create a Workflow Rule → Set Evaluation & Rule Criteria →
an Outbound Message in Add an Immediate Action → Choose Outbound Message → Enter
Salesforce? Endpoint and Select Fields → Activate the Rule.
3. Why is the Endpoint URL The Endpoint URL specifies where Salesforce sends the data. It must be a
important in configuring Outbound valid server/API that can accept and process the message, otherwise, the
Messages? delivery will fail.
4. What happens if the receiving If Salesforce does not get the expected acknowledgement from the
system doesn't send the proper receiving system, it marks the outbound message as failed and will keep
acknowledgement? retrying delivery.
5. How can you monitor and Salesforce provides monitoring tools in Setup where you can see
troubleshoot Outbound Message successful and failed message attempts, review details, and understand if
deliveries? messages need attention or retries.
Episode 19 :Apex for Salesforce Admins

1. Understanding Admin Tools vs. Code

●​ Admin tools (like formulas, workflow rules, flows) use much of the same logic that code does.
●​ When you build a formula, you’re actually writing logic that Salesforce turns into “real code” behind the
scenes.
2. Key Practical Examples
●​ Formulas: Create calculated fields in Salesforce by combining values and logic, similar to writing small
code snippets.
●​ Reports: Selecting fields and filtering records is just like querying data using a coding language called
SOQL in Apex.
●​ Automation (Workflows, Process Builder, Flows): These run based on set criteria, like “if this
happens, then do that,” which is similar to conditional logic in coding.

3. Translating Admin Skills to Apex

●​ Creating Variables: In both declarative tools and code, you choose a type (like number or text), give it a
name, and store a value in it.
●​ Conditional Logic: “If this, then that” logic is called an “if statement” in code, like using the IF function
in formulas.
●​ Looping: Processing many records is like looping over a list in a flow or using a “for” loop in Apex.
●​ Querying Data: Using the report builder’s filters is nearly the same as writing a SOQL query in code:
○​ SELECT Name, Type FROM Account WHERE Type = 'Customer'

4. Apex Triggers & DML

●​ Apex Triggers: Specialized code that runs when records are created, updated, or deleted—just like
setting up automation to respond to record changes.
●​ DML (Database Manipulation Language): Lets you create, update, or delete records in code like you
do with declarative automation.

Detailed Key Concepts (Explained Clearly)

●​ Apex: Programming language designed by Salesforce, used to add highly customized behaviors that
aren't possible with point-and-click tools alone.
●​ Variables: Store information; must always define the type (number, text, record, etc.).
●​ Conditional Logic / If Statements: Code checks conditions and takes different actions based on what
it finds.
●​ Methods/Functions: Reusable blocks of logic (like a formula field or a process step).
●​ SOQL (Salesforce Object Query Language): Similar to SQL, lets you fetch data from Salesforce
records in code.
●​ Triggers: Automatically run pieces of Apex code when something happens to a record.
●​ Collections: Store multiple values (like a list of names or numbers).

Interview Questions and Detailed Answers

Question Answer
Both let you use logic, calculations, and field values to create new results.
1. How is writing a
Formulas use point-and-click and simple functions, while Apex code uses
Salesforce formula similar
programming syntax, but the main ideas (variables, conditions, logic) remain the
to writing Apex code?
same1.
2. What is SOQL and how SOQL stands for Salesforce Object Query Language. It lets you select data from
does it relate to creating a Salesforce records using code, similar to choosing fields and filters when building
report? a report1.

3. What is an Apex Trigger, An Apex Trigger is code that runs automatically when records are created,
and how is it like flows or updated, or deleted—just like automations in flows or process builder that react to
process builder changes in data. Triggers can handle more complex scenarios when clicks-only
automations? tools aren't enough1.
4. Why do variables in Apex Variables must know what kind of data they store so Apex can use them correctly.
need a type (like number or This is similar to choosing a “Data Type” when creating fields or variables in
text)? declarative tools1.
Identify the conditions (IF statements), variables, and actions. Write them as code,
5. How do you convert a
using Apex syntax but following the same logic flow. Most formulas and
formula or automation logic
automation steps translate directly into variables, methods, and conditional logic
into code?
in code1.