Page layouts & record types
Once your objects and fields exist, you control how users experience them. A page layout defines which fields, related lists, and buttons appear on a record and in what order. You edit layouts with a drag-and-drop editor in Object Manager, dropping fields into sections and marking them required or read-only for that layout. Well-designed layouts group related fields together and hide the noise, which directly improves data quality because users are not overwhelmed.
A record type lets a single object support more than one business process. Suppose your Opportunity object serves both a "New Business" process and a "Renewal" process. With record types you can give each its own picklist values, its own page layout, and its own sales stages, all on the same object. Users pick the record type when they create a record, and Salesforce then shows the right layout and options.
The pieces fit together like this: a record type is assigned to profiles, each record type points to a page layout per profile, and each record type can restrict which picklist values are available. This combination is how you tailor one object to several teams without duplicating data.
A word of caution: record types add real complexity. Every new one multiplies the layouts and picklist configurations you maintain, so introduce them only when business processes genuinely diverge. Many orgs accumulate record types nobody remembers the reason for.
As an exercise, create two record types on Opportunity — "New Business" and "Renewal" — with different Stage picklist values, build a page layout for each, and assign them to your profile. Create an opportunity of each type and notice how the experience changes. Layouts and record types are the admin's main tools for shaping the user experience declaratively. With the data model in hand, the next section turns to automating the work that happens on top of it.
