TECH **Salesforce Administrator: Custom Apps, Tabs, and Lightning Pages – Zero-Fluff Study Guide**

Salesforce Administrator: Custom Apps, Tabs, and Lightning Pages – Zero-Fluff Study Guide

1. What This Is & Why It Matters

You’re a Salesforce Admin, and your org is growing. Users complain that the default Sales app is cluttered, managers want a dedicated space for their team’s workflows, and executives need a simplified dashboard view. Custom Apps, Tabs, and Lightning Pages are your tools to solve this.

• Custom Apps = Containers for related tabs, branding, and navigation. Think of them like "workspaces" in Slack or "projects" in Jira—each app groups relevant tools for a specific team (e.g., "Service Console" for support agents, "Marketing Hub" for campaign managers).
• Tabs = The "buttons" in the navigation bar (e.g., Accounts, Reports, a custom object). You control which tabs appear in which apps.
• Lightning Pages = The actual UI layout (e.g., a record page with a highlights panel, related lists, and custom components). These are what users see when they click a tab.

Why this matters in production:
- User adoption plummets if people can’t find what they need. A well-organized app with the right tabs = happier users = less shadow IT (e.g., people exporting data to Excel because Salesforce feels "too messy").
- Security risks if you don’t restrict tabs/apps properly. Example: A sales rep shouldn’t see the "Compensation" tab in the HR app.
- Performance suffers if Lightning Pages are bloated with unnecessary components. A slow page = frustrated users = more support tickets.

Real-world scenario:
You inherit an org where the default "Sales" app is a dumping ground for 50+ tabs. Sales reps waste time scrolling, and new hires get overwhelmed. Your mission: Create a lean "Sales Pro" app with only the tabs they need (Accounts, Opportunities, Dashboards, a custom "Quick Actions" tab) and a Lightning Page optimized for mobile.

2. Core Concepts & Components

? Custom App

• Definition: A branded container that groups related tabs, sets navigation style (standard or console), and defines visibility (who can see it).
• Production insight: If you don’t assign apps to profiles, users won’t see them. Always test with a non-admin user!
• Key settings:
• App Type: Standard (traditional navigation) or Console (split-view for service agents).
• Branding: Logo, color scheme (hex codes), and description (users see this in the app launcher).
• Utility Items: Quick-access tools (e.g., Notes, History, Omni-Channel) that appear in the footer.

? Tab

• Definition: A clickable item in the navigation bar (standard objects like Accounts, custom objects, web tabs, Lightning Component tabs).
• Production insight: Tabs can be hidden (not visible in any app), default on (visible in all apps), or app-specific (only in certain apps). Misconfigure this, and users see irrelevant tabs.
• Types of tabs:
• Standard Object Tabs (e.g., Accounts, Contacts).
• Custom Object Tabs (e.g., "Projects").
• Web Tabs (embed external sites, e.g., a company intranet).
• Lightning Component Tabs (custom UI built with Aura/LWC).
• Visualforce Tabs (legacy, but still used in older orgs).

? Lightning Page (App Page, Home Page, Record Page)

• Definition: The UI layout users see when they click a tab. Three types:
• App Page: A standalone page (e.g., a custom dashboard).
• Home Page: The landing page when users log in.
• Record Page: The layout for a specific record (e.g., an Account page).
• Production insight: Overloading a record page with too many components (e.g., 10 related lists + 5 custom components) kills performance. Use Dynamic Forms to show/hide fields based on user role.
• Key components:
• Highlights Panel: Top section (e.g., key fields like Account Name, Industry).
• Tabs Component: Lets users switch between related lists, details, and custom components.
• Related Lists: Tables of child records (e.g., Contacts under an Account).
• Custom Components: Lightning Web Components (LWC) or Aura components.

? App Launcher

• Definition: The grid of apps users see when they click the "waffle" icon (☰) in the top-left.
• Production insight: If an app doesn’t appear here, users can’t access it. Check App Menu settings to order apps.

? Dynamic Forms (Beta → GA in Winter '23)

• Definition: A way to conditionally show/hide fields on a Lightning Record Page based on user profile, record type, or field values.
• Production insight: Replaces the need for multiple page layouts. Example: Show "Discount Approval" field only if the Opportunity Amount > $10K.

? AppExchange Apps

• Definition: Pre-built apps (e.g., DocuSign, Conga) that add tabs/components to your org.
• Production insight: Some AppExchange apps automatically add tabs to all apps. Audit these to avoid clutter.

3. Step-by-Step Hands-On: Build a "Sales Pro" App

Prerequisites

• System Admin access to a Sandbox (never test in Production!).
• A custom object (e.g., "Deals") to use as a tab.
• A Lightning Web Component (LWC) or Visualforce page (optional, for a custom tab).

Step 1: Create a Custom App

1. Navigate: Setup → App Manager → New Lightning App.
2. Fill in details:
3. App Name: Sales Pro
4. Description: Streamlined app for sales reps (Accounts, Opportunities, Deals, Dashboards)
5. Image: Upload a logo (e.g., sales-pro-logo.png).
6. Primary Color: #1B3A57 (dark blue).
7. App Type: Standard Navigation (not Console).
8. Click Next.
9. Select tabs:
10. Available Tabs: Accounts, Opportunities, Dashboards, Reports, Chatter, Deals (your custom object).
11. Move to Selected Tabs (order matters!).
12. Default Tab: Accounts.
13. Click Next.
14. Assign to profiles:
15. Select System Administrator and Standard User (or your sales profile).
16. Save.

Verify:
- Click the App Launcher (☰) → Search for "Sales Pro" → Open it.
- You should see the tabs you selected in the navigation bar.

Step 2: Create a Custom Tab for a Lightning Component

(Skip if you don’t have a component.)

1. Navigate: Setup → Tabs → New (under "Lightning Component Tabs").
2. Select a component:
3. Choose your LWC (e.g., quickActions).
4. Tab Label: Quick Actions
5. Tab Name: Quick_Actions
6. Tab Style: Pick an icon (e.g., "Lightning Bolt").
7. Save.
8. Add to "Sales Pro" app:
9. Go to App Manager → Edit Sales Pro → Add Quick Actions to Selected Tabs.

Verify:
- Open the "Sales Pro" app → You should see the new tab.

Step 3: Customize a Lightning Record Page (Account Page)

1. Navigate: Accounts tab → Open any Account record.
2. Click the gear icon (⚙️) → Edit Page.
3. Drag components:
4. Highlights Panel: Keep at the top.
5. Tabs Component: Add below highlights.
   • Tabs: Details, Related, Activity, Chatter.
6. Related Lists: Add "Contacts" and "Opportunities" under the Tabs component.
7. Add a custom component (optional):
8. Drag your LWC (e.g., accountHealthScore) to the right sidebar.
9. Activate:
10. Click Save → Activate → Assign as Org Default (or assign to specific profiles).
11. Add Dynamic Forms (optional):
12. Click the Details tab → Upgrade Now (if prompted).
13. Add a section: "Key Info".
14. Add fields: Account Name, Industry, Annual Revenue.
15. Set visibility: Show "Annual Revenue" only if Industry = "Technology".

Verify:
- Open an Account record → Check that the layout matches your design.

Step 4: Restrict App Visibility (Security)

1. Navigate: Setup → App Manager → Click the dropdown next to Sales Pro → Edit.
2. Assign to profiles:
3. Remove "Standard User" (if you only want admins to see it).
4. Add "Sales Rep" profile.
5. Save.

Verify:
- Log in as a Sales Rep → Check that "Sales Pro" appears in the App Launcher.
- Log in as a Marketing User → Confirm "Sales Pro" is not visible.

4. ? Production-Ready Best Practices

Security

• Least privilege: Only assign apps/tabs to profiles that need them. Example: HR shouldn’t see the "Sales Pro" app.
• Tab visibility: Use Tab Settings in Profiles to hide tabs (e.g., hide "Deals" tab for non-sales users).
• Lightning Page assignments: Don’t assign a page as Org Default if it’s only for one team. Use App Default or Profile Assignments.

Cost Optimization

• Avoid AppExchange bloat: Some apps add dozens of tabs. Audit installed packages (Setup → Installed Packages) and remove unused ones.
• Lightning Page performance: Fewer components = faster load times. Use Dynamic Forms to reduce clutter.

Reliability & Maintainability

• Naming conventions:
• Apps: [Team] [Purpose] (e.g., Sales Pro, Service Console).
• Tabs: [Object/Function] (e.g., Deals, Quick Actions).
• Documentation: Keep a spreadsheet of apps, tabs, and assigned profiles for audits.
• Sandbox testing: Always test app/tab changes in a Full Sandbox before deploying to Production.

Observability

• User feedback: Add a Chatter post or Survey tab to gather feedback on app usability.
• Usage metrics: Check Setup → Lightning Usage App to see which pages are slow or unused.

5. ⚠️ Common Mistakes & Traps

6. ? Exam/Certification Focus

Typical Question Patterns

1. "Which tool would you use to…?"
2. Example: "A sales manager wants a simplified view of Opportunities with only key fields. What do you use?"
   • Answer: Dynamic Forms (not multiple page layouts).

3. Example: "You need to embed an external website in Salesforce. What do you create?"

   
   
   • Answer: Web Tab.

4. "What’s the difference between…?"

5. App vs. Tab: An app is a container for tabs; a tab is a clickable item.
6. Standard vs. Console App: Standard = traditional navigation; Console = split-view for service agents.

7. Lightning Page vs. Page Layout: Lightning Page = UI layout (components); Page Layout = field-level control (but being replaced by Dynamic Forms).

8. Scenario-Based Questions

9. "A support agent needs a split-view layout with Cases on the left and Knowledge Articles on the right. What do you configure?"
   • Answer: Console App (not a Standard App).
10. "A custom object tab isn’t visible to users. What’s the most likely cause?"
    • Answer: The tab is hidden in the user’s profile settings.

⚠️ Trap Distinctions

• App Assignment vs. Tab Visibility:
• App Assignment = Who can see the app in the App Launcher.
• Tab Visibility = Who can see the tab within the app (controlled in Profiles).
• Lightning Page Assignments:
• Org Default = Everyone sees this page.
• App Default = Only users of this app see this page.
• Profile Assignment = Only users with this profile see this page.

7. ? Hands-On Challenge

Challenge:
Create a "Marketing Hub" app with: 1. A custom tab for a "Campaign Planner" Lightning Web Component (or a placeholder).
2. A Lightning Home Page with:
- A Dashboard component (e.g., "Marketing Performance").
- A List View of Campaigns.
3. Restrict the app to the "Marketing User" profile.

Solution:
1. Create the app:
- Setup → App Manager → New Lightning App → Name: Marketing Hub.
- Tabs: Campaigns, Dashboards, Reports, Chatter, Campaign Planner (custom tab).
- Assign to Marketing User profile.
2. Create the custom tab:
- Setup → Tabs → New (Lightning Component Tab) → Select your LWC (or create a dummy one).
3. Customize the Home Page:
- Click the Home tab → Edit Page → Add a Dashboard component and a List View component.
- Save → Activate → Assign as App Default for Marketing Hub.
4. Test:
- Log in as a Marketing User → Open Marketing Hub → Verify the Home Page loads correctly.

Why it works:
- The app groups marketing-specific tabs.
- The Home Page is tailored to marketing needs (dashboards + list views).
- Restricting to the Marketing User profile ensures only the right users see it.

8. ? Rapid-Reference Crib Sheet

9. ? Where to Go Next

1. Salesforce Help: Custom Apps
2. Trailhead: Lightning App Builder
3. Dynamic Forms Documentation
4. Salesforce Admins Blog: App Design Tips