Salesforce Platform Foundations Study Guide

8 sections 22 lessons ~49 min reading

Orientation to the Salesforce Certified Platform Foundations credential, current published exam logistics, official weighted outline, preparation resources, and conduct expectations.

1

Exam Overview

1 lesson · 3 min

0/1 done

Orientation to the Salesforce Certified Platform Foundations credential, current published exam logistics, official weighted outline, preparation resources, and conduct expectations.

  1. 1.1 Platform Foundations Complete Exam Overview 3 min
2

Data Model

15% of exam · 3 lessons · 7 min

0/3 done

Salesforce organizes information in objects, records, and fields. The main objects support different stages of customer work: Leads represent unqualified prospects, Accounts represent customers or businesses, Contacts represent people associated with Accounts, Opportunities track potential sales, and Cases track customer issues. When a Lead is qualified, Salesforce can convert it into an Account and Contact, and optionally create an Opportunity. Choose objects based on the information’s business purpose. Standard objects come with Salesforce; custom objects store organization-specific information. Record IDs uniquely identify records, while record names can change. Remember: Choosing an object does not determine who can see its records. Visibility is managed separately through permissions and sharing.

  1. 2.1 Objects, Records, and the Core CRM Objects 3 min
  2. 2.2 Relationships and Customer Lifecycles 3 min
  3. 2.3 Data Visibility and Data Integrity 1 min
3

Navigation

20% of exam · 3 lessons · 7 min

0/3 done

Teaches users to locate records and information, move among applications, understand user settings, and recognize where configuration belongs. Official blueprint mapping: Official mapping: Navigation (28%). The listed exam objectives cover locating/accessing information and identifying where customization takes place. Productivity and collaboration details in this requested chapter are supplemental study context, not an additional official weighted domain. Objective: Select global search, object list views, tabs, and related lists to locate records efficiently. ### Core concepts Global search is useful when a user knows a name, keyword, or identifier but is unsure which object or list contains the record. Search can return matches across supported objects and lets the user narrow the result set. A list view is better when the user wants a repeatable slice of one object, such as “My Open Opportunities” or “Cases Created This Month.” A related list is best when the user starts from a known parent record and needs its connected records. Example: A sales coordinator has a company name from an email. Global search can find the Account or matching Contact. If the coordinator needs all opportunities assigned to a team, an Opportunity list view with filters and columns is more efficient. If the coordinator has opened the Account and wants the open Cases for that customer, the Cases related list is the natural route. These tools complement each other; no single one is always best. When a search result is missing, check spelling, whether the record is indexed and searchable, the object scope, and the user’s access. Search does not bypass security. A user cannot use search to expose a record they are not authorized to view. Recently viewed items and pinned lists can speed common work but may create a false assumption that the list contains every matching record. Always consider the list’s filters and sort order. List views can be personal or shared based on permissions and configuration. Filters should be explicit. For example, “My Open Cases” depends on the record owner and status conditions; it is not equivalent to “All Open Cases.” Users can often select visible columns, sort, and use list view controls to take supported actions. For broader summaries or grouped totals, use reports rather than trying to turn a list into an analytics tool. Users should make navigation decisions based on the task: search for an unknown record, use a list for a defined working set, open a record’s related list for connected items, and use a report for aggregate questions. This distinction is a frequent scenario pattern because it tests whether the candidate understands the purpose of each feature. NOTE: Search results are governed by user access and product behavior; the absence of a result does not prove that the record does not exist. TIP: Identify the starting point and desired result. “I know the customer” points to the Account and its related lists; “show my work queue” points to a list view; “find this person anywhere” points to global search. ### Extra concept Extra concept: Favorites let a user bookmark frequently used records, lists, reports, and pages. Favorites improve retrieval but do not change record permissions. Key points:  Global search is useful when a user knows a name, keyword, or identifier but is unsure which object or list contains the record.  Example: A sales coordinator has a company name from an email.

  1. 3.1 Finding Information with Search, Lists, and Related Lists 3 min
  2. 3.2 Apps, Tabs, and the App Launcher 3 min
  3. 3.3 Setup, Object Manager, and Personal Settings 1 min
4

Productivity and Collaboration

4% of exam · 3 lessons · 7 min

0/3 done

Covers practical ways Salesforce users organize daily work and collaborate around customer records. These are useful platform concepts, but they are supplemental to the official Foundations outline unless tied to an explicit objective. Official blueprint mapping: Official mapping: Salesforce does not publish a separate Productivity and Collaboration weight for Platform Foundations. Use this chapter as applied context; do not treat it as a separately weighted exam domain. Objective: Use Salesforce activities to record follow-up work and meetings in the context of customer records. ### Core concepts Tasks and events are activities associated with people and business records. A task represents work to complete, often with a due date, owner, and status: call a prospect, send a proposal, or follow up on a Case. An event represents a scheduled appointment or meeting with a date and time. Activities help teams understand what has happened and what should happen next without relying on a private notebook or an isolated calendar entry. When a user creates an activity, they should relate it to the correct record and, where relevant, the correct person. A call task related to a Lead preserves the qualification history. A customer review meeting related to an Account and its Opportunity can support continuity when another teammate takes over. If the activity is not linked appropriately, it may be difficult to find from the record and may be omitted from team reporting. Scenario: An account executive completes a discovery call and agrees to send a technical outline by Friday. The user records the call as completed and creates a follow-up task with an owner and due date. A product demonstration next Tuesday is an event. The task captures a commitment; the event reserves time. The user should review the activity timeline before contacting the customer again so the team does not duplicate work. Activities improve handoffs, but they are not a substitute for structured sales or service records. A deal’s value and stage belong on an Opportunity; a support issue belongs on a Case. A task can remind the owner to update those records, while an event can document a meeting. Use notes for contextual detail, but keep critical status or classification in fields that can be reported and governed. Privacy and accuracy still matter. Activity descriptions can contain sensitive details, so record only information needed for business continuity and follow organizational policy. Ensure the activity owner is correct. A task assigned to the wrong person may not appear in the intended user’s work queue. When a record is private or shared selectively, related activity visibility may depend on system behavior and access configuration. NOTE: Activity features and page layout vary by edition and configuration. Follow the organization’s conventions for relating tasks and events. TIP: If a scenario asks how to make a follow-up visible to a team, choose a shared CRM activity linked to the relevant record rather than a personal reminder alone. ### Extra concept Extra concept: Activity timelines combine relevant past and upcoming activity into a chronological view. They help users prepare for the next interaction, but only when users consistently log meaningful activities. Key points:  Tasks and events are activities associated with people and business records.  When a user creates an activity, they should relate it to the correct record and, where relevant, the correct person.

  1. 4.1 Tasks, Events, and Activity History 3 min
  2. 4.2 Notes, Chatter, and Record-Centered Collaboration 3 min
  3. 4.3 Personal Productivity and Mobile Workflows 1 min
5

Reporting

15% of exam · 3 lessons · 5 min

0/3 done

Shows how reports answer structured questions about records and how dashboards communicate key measures visually. Official blueprint mapping: Official mapping: Reports & Dashboards (15%). Salesforce uses the phrase “Reports & Dashboards”; this chapter uses the requested shorter heading. Objective: Describe what reports do and select a report format and filters that answer a business question. ### Core concepts A Salesforce report is a view of records that meet defined criteria. It can display detail rows and can summarize information for analysis. Start report design with a question: “Which open opportunities are expected to close this quarter?” That question implies an Opportunity report, filters for status and close date, and useful columns such as account, owner, stage, amount, and close date. Adding unrelated columns makes the report harder to scan. Tabular reports show rows, similar to a list. Summary reports group rows and support subtotals. Matrix reports group by both rows and columns, such as pipeline by owner and quarter. Joined reports display multiple report blocks for related or distinct views, where supported. Choose the simplest format that answers the question. A tabular report is often sufficient for a detailed call list; a summary format suits grouped totals; a matrix format helps compare two dimensions. Filters define the report population. Standard filters may control date range or record status; field filters narrow to conditions such as Stage equals Proposal. Cross filters can include or exclude records based on related records, for example Accounts with open Opportunities, depending on available report types and configuration. A filter that is too broad can slow analysis and overwhelm the audience; one that is too narrow can hide important records. Scenario: A manager asks for the number and total value of open deals by owner and stage. Use an Opportunity report, filter out closed stages, group rows by owner and stage, and summarize Amount. Confirm whether the manager wants a current snapshot or a particular close-date period. If “open” has a local definition, use the organization’s stage/status conventions rather than guessing. Report types determine which objects and fields can be included. If a desired field is absent, the issue may be the selected report type, field access, or object relationship—not a broken report builder. A report returns only records the running user is permitted to see, subject to report configuration. Check filters, report type, user access, and date assumptions when a report seems incomplete. WARNING: A polished chart does not correct a flawed filter or inaccessible records. Validate the underlying rows and totals before sharing an important metric. TIP: Translate the question into object, population, grouping, measure, and time period before building the report. ### Extra concept Extra concept: A bucket field can group report values into user-defined categories for analysis without changing the underlying records. It is useful for exploration, but durable business classifications belong in governed data fields. Key points:  A Salesforce report is a view of records that meet defined criteria.  Tabular reports show rows, similar to a list.  Filters define the report population. Official references:

  1. 5.1 Report Purpose, Formats, and Filters 3 min
  2. 5.2 Dashboards, Components, and Data Context 2 min
  3. 5.3 Report Quality, Sharing, and Troubleshooting Coming soon
6

Salesforce Ecosystem

32% of exam · 3 lessons · 6 min

0/3 done

Introduces Salesforce as a platform and ecosystem, maps common business needs to product families, and identifies learning resources and career roles. Official blueprint mapping: Official mapping: Salesforce Ecosystem (32%), the largest published Platform Foundations domain. This section covers all four official objectives for the ecosystem. Objective: Describe how a connected CRM platform helps organizations connect departments, customer data, and business processes. ### Core concepts Organizations use Salesforce to manage customer relationships and coordinate work across departments. A shared CRM can connect sales activity, service interactions, marketing engagement, commerce, and other business processes around customer information. The value is not simply storing names in one place. It is making relevant information available to the teams that need it, supporting consistent processes, and measuring outcomes with reports and dashboards. Consider a company that sells equipment and provides maintenance. Sales tracks prospective customers and Opportunities. After a sale, service manages Cases and customer communications. Marketing can segment audiences and coordinate campaigns, subject to consent and data governance. A unified customer context helps a service agent understand what was purchased, while sales can see open issues before a renewal conversation. Access controls and data quality remain essential so that a connected platform does not become uncontrolled access to all data. Salesforce is a configurable platform. Organizations can use standard objects, add custom fields and objects, automate supported processes, and integrate with external systems. The right approach depends on business requirements, available product capabilities, data sensitivity, implementation effort, and ongoing ownership. Configuration should solve a clear need and align with the organization’s release and security practices. Use requirements gathering before selecting a feature. Ask who performs the work, what triggers it, what data is needed, who can access it, and how success will be measured. Then compare a standard capability with customization or integration. For example, a simple follow-up reminder may fit a task or automation; a complex external billing process may require an approved integration. A product name alone is not a solution architecture. Companies adopt Customer 360 products to support different functions, but exact packaging and availability can change. The exam asks candidates to identify suitable product offerings at a high level, not to memorize every SKU. Focus on the business domain: sales relationships and pipeline, customer service, marketing engagement, commerce, analytics, integration, or platform customization. Check current official product pages for current packaging and limits. NOTE: The phrase “single customer view” describes a goal, not a guarantee that data is automatically unified. Data models, integrations, identity matching, governance, and access design determine the actual result. TIP: In use-case questions, identify the department and outcome first, then match to the product family. Avoid selecting a product solely because its name contains a familiar word. ### Extra concept Extra concept: Salesforce’s multitenant architecture allows many organizations to use a shared infrastructure while isolating their data and configuration. Customers still remain responsible for their own access design, data quality, and user administration. Key points:  Organizations use Salesforce to manage customer relationships and coordinate work across departments.

  1. 6.1 How Organizations Use Salesforce and Customer 360 3 min
  2. 6.2 Customer 360 Product Families and Use-Case Matching 3 min
  3. 6.3 Learning Resources, Roles, and Career Paths Coming soon
7

Security and Access

7% of exam · 3 lessons · 7 min

0/3 done

Provides foundational context for protecting orgs, objects, fields, and records. These topics support the official visibility objective but are not an independent Platform Foundations weighted domain. Official blueprint mapping: Official mapping: No separate Security and Access percentage is published for Platform Foundations. The exam guide includes choosing a feature to ensure data visibility within Data Model (25%) and notes foundational security and sharing knowledge in its audience description. Objective: Distinguish login controls, object permissions, field permissions, and record-level sharing. ### Core concepts Salesforce access is layered. Authentication establishes who the user is and whether they can enter the org. Organization and session controls can impose additional login conditions. Object permissions determine whether the user can read, create, edit, or delete records of an object. Field-level security determines whether a field is visible or editable. Record-level sharing determines which particular records the user can access. A user must pass the relevant layers to perform an action. Use the least-privilege principle: provide the minimum access needed for a user’s job. Profiles establish a baseline of settings and permissions; permission sets and permission set groups can extend access for specific responsibilities. A role primarily supports record access through the hierarchy and is not a replacement for object permissions. Page layouts control record-page presentation, but field-level security is the security control for field access. Scenario: A support agent can open the Case object but cannot see one customer’s Case. Object permission exists, so investigate record-level sharing, ownership, hierarchy, teams, or sharing rules. If the agent can open the Case but cannot see the customer’s tax identifier field, check field-level security and whether the field is on the page. If the entire Case object is absent, check object permissions and app navigation separately. Administrative troubleshooting should reproduce the problem with a representative user and record. Avoid using an administrator’s broad access as proof that a configuration is correct. Check assigned profiles and permission sets, the object and field permissions, record ownership and sharing, and the app or page context. Change only the layer that addresses the actual gap. Security changes can have broad consequences. Granting “View All” or “Modify All” may bypass intended record sharing for an object. Broad profiles can create unnecessary privilege. Sensitive fields should have an owner and documented purpose. Review access when job responsibilities change and remove stale grants. Authentication controls, least privilege, and user education all contribute to protection. WARNING: A field hidden from a page layout is not necessarily protected from reports, APIs, or other interfaces. Use field-level security for field confidentiality. TIP: Diagnose from broad to narrow: can the user log in, access the object, see the field, and access this specific record? ### Extra concept Extra concept: Permission sets are additive. They grant access on top of the user’s baseline; they are not generally used to take away permissions already granted elsewhere. Key points:  Salesforce access is layered.  Use the least-privilege principle: provide the minimum access needed for a user’s job.  Scenario: A support agent can open the Case object but cannot see one customer’s Case.

  1. 7.1 The Layers of Salesforce Access 3 min
  2. 7.2 Record Sharing and Data Visibility 3 min
  3. 7.3 Security Scenarios and Safe Troubleshooting 1 min
8

User Setup

7% of exam · 3 lessons · 7 min

0/3 done

Explains the basic lifecycle of Salesforce user accounts and how user identity, profiles, permission assignments, and activation affect access. These topics provide foundational preparation context rather than a separate Platform Foundations exam weight. Official blueprint mapping: Official mapping: Salesforce does not publish a separate User Setup percentage for Platform Foundations. User administration is identified as foundational capability in the audience description; the official outline does not list a standalone User Setup domain. Objective: Describe what an org user account represents and the high-level steps for provisioning access. ### Core concepts A Salesforce user account represents an individual who can access an org under an assigned identity, license, and permissions. User administration is not simply creating a username. An administrator must confirm the person’s business need, select an available license that supports the required capabilities, assign a suitable profile and any needed permission sets, and ensure the user is active only when access should begin. Provisioning begins with a request. Verify the user’s name, email, role, team, manager, location, and required app or object access according to organizational policy. Select the right license based on the features the user needs and what the organization owns. A license places a ceiling on available capabilities; a profile and permission assignments determine access within that ceiling. Do not assign the most permissive license by default. Scenario: A new sales coordinator needs to work with Leads, Accounts, Contacts, and Opportunities and view a team dashboard. The administrator should verify the appropriate license and baseline profile, then add narrowly scoped permissions if needed. The dashboard folder must also be shared. Creating the user alone does not guarantee that the user can see the desired report or customer records. Activation status matters. An inactive user cannot log in, but records owned by that user may still need reassignment or other handling. Deactivating a user is generally preferable to deleting the identity when an employee leaves because historical records and audit context should remain. Follow organizational offboarding procedures to revoke sessions, transfer ownership, and review integrations or scheduled work tied to the user. Usernames must follow Salesforce requirements and be unique across Salesforce organizations. Email addresses and usernames serve different purposes. Users may have verified email addresses and organization-specific usernames. Follow current official guidance for identity changes, federation, and login policies; do not assume a username is the same as the person’s email address. WARNING: Provisioning the wrong license or broad profile can expose data or create avoidable costs. Confirm the role and least-privilege access before activation. TIP: Think of onboarding as identity + license + baseline permissions + additional access + app/folder visibility + verification. ### Extra concept Extra concept: A user record is also the owner of records, tasks, and scheduled work. Plan ownership reassignment as part of role changes and offboarding. Key points:  A Salesforce user account represents an individual who can access an org under an assigned identity, license, and permissions.

  1. 8.1 User Accounts, Licenses, and Activation 3 min
  2. 8.2 Profiles, Permission Sets, and Role Context 3 min
  3. 8.3 User Lifecycle, Preferences, and Access Reviews 1 min