Standard Object
A Standard Object is a pre-built database table that comes included with every Salesforce org.
Definition
A Standard Object is a pre-built database table that comes included with every Salesforce org. Standard Objects like Account, Contact, Opportunity, Case, and Lead provide the foundational data model for CRM processes. They come with predefined fields, relationships, and behaviors, though administrators can customize them with additional fields and configurations.
In plain English
“Imagine this: You know how you have an address book or a contact list on your phone with all your friends' names and numbers? Standard Object in Salesforce is kind of like that, but for a whole company. It helps grown-ups at work keep track of all the important people and things they deal with every day, so nothing gets forgotten.”
Worked example
When a new Salesforce org is provisioned for Brightpath Consulting, it already contains Standard Objects like Account (for tracking client companies), Contact (for people at those companies), Opportunity (for deals), and Case (for support tickets). The admin customizes these by adding industry-specific fields but does not need to build the core data model from scratch.
Why Standard Objects are the platform's opinion about what a CRM is
Account, Contact, Opportunity, Lead, Case, User, Task, Event - Salesforce ships every org with a curated set of Standard Objects representing the universal concepts of a customer relationship management system. The schema, default fields, behaviors, and integrations have all been refined over decades and represent Salesforce's accumulated opinion about what CRM data should look like. Most of the platform's tooling assumes you'll use them.
The reason starting with Standard Objects pays off is the integration density that comes for free. Mailchimp knows about Lead. DocuSign knows about Opportunity. Marketing Cloud knows about Contact. Building parallel custom objects to express the same concepts is a common anti-pattern that produces an org which integrations can't easily talk to. Customize Standard Objects extensively (custom fields, validation rules, page layouts) before reaching for Custom Objects; reserve those for genuinely org-specific entities.
How to create Standard Object
Standard Objects are the Salesforce-provided objects every org ships with — Account, Contact, Lead, Opportunity, Case, Task, Event, etc. You don't "create" Standard Objects; you create records of them. The page covers what configuration you can do on a Standard Object — fields, layouts, validation rules, automation.
- Open Setup → Object Manager → pick a Standard Object
Object Manager lists all Standard + Custom Objects.
- Review the Schema sections
Fields & Relationships / Page Layouts / Lightning Record Pages / Validation Rules / Triggers / Buttons, Links, and Actions / Search Layouts.
- Add Custom Fields
Fields & Relationships → New → pick a field type. Most field types are available; some Standard Objects restrict certain types.
- Customize Page Layouts
Object Manager → object → Page Layouts → Edit. Drag fields, set required, set read-only.
- Add Validation Rules
Object Manager → object → Validation Rules → New.
- Configure Record Types
Object Manager → object → Record Types → New. Some standard objects (like Lead) heavily benefit from record types.
- Configure Automation
Flows / Triggers / Workflow Rules. All can target standard objects same as custom.
- Standard Objects can be customized but not deleted. Some standard fields can't be made read-only or hidden — check field documentation.
- Standard Object behavior is sometimes hardcoded by Salesforce. Adding logic via triggers / flows can fight against built-in behavior — test thoroughly.
- Renaming standard objects (Setup → Rename Tabs and Labels) only changes labels — the API name stays as Account, Contact, etc. Code references must use the API names.
How organizations use Standard Object
Build their entire data model on Standard Objects (Account, Contact, Opportunity, Lead, Case) and resist creating custom objects unless the standard one cannot represent the concept. The discipline keeps the org compatible with managed packages, AppExchange tools, and any third-party Salesforce integration that assumes standard schema.
Treat Standard Objects as a contract - any custom field added to Account is documented in the Account Field Catalog, and any new field needs a sponsor and a sunset trigger. The list of custom fields on Account stays smaller than 30 even after a decade of org evolution.
Use Standard Object events (CDC, Platform Events) to publish state changes to their event-bus integration layer. Because the publishers are Standard Objects, the integration uses a stable contract; the same code worked across three quarterly Salesforce releases without modification.
Trust & references
Straight from the source - Salesforce's reference material on Standard Object.
- Standard ObjectsSalesforce Developers
- Salesforce Object Reference ConceptsSalesforce Developers
Test your knowledge
Q1. What happens when Standard Object data is not maintained properly in Salesforce?
Q2. Which Salesforce Cloud is Standard Object most closely associated with?
Q3. What best describes the purpose of Standard Object in Salesforce?
Discussion
Loading discussion…