Lesson 5 of 22 · All lessons

Section 3 · Navigation · 20% of exam

3.1 Finding Information with Search, Lists, and Related Lists

3 min read Updated Nov 19, 2026

Exam objective

Explain how apps organize navigation and how users switch to the right work area.

  • When a search result is missing, check spelling, whether the record is indexed and searchable, the object scope, and the user’s access.

Official references: https://help.salesforce.com/s/articleView?id=search.search_overview.htm&language=en_US&type=5 https://trailhead.salesforce.com/content/learn/modules/cert-prep-salesforce-certified-associate/explore-navigation https://help.salesforce.com/s/articleView?id=xcloud.basics_organize_data.htm&language=en_US&type=5

Core concepts

A Salesforce app groups tools and objects around a role or business process. A sales app may place Accounts, Contacts, Leads, and Opportunities in its navigation. A service app may emphasize Cases, Contacts, and service workspaces. Apps help reduce the number of choices a user sees at once; they do not create a separate data silo. The same underlying Account can be available in several apps when permissions and navigation settings allow it.

The App Launcher provides a way to find and open Salesforce apps and supported connected items. In Lightning Experience, the navigation bar gives access to the objects, pages, and utilities configured for the current app. A user who cannot find an object should check the current app, its navigation items, and access. The object might not be included in that app even though the user has permission to it.

Example: A sales user needs to review a Case before calling a customer. If Cases are not on the current navigation bar, the user can use the App Launcher to open a service-oriented app or use search to locate the record, depending on the organization’s setup. The user should not assume that changing apps changes the record’s owner or access model. Apps shape the interface; permissions and sharing shape access.

Customization decisions belong in the correct setup surface. Administrators use Setup for organization configuration and Object Manager for objects and fields. App Manager configures apps and their navigation. Lightning App Builder configures pages and components. Users typically personalize supported settings from their profile menu or personal settings. A scenario that asks “where would an admin add a field?” points to Object Manager. “Where would an admin change app navigation?” points to app configuration.

Users may have different apps available because app visibility and assigned permissions vary. If an app is missing, gather the user’s role, assigned access, and exact navigation context before escalating. Adding every object to every app can make the interface noisy and can still fail to grant access. Good navigation design gives each user the work surfaces relevant to their responsibilities.

Hiding a tab or omitting an object from app navigation is not a substitute for removing permissions. A user may still reach data through another authorized path.

Separate app selection from data authorization. Ask “which interface organizes this work?” and “does the user have permission to this information?” as two distinct questions.

Extra concept

Extra concept: A utility bar can provide persistent productivity tools, such as notes or history, across pages in an app. Its availability depends on app configuration and user permissions.

Key takeaways

  • A Salesforce app groups tools and objects around a role or business process.
  • The App Launcher provides a way to find and open Salesforce apps and supported connected items.

Check your knowledge

Answer exam-style Navigation questions with answers and explanations.

Practice Navigation
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Foundations simulator: same number of questions, same time limit.

Get Complete Access