Module 1 — Salesforce Fundamentals
Understand the core of Salesforce and how businesses use CRM workflows.
What you will learn
- ✓Explain what Salesforce is and how it helps businesses manage customers and processes.
- ✓Understand CRM, objects, records, fields, and relationships in Salesforce.
- ✓Learn how data is organized and how users access it securely.
- ✓Understand how reports and dashboards help teams track business performance.
Study material
1. What is Salesforce?
Salesforce is a cloud-based Customer Relationship Management (CRM) platform. It helps businesses manage customer data, sales processes, service operations, marketing, and internal workflows in one system. Instead of storing customer details in scattered spreadsheets or systems, Salesforce gives a single place to capture, organize, and act on information.
Practical example
Example: A company stores lead information, customer contacts, support tickets, and sales opportunities in Salesforce. Sales reps can see where each customer stands in the sales pipeline without asking the marketing or support team repeatedly.
2. What is CRM?
CRM means Customer Relationship Management. It is a strategy and technology used to manage interactions with customers, prospects, and partners. A good CRM system captures every touchpoint, such as a sales call, an email, a service case, or a renewal conversation. This helps businesses understand what the customer needs and respond faster.
Practical example
Example: When a customer calls for support, the service agent can see their purchase history, open cases, and account details in Salesforce before answering the call.
3. Why Salesforce is popular
Salesforce is popular because it is cloud-based, highly customizable, and scalable. It supports many business areas, including sales, service, marketing, commerce, and analytics. It also has a large ecosystem of tools, apps, and integrations.
Practical example
Example: A company can use Salesforce Sales Cloud for sales tracking, Service Cloud for customer support, and Marketing Cloud for campaigns, all connected to the same customer data.
4. Core Salesforce concepts
Every Salesforce org contains several core building blocks. Understanding these is essential before learning Apex, LWC, or automation. The basic building blocks are objects, records, fields, relationships, and users.
Practical example
Example: An Account object stores company information, and each Account record is a separate company. A Contact record belongs to an Account and represents a person working there.
5. Objects in Salesforce
Objects are tables in Salesforce that store information. Standard objects are built into Salesforce, such as Account, Contact, Opportunity, Lead, and Case. Custom objects are created by admins or developers to meet business-specific needs.
Practical example
Example: Account = customer company; Contact = customer contact person; Opportunity = sales deal; Case = support issue; custom object like Project or Invoice if needed by the business.
6. Records and fields
A record is one row of data inside an object. A field is one column or attribute of that object. For example, in the Account object, Name, Billing City, Phone, and Industry are fields. Each account record has values in those fields.
Practical example
Example: Account record: Tata Motors, Billing City = Mumbai, Industry = Manufacturing, Phone = 9988776655.
7. Relationships between objects
Salesforce allows objects to be connected through relationships. This helps data stay organized and linked. Common relationship types are lookup and master-detail. These are important because they connect customers to contacts, deals, and related records.
Practical example
Example: A Contact is related to an Account because a person works for a company. An Opportunity is also related to that Account because a deal is created for that company.
8. Lookup relationships
A lookup relationship links two objects loosely. One object can point to another, but the child record can exist without the parent being deleted. It is used when objects are related but not tightly dependent on each other.
Practical example
Example: A custom object called Project can have a lookup to Account because a project may belong to a customer account, but it does not have to be deleted with the account.
9. Master-detail relationships
A master-detail relationship creates a stronger parent-child relationship. The child record cannot exist without the parent. This type is often used for configuration, roll-up summaries, sharing, and strict dependencies.
Practical example
Example: A custom object called Order Item may be a child of Order. If the Order is deleted, the Order Item should also be deleted.
10. Data model and schema
A Salesforce data model defines how objects, fields, and relationships work together. The schema is the blueprint of the system. A well-designed data model ensures data is clean, consistent, and easy to report on.
Practical example
Example: If a business tracks students, courses, and enrollments, the data model may include Student, Course, and Enrollment objects with relationships between them.
11. Standard vs custom objects
Standard objects already exist in Salesforce and are used for common business needs. Custom objects are created when the standard objects are not enough. Both can have fields, formulas, validation rules, and automation.
Practical example
Example: Standard object: Case. Custom object: Vehicle Service Request for a transport company that needs custom tracking beyond default objects.
12. Users, profiles, and roles
Salesforce is used by many users. Each user has access to data based on profile, role, permission sets, and sharing. A profile controls baseline access, while roles and sharing control visibility across the org.
Practical example
Example: A sales manager may see all opportunities in their region, while a sales rep sees only their own opportunities unless sharing is enabled.
13. Security model in Salesforce
Security is a major part of Salesforce. The platform allows you to control who can see, edit, create, and delete data. This is done through profiles, permission sets, sharing rules, role hierarchy, and object permissions.
Practical example
Example: A support agent might have access to Cases but not to financial data. A finance manager may have access to account billing fields but not to customer support records.
14. Profiles and permission sets
Profiles define the minimum access a user has. Permission sets grant additional access without changing the profile. This model helps organizations control permissions in a flexible way.
Practical example
Example: A sales rep profile may allow access to Leads and Opportunities, while a permission set adds access to advanced reporting features only for selected users.
15. Sharing and visibility
Salesforce uses sharing settings to decide which users can access records. Sharing can be controlled by role hierarchy, territory, public groups, and criteria-based rules. This matters because data privacy and business access are critical.
Practical example
Example: Managers may view records owned by their team through the role hierarchy, while restricted data can be shared only by public group rules.
16. Reports and dashboards
Reports and dashboards convert raw CRM data into useful business insights. Reports show tabular or summary views of data, while dashboards visualize key numbers in charts and widgets. This helps managers make decisions quickly.
Practical example
Example: A sales manager runs a report on closed deals this quarter and views a dashboard showing revenue by region, win rate, and sales growth.
17. Types of reports
Salesforce offers tabs, summary, matrix, and joined reports. Each report type helps answer different business questions. A tabular report is simple, while a summary or matrix report groups data based on categories.
Practical example
Example: A tabular report lists all open opportunities, while a summary report groups them by sales stage and region.
18. Dashboards
Dashboards are visual representations of metrics. They show key performance indicators (KPIs) using charts, gauges, and tables. Dashboards are used by managers, leaders, and team members to monitor goals and trends.
Practical example
Example: A dashboard may show pipeline value, number of closed deals, and open cases by priority for the executive team.
19. Why fundamentals matter
A strong understanding of Salesforce fundamentals is critical before deeper learning such as Apex, LWC, automation, or integration. If the data model or security model is weak, later business logic may break or create data issues. Basics are the foundation of everything in Salesforce.
Practical example
Example: If a custom object is incorrectly related to Account or fields are not mapped properly, a report may show wrong numbers, and a workflow may trigger on the wrong records.