If you’ve ever opened a Salesforce record and wondered why certain fields appear in a certain order — or why your colleague sees different buttons than you do on the same record — the answer is page layouts in Salesforce.
Page layouts are one of the most essential, everyday tools in a Salesforce Administrator’s toolkit. They shape how your users interact with data, and when designed well, they can dramatically improve user adoption, data quality, and team productivity. Get them wrong, and your users end up drowning in irrelevant fields, hunting for the information they actually need.
This guide covers everything you need to know — from the fundamentals to advanced techniques — so you can configure page layouts in Salesforce with confidence.
Page layouts in Salesforce are configuration templates that control what information users see — and how it is organized — when they view or edit a record. Specifically, they determine:
- Which fields appear on the record detail and edit pages
- How fields are organized into sections
- Which fields are required, read-only, or editable
- Which buttons and actions are available at the top of the record
- Which related lists appear at the bottom of the record
- Which custom links and Visualforce pages are embedded
- What users see in the Salesforce Mobile App
Every standard and custom Salesforce object (Accounts, Contacts, Opportunities, Leads, Cases, and any object you create) has at least one page layout by default. Administrators can create multiple page layouts per object and assign different layouts to different user profiles or record types — meaning a sales rep, a support agent, and a manager can all open the same Account record and see a view that’s perfectly tailored to their role.
The core idea: Page layouts in Salesforce give administrators declarative, point-and-click control over the user interface for every record in the system — no code required.
Why Page Layouts Matter?
Page layouts might seem like a cosmetic detail, but they have a direct, measurable impact on how well your Salesforce implementation actually works in practice.
They Drive User Adoption
The number one reason Salesforce implementations struggle is poor user adoption. When users open a record and are greeted by a cluttered wall of 80 fields, most of which are irrelevant to them, they disengage. A clean, purposeful page layout — with only the fields that matter to that role — makes Salesforce feel intuitive rather than burdensome.
They Enforce Data Quality
By marking key fields as Required on a page layout, you ensure users fill in the information your business depends on before they can save a record. This is one of the simplest and most effective tools for improving data completeness.
They Support Role-Based Workflows
Different teams need different information. A Sales Development Rep qualifying a lead doesn’t need the same view as a Finance Manager reviewing a closed-won opportunity. Page layouts let you tailor the experience to each role, so every team sees exactly what they need — and nothing they don’t.
They Directly Affect ROI
Well-designed page layouts reduce the time it takes to enter and find data. Multiply that time saving across dozens or hundreds of users over a year, and the return on a thoughtful layout design is significant. How you design a page layout in Salesforce can make or break user adoption — and good design leads to greater ROI.
The Page Layout Editor: A Walkthrough
Salesforce uses the Enhanced Page Layout Editor (sometimes called the drag-and-drop editor) to build and modify page layouts. Here’s a quick orientation before diving into how to use it.
Accessing the Editor
Setup → Object Manager → [Select an Object] → Page Layouts → [Select or Create a Layout]
The Two Main Areas
The Palette (Top Section) The palette sits at the top of the editor and contains every element you can add to your layout, organized into tabs:
- Fields — all available fields for this object
- Buttons — standard and custom buttons
- Custom Links — links you’ve defined on the object
- Related Lists — related objects that can be displayed
- Mobile & Lightning Actions — quick actions for Lightning Experience and the mobile app
- Visualforce Pages — embedded Visualforce components (if applicable)
The Canvas (Bottom Section) The canvas is where you build the layout. You drag elements from the palette and drop them onto the canvas to add them. The canvas reflects exactly how the record page will look for users assigned to this layout.
Quick Save and Layout Switcher
Two features that speed up your work when managing multiple layouts:
- Quick Save — saves your changes without leaving the editor
- Layout Switcher — a dropdown in the editor header that lets you jump between page layouts for the same object without going back to the list
Preview As
The Preview As button lets you preview how the layout will look for a specific user profile. Always use this before finalizing a new layout to catch any display issues.
Key Components of a Salesforce Page Layout
Understanding the building blocks of a page layout is essential before you start creating and customizing them. Here’s a breakdown of every component you can work with.
Fields
Fields are the heart of any page layout. You control:
- Which fields appear — drag them from the palette onto the canvas, or drag them off to remove them
- Where they appear — left column, right column, or full-width
- Field Properties — click the wrench icon on any field to set:
- Required — the user must fill in this field before saving the record
- Read-Only — the field is visible but cannot be edited through this layout
Important: Field-level security (FLS) and page layout settings work together but independently. If a field is hidden via FLS for a user’s profile, it will not appear on the layout even if you’ve added it. FLS always takes precedence over the layout. Never rely on page layouts alone to restrict access to sensitive data — use FLS and profiles for true security.
Sections
Sections let you group related fields under a labeled heading, making the page easier to scan and navigate. When creating or editing a section, you can:
- Set the section label (visible to users, or hidden if you prefer)
- Choose 1-column or 2-column layout
- Set the tab-key order (left-to-right or top-to-bottom)
- Enable collapsible sections — users can expand or collapse them to keep the page tidy
Good section naming — “Contact Information,” “Deal Details,” “Billing Address” — dramatically improves how quickly users can find what they’re looking for.
Buttons and Quick Actions
The buttons at the top of a record page are controlled here. You can:
- Control which standard buttons appear (Edit, Delete, Clone, Follow, etc.)
- Add custom buttons that link to external pages, trigger Visualforce, or call a custom action
- Add and order Quick Actions — these are the action buttons that appear in the Lightning Experience action bar (e.g., Log a Call, New Task, Send Email)
- Configure Salesforce Mobile and Lightning Experience Actions — the actions available when using the Salesforce app
Related Lists
Related lists appear at the bottom of a record and display records from associated objects. For example, an Account might show related lists for Contacts, Opportunities, Cases, Activities, and Attachments.
For each related list, you can:
- Choose which related lists appear and in what order
- Customize the columns displayed in each list
- Add or remove buttons from the related list toolbar
Getting related list columns right is important. A Contacts related list that shows Name, Title, Phone, and Email is far more useful than one that only shows Name.
Custom Links
Custom links can point to internal Salesforce URLs, external websites, or custom Visualforce pages. They appear on the record detail page and give users quick access to related resources — for example, a link to open the company’s LinkedIn profile or a link to a custom reporting page.
Visualforce Pages
If your org uses Visualforce, you can embed Visualforce pages directly within a section on the page layout. You control the height of the embedded frame and whether scroll bars are displayed. This enables custom UI experiences — dashboards, maps, calculators — right inside a standard record page.
Mobile Cards (Salesforce Mobile App)
The Salesforce Mobile and Lightning Experience Actions section of the page layout editor controls which actions appear in the Salesforce mobile app. Additionally, Compact Layouts (a separate but related feature) control the field highlights that appear in the record header card when browsing records in mobile.
How to Create a Page Layout in Salesforce (Step-by-Step)
Creating a page layout in Salesforce is a purely declarative process — no code, no developer required. Here’s the full walkthrough.
Step 1: Go to Setup
Click the gear icon ⚙️ in the upper-right corner of Salesforce and select Setup.
Step 2: Open Object Manager
In the Quick Find search box, type Object Manager and select it. Then click on the object you want to create a layout for — for example, Opportunity or Contact.
Step 3: Navigate to Page Layouts
In the left-hand sidebar of the Object Manager, click Page Layouts. You’ll see a list of all existing layouts for this object.
Step 4: Create New or Clone Existing
- Click New to start a fresh layout from scratch
- Click Clone (next to an existing layout) to start from a copy of an existing layout
Pro Tip: Cloning is almost always faster. If your new layout is similar to an existing one, clone it and modify — rather than building from zero. You’ll preserve the sections and structure, and just need to add, remove, or adjust specific fields.
Step 5: Name Your Layout
Give the layout a clear, descriptive name that will make sense months from now. Good examples:
- “Opportunity Layout – Enterprise Sales”
- “Contact Layout – Support Team”
- “Lead Layout – Marketing”
Avoid generic names like “New Layout 2” — these create confusion as your org grows.
Step 6: Build the Layout in the Editor
The Enhanced Page Layout Editor opens. Now you can:
- Add Sections — click the Sections element in the palette and drag it to the canvas, then name it
- Add Fields — drag fields from the palette into your sections; position them in the left or right column
- Set Field Properties — click the wrench 🔧 icon on a field to mark it Required or Read-Only
- Configure Buttons — scroll to the buttons section and drag buttons on or off
- Set Up Related Lists — click the Related Lists tab in the palette, add the lists you need, and configure their columns
- Add Mobile Actions — in the “Salesforce Mobile and Lightning Experience Actions” section, arrange the actions for mobile and Lightning users
Step 7: Save
Click Save. Your layout is saved but not yet visible to users — it needs to be assigned to one or more profiles first.
How to Assign Page Layouts to Profiles and Record Types
A page layout only affects users once it’s been assigned to their profile (and optionally to a specific record type). Here’s how to do it.
Method 1: Page Layout Assignment (Recommended)
- From the Page Layouts list for your object, click the Page Layout Assignment button at the top right
- Click Edit Assignment
- A grid appears with profiles as rows and record types as columns (if you have record types enabled)
- Click a cell or select multiple cells to highlight them, then choose a page layout from the dropdown at the top
- Click Save
This view is extremely powerful — you can see exactly which layout every profile sees for every record type, all on one screen.
Method 2: Assign via the Profile Page
- Go to Setup → Profiles → [Select a Profile]
- Scroll down to the Page Layout Assignments section
- Click Edit and change the layout assigned to any object
Understanding the Profile + Record Type Matrix
When record types are involved, each combination of profile + record type can have a different page layout. For example:
| Profile | Master Record Type | Enterprise Record Type | SMB Record Type |
|---|---|---|---|
| Sales Rep | Sales Layout – Default | Sales Layout – Enterprise | Sales Layout – SMB |
| Sales Manager | Manager Layout | Manager Layout – Enterprise | Manager Layout – SMB |
| Support Agent | Support Layout | Support Layout | Support Layout |
Key Insight: One page layout can be assigned to multiple profiles. You don’t need a separate layout for every profile — only create new layouts when the content genuinely needs to differ. Over-creating layouts leads to a maintenance nightmare over time.
Page Layouts vs. Dynamic Forms: What's the Difference?
Dynamic Forms is one of the most important modern developments in Salesforce record page customization, and every admin working in Lightning Experience should understand how it relates to traditional page layouts.
What Traditional Page Layouts Do
With a traditional page layout, every user assigned to that layout sees the exact same set of fields — all the time. There is no way to say “only show this field when the Status is Active” or “hide this section for users in the West region” using the page layout editor alone. Field visibility at the layout level is static.
What Dynamic Forms Add
Dynamic Forms, managed via the Lightning App Builder, let you place individual fields and sections directly on the record page as components — and apply visibility rules to each one. A visibility rule can be based on:
- The value of another field (“Show Discount Reason only when Discount % > 10%”)
- The user’s profile or permission set
- The device being used (desktop vs. mobile)
- Custom logic combining multiple conditions
This means fields appear and disappear in real time as users interact with a record, reducing clutter and guiding users through the right process dynamically.
What Page Layouts Still Control — Even With Dynamic Forms
Even when you migrate to Dynamic Forms, the traditional page layout is not fully replaced. It still controls:
- Related Lists — which related lists appear, their columns, and buttons
- Standard and Custom Buttons — the action bar at the top of the record
- Custom Links — links embedded on the detail page
- Mobile Layouts — the classic Record Detail mobile component
Summary: Dynamic Forms give you field-level conditional visibility and a cleaner Lightning-native experience. Traditional page layouts remain essential for related lists, buttons, and links. The two work together.
How to Migrate to Dynamic Forms
- Open a record page → click the gear icon → Edit Page
- In the Lightning App Builder, click the Record Detail component
- In the properties pane, click Upgrade Now to launch the Dynamic Forms migration wizard
- Select your existing page layout as the source — Salesforce will convert all fields and sections into individual components
- Click Finish → configure visibility rules as needed → Save and Activate
Page Layouts vs. Lightning Record Pages
This is a common source of confusion for admins newer to Lightning Experience.
| Feature | Page Layouts | Lightning Record Pages |
|---|---|---|
| Managed In | Object Manager → Page Layouts | Setup → Lightning App Builder |
| Controls | Fields, sections, buttons, related lists, links | Overall page structure, components, tabs, sidebars |
| Field Visibility | Static (all users on the layout see same fields) | Dynamic (with Dynamic Forms — conditional visibility) |
| Assigned To | Profiles (and record types) | Apps, record types, and profiles |
| Works In | Classic and Lightning Experience | Lightning Experience only |
Think of it this way: the Lightning Record Page is the outer container that defines the structure and layout of tabs, sidebars, and components. The Page Layout (or Dynamic Forms components) controls the actual fields and data inside the record detail section of that container.
Page Layouts vs. Record Types: When to Use Which?
Record Types and Page Layouts are two different tools that are often used together, but serve different purposes.
| Page Layouts | Record Types | |
|---|---|---|
| What it does | Controls the UI — which fields, buttons, and lists appear | Controls the data model — which picklist values and business process apply |
| Best for | Showing the right information to the right people | Supporting different business processes on the same object |
| Example | Support Agents see a different view of a Contact than Sales Reps | Enterprise Opportunities follow a different sales stage process than SMB Opportunities |
| Assigned via | Profile (directly or through record type) | Profile |
Use Record Types when:
- You have different types of records that follow different sales or service processes
- You need different picklist values for different groups of users
- You want to present a completely different page layout per business scenario
Use Page Layouts (without Record Types) when:
- The business process is the same but different roles just need to see different fields
- You want to simplify the user experience without creating multiple record types
A common and powerful pattern: use Record Types to define the business process, and use Page Layout Assignments on those record types to deliver the right UI to each profile.
Page Layout Best Practices
Following proven best practices is the difference between a page layout that users love and one they tolerate.
1. Less Is More — Ruthlessly Remove Unnecessary Fields
Every field on a page layout that a user doesn’t regularly need is noise. Cluttered layouts are one of the top reasons users avoid entering data in Salesforce. When in doubt, take it out. You can always add fields back if users ask for them.
2. Front-Load the Most Important Fields
Keep the most used fields near the top of the layout. Users scroll minimally — critical fields buried at the bottom often get skipped entirely.
3. Group Related Fields into Clearly Named Sections
Use sections (with visible headers) to logically organize fields. A well-sectioned layout helps users navigate quickly. Examples: “Key Dates,” “Financial Details,” “Shipping Address,” “Internal Notes.”
4. Make Sections Collapsible
Enable collapsible sections so users can collapse parts of the layout they don’t need for a given workflow. This keeps the page manageable without removing fields that are occasionally needed.
5. Be Deliberate About Required Fields
Only mark a field as Required at the layout level when it is genuinely essential every single time a user creates or edits a record. Over-using required fields frustrates users and can prevent legitimate data entry — for example, blocking a quick update because a non-critical field hasn’t been filled in.
6. Maintain Consistent Field Positions Across Objects
Where similar fields exist across multiple objects (like Owner, Created Date, or Status), place them in the same general area on each layout. Consistency builds user intuition and speeds up navigation across the platform.
7. Customize Your Related List Columns
The default related list column configuration is rarely optimal. Customize the columns shown in each related list to surface the information users actually need. A Contacts related list that shows Name, Title, Phone, and Email is infinitely more useful than one showing Name and Created Date.
8. Use the "Preview As" Feature Before Assigning
Before assigning a new or updated layout, use Preview As to see the layout from the perspective of the profile you’re assigning it to. What looks right to you as an admin may not look right to a user.
9. Use Field-Level Security for Real Security Restrictions
Page layouts control visibility on the record page UI. They are not a security mechanism. If a field must truly be hidden from a user for security or compliance reasons, restrict it via Field-Level Security (FLS) on the profile — not by leaving it off the layout. Anyone can still see layout-excluded field values through reports, list views, or the API unless FLS restricts them.
10. Audit and Clean Up Layouts Regularly
As your org evolves, page layouts accumulate stale fields, outdated sections, and unused layouts. Schedule a quarterly or annual audit to review layouts for relevance, remove unused layouts, and ensure assignments still reflect the current team structure.
Common Page Layout Mistakes to Avoid
Even experienced admins fall into these traps. Watch out for them:
Relying on Page Layouts for Security As mentioned above, removing a field from a page layout does not restrict access to that data. Use profiles and permission sets with FLS for true data security.
Creating Too Many Similar Layouts It’s tempting to create a new layout for every minor variation. This leads to a sprawling, unmanageable collection of layouts that are hard to maintain. Look for opportunities to consolidate — one well-designed layout can often serve multiple profiles.
Making Too Many Fields Required Required fields create friction. The more fields you mark as required, the more obstacles you put between your user and saving a record. Reserve the Required property for fields that are absolutely essential.
Ignoring Mobile If your users access Salesforce on mobile devices, test your page layouts on mobile. Configure the Salesforce Mobile and Lightning Experience Actions section to include the most relevant actions for mobile users.
Not Testing Before Assigning Always test a new or modified layout before assigning it to active users. Log in as a test user (or use the Preview As feature) to confirm the layout looks and behaves as intended.
Using Page Layouts as the Only Customization Tool Page layouts are powerful, but they work best as part of a broader customization strategy that includes Dynamic Forms for conditional visibility, Compact Layouts for the highlights panel, and the Lightning App Builder for overall page structure.
Frequently Asked Questions
Q: Can one page layout be assigned to multiple profiles? Yes. A single page layout can be assigned to as many profiles as you like. Only create separate layouts when the content genuinely needs to differ between user groups.
Q: What is the difference between making a field required on the page layout versus universally required? Setting Required on a page layout means users on that specific layout must fill in the field before saving. A universally required field (marked as required at the object field level) is required for all users, regardless of which layout they’re on — including API and import operations.
Q: Does removing a field from a page layout hide it from the user completely? No. It removes the field from the record detail and edit pages for that layout. However, the user may still see the field value in list views, reports, related lists on other objects, or via the API — unless you also restrict it through Field-Level Security.
Q: How many page layouts can I have per object? There is no hard-coded limit, but Salesforce recommends keeping the number manageable (generally no more than 200) to avoid administrative overhead and confusion.
Q: Do page layouts work in both Salesforce Classic and Lightning Experience? The page layout editor manages content for both Classic and Lightning Experience. In Lightning Experience, the page layout works alongside the Lightning App Builder (which controls the broader page structure) and Dynamic Forms (which controls individual field visibility). In Classic, the page layout controls everything on the record page.
Q: Can I clone a page layout to use as a starting point for a new one? Yes, and this is the recommended approach. When creating a new layout, choose to clone an existing one rather than starting from scratch. This preserves the section structure and field organization, so you only need to make targeted changes.
Q: What happens to a page layout if I delete a field? If you delete a field from the object, it is automatically removed from all page layouts, related lists, and reports that referenced it. Salesforce handles this cleanup automatically.
Q: Can I have different page layouts for desktop and mobile? Not directly through the page layout editor — the same page layout applies to both. For mobile-specific customization, use the Salesforce Mobile and Lightning Experience Actions section in the page layout to configure relevant actions, and use Compact Layouts to control the fields shown in the mobile record highlight card.
Take Your Salesforce Skills Further
Understanding page layouts in Salesforce is a critical skill — but it’s just one chapter in the story of becoming a certified Salesforce Administrator.
A fully qualified Salesforce Admin is expected to know user management, security and access, the automation engine (Flows, Approval Processes), reports and dashboards, data management tools, the sales and service cloud feature set, and much more. It’s a broad, highly valued skill set — and the Salesforce Certified Administrator credential is one of the most respected certifications in the CRM industry.
Ready to Become a Certified Salesforce Admin?
If you want a structured, step-by-step path to passing the Salesforce Admin Certification Exam — with expert instruction, hands-on exercises, and everything you need to go from beginner to certified — the MyTutorialRack Salesforce Admin Certification Course has you covered.
Here’s what you’ll master:
- Salesforce Setup & Configuration
- User Management, Profiles & Permission Sets
- Object Manager, Fields, Page Layouts & Record Types
- Sales Cloud & Service Cloud Features
- Automation: Flows, Approval Processes & Workflow Rules
- Reports, Dashboards & Analytics
- Data Management, Imports & Data Quality
- Security Model: OWDs, Roles, Sharing Rules & FLS
- AppExchange & Platform Fundamentals
- Full Exam Preparation with Practice Questions
Whether you’re a complete beginner looking to launch a career in the Salesforce ecosystem, or a working professional who wants a globally recognized credential to validate your skills and increase your earning potential — this course is designed for you.
Don’t just learn about page layouts — learn to build, govern, and optimize an entire Salesforce org from the ground up.
