What you need to do to switch record page templates
To change a Lightning record page template, you go into your Salesforce org's setup menu, find the object whose record page you want to change, and select a different template from the available options. The steps differ slightly depending on whether you're working with a standard object (like Account or Opportunity) or a custom object, but the core process is the same: navigate to Object Manager, open the page layout settings, and reassign the template.
The template you choose controls how fields, sections, and related information appear when someone opens a record. Switching templates doesn't delete your existing page layouts — it just changes which template Salesforce uses as the foundation for displaying that record type.
Key Takeaways
- You access record page templates through Setup > Object Manager, then select your object and go to Lightning Record Pages.
- Each record type can have its own template assigned, so you may need to change the template for specific record types rather than the whole object.
- Changing a template takes effect immediately for all users with access to that record, so test the change on a sandbox first if you're in production.
- The template you select must already exist in your org — you cannot create a new template from the assignment screen.
Steps to change the template in Setup
Open Setup by clicking the gear icon in the top right of your Salesforce home page, then select Setup. In the left sidebar, use the Quick Find box to search for "Object Manager" and click it. This opens a list of all objects in your org.
Find and click the object whose record page template you want to change — for example, Account, Contact, or a custom object. Once the object details page opens, look for the "Lightning Record Pages" section in the left sidebar menu. Click it to see all record pages and templates currently assigned to that object.
You'll see a list showing each record page, its template, and which record types use it. Click the record page name to open its details. At the top of the page, you'll see a dropdown or button labeled "Template" or "Change Template" — click it to see the available templates your org has built. Select the template you want to use, then click Save.
How record types affect which template you change
If your object uses record types, each record type can have its own page template assigned. This means you might need to change the template for one record type while leaving another unchanged. When you're in the Lightning Record Pages section, the list shows you which record types are tied to each page and template combination.
If you want the same template for all record types, you can often do this in one step by editing the master page layout. If you want different templates for different record types, you'll need to change them individually. Check the record type column in the list to see which record types are affected by each change you make.
Testing the change before it affects users
If you're working in a production org, create a sandbox copy first and test the template change there. Switch to your sandbox, follow the same steps to change the template, and verify that all the fields, sections, and related lists appear the way you want them to. Check how the page looks on both desktop and mobile, since some templates display differently on smaller screens.
Ask a few users from different roles to view a test record in the sandbox and confirm the layout works for their workflow. Once you're confident the change is correct, apply it to your production org using the same steps.
What happens to your existing page layouts after you change the template
Changing the template does not delete or modify your existing page layouts. The template is the base structure, and your page layouts sit on top of it. If you switch templates and then want to go back to the previous one, you can — your old page layout will still be there with all your customizations intact.
However, different templates may have different capabilities or field arrangements. When you switch to a new template, you may need to adjust your page layout again to match the new template's structure. Review your page layout after changing the template to make sure all required fields are visible and in the right order.
Common reasons to change a record page template
Teams often change templates when they need a different layout for a new workflow, want to add or remove sections that a different template supports, or need to accommodate mobile users better. Some templates are optimized for data entry, while others are better for viewing related records and activity. If your current template doesn't have a section type you need or displays information in a way that slows down your team, switching templates can solve that.
Another common reason is consolidating templates across your org. If you've been using multiple templates and want to standardize on one, you can change all your record pages to use the same template, then manage customizations through page layouts instead of maintaining separate templates.
Frequently Asked Questions
Can I create a new template from the template assignment screen?
No. You can only assign templates that already exist in your org. To create a new template, you need to go to Setup > Lightning App Builder, build the template there, and then return to Object Manager to assign it to your record pages.
Will changing the template affect records that are already open in user browsers?
No. Users who have a record open will see the old template until they refresh the page or navigate away and back to the record. The new template takes effect the next time someone opens that record type.
What if I change the template and users report missing fields?
The new template may not include all the fields your old template had. Open the page layout for that record page and add the missing fields back in. You can customize which fields appear on any template through the page layout editor.
Can different users see different templates for the same record?
No. The template assignment is at the object and record type level, so all users see the same template for a given record type. If you need different layouts for different users, use page layout assignments tied to profiles or permission sets instead of changing the template itself.
Do I need to change the template for each record type separately?
Only if you want different templates for different record types. If all your record types should use the same template, you can often change the master page layout once and it applies to all record types that don't have their own override.