Lesson 6 of 22 · All lessons

Section 3 · Navigation · 20% of exam

3.2 Apps, Tabs, and the App Launcher

3 min read Updated Nov 19, 2026

Exam objective

Identify where Salesforce configuration occurs and distinguish administrative setup from ordinary user preferences.

  • Example: A sales user needs to review a Case before calling a customer.

Official references: https://help.salesforce.com/s/articleView?id=platform.apps_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=platform.setup_overview.htm&language=en_US&type=5

Core concepts

Setup is the administrative area for configuring Salesforce. It includes a Quick Find search that helps administrators locate setup pages without navigating a long tree of menus. Object Manager centralizes configuration for objects, including fields, record types, page layouts, and supported business behavior. The exact items available depend on the object, edition, and permissions. For exam scenarios, understand the purpose of each surface rather than memorizing every menu label. Object Manager is used when the change belongs to an object’s structure or record experience: adding a custom field, adjusting a page layout, or reviewing object relationships. App configuration belongs to app management. Lightning pages and components are configured in Lightning App Builder. User access is managed through user and permission settings. The key exam distinction is the boundary between the page where a person works and the administrative environment where configuration is performed.

Personal settings are different. A user may adjust supported preferences such as language, time zone, email settings, or personal information from their profile menu and personal settings. An administrator may set defaults or policies, but user preferences do not alter the organization’s underlying data model. A request to change an individual’s display preference should not automatically trigger a global configuration change.

Scenario: A team asks to display a new “Renewal Health” field on Opportunity records. The administrator creates or locates the field in Object Manager, sets appropriate field access, and places it on the appropriate page layout or Lightning page. The field’s existence and its visibility are separate decisions. If the user asks for a new item in the sales app navigation, app configuration is involved instead. If the user wants a different time zone, personal settings may be the right route.

Always verify the requested outcome before choosing a tool. “Change the value on this record” is ordinary record editing. “Change the fields available on all records of this object” is configuration. “Change what this app displays” is app or page configuration. “Change what this user can access” is permissions and sharing. A wrong setup surface can produce a change that is technically valid but does not solve the stated problem.

Setup access is powerful. Only authorized administrators should make org-wide changes, and changes should be tested in a suitable environment when the organization’s release process requires it.

In a multiple-choice scenario, locate the scope: one user preference, one record, an object definition, a Lightning page, an app, or an access policy.

Extra concept

Extra concept: Setup Audit Trail can help authorized administrators review recent configuration changes. It supports governance and investigation but does not replace change documentation or testing.

Key takeaways

  • Setup is the administrative area for configuring Salesforce.

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