Record Type
A Record Type in Salesforce allows administrators to offer different business processes, picklist values, and page layouts for the same object based on user profile or context.
Definition
A Record Type in Salesforce allows administrators to offer different business processes, picklist values, and page layouts for the same object based on user profile or context. Record Types are commonly used when a single object serves multiple purposes, ensuring that each group of users sees only the fields and values relevant to them.
In plain English
“Here's a simple way to think about it: Record Types let one object serve many business processes. Same Account schema, different page layouts, different picklist values, different stages - without creating separate custom objects.”
Worked example
At GlobalTech, the Account object has two Record Types: "Customer" and "Partner." When a sales rep creates a Customer Account, they see fields for Annual Revenue, Industry, and Support Tier. When the partner team creates a Partner Account, they see fields for Partner Level, Certification Status, and Commission Rate. Each Record Type has its own page layout and picklist values.
Why Record Types let one object serve many business processes
Account is one object, but the Account record for an enterprise customer doesn't look like the Account record for an SMB or a partner - different fields matter, different stages apply, different teams own each. Record Type is the platform feature that lets a single object serve those distinct business processes simultaneously. Each Record Type can have its own picklist values, its own page layout, and its own set of valid stages, all without creating separate custom objects.
The reason this is worth knowing about even if you'd default to one object per process is governance. Five Record Types on Account is one schema to maintain; five custom objects (Enterprise_Account__c, SMB_Account__c, etc.) is five - with five times the integrations, five times the reports, and a giant join problem. Use Record Types when the underlying entity is the same but the business process differs; reserve custom objects for genuinely different things.
How to set up Record Type
Record Types are the platform's way to give one object multiple personalities — different page layouts, different picklist value sets, different business processes for the same Opportunity, Case, or Account. They're foundational once you have more than one team using the same object differently.
- Open Setup → Object Manager → [object] → Record Types
Object Manager → pick the object → Record Types in the left rail.
- Click New
Top-right of the record types list.
- Pick the Existing Record Type to clone from
First record type on a fresh object: clones from Master. After that, you usually clone from another type to inherit picklist value sets.
- Set Label, Record Type Name, and Description
Label is the user-facing pick ("Enterprise Deal"); Name is the API.
- Tick Active and assign to Profiles
Active = false hides it from the picker but keeps existing records valid. The grid below picks which Profiles can use it and which is each profile's Default.
- Save → configure picklist values
On Save, you'll be prompted to configure picklist values for each picklist on the object. This is where Record Types differ from each other most often.
- Assign Page Layouts
After saving, click Page Layout Assignment → assign the right layout per Profile × Record Type.
On = visible in the picker. Off = hidden but existing records keep their type.
Which profiles can see the record type, and which is each profile's default.
Per-record-type subset of the master picklist values.
Each Profile × Record Type combo gets a specific layout.
Some objects let Record Types reference different Business Processes for stage/status picklists.
- Picklist values are per-record-type. Adding a new value to the master picklist does NOT add it to the record types — you have to add it explicitly to each.
- If a user's profile has access to only one record type, the create flow skips the picker. If two or more, the picker appears — annoys users who expect one path.
- Deleting a record type fails if any record is using it. Convert / mass-update those records to a different type first, then delete.
How organizations use Record Type
Distinguished B2B and B2C Accounts via Record Types; same data shape, different operational patterns per type.
Different Opportunity Record Types for new business vs. renewal; stage progressions match each pattern.
Trust & references
Straight from the source - Salesforce's reference material on Record Type.
- Create Record TypesSalesforce Help
- Tailor Business Processes to Different Record Types UsersSalesforce Help
Test your knowledge
Q1. In which area of Salesforce would you typically find Record Type?
Q2. Can a Salesforce admin configure Record Type without writing code?
Q3. What is the primary benefit of Record Type for Salesforce administrators?
Discussion
Loading discussion…