Account
An Account in Salesforce represents a company, organization, or individual that you do business with.
Definition
An Account in Salesforce represents a company, organization, or individual that you do business with. It is one of the most fundamental standard objects and serves as the central hub for tracking all interactions, opportunities, cases, and relationships with your customers, partners, and competitors.
In plain English
“Here's a simple way to think about it: an Account is the gravitational center of every Salesforce org. The parent record Opportunities roll up to, the entity Cases reference, the company Contacts work for. Almost every other major object hangs off it.”
Worked example
Imagine your company sells software to businesses. You would create an Account record called "Acme Corporation" in Salesforce. Under this Account, you store all related Contacts (like the CEO and IT Manager), Opportunities (pending deals), Cases (support tickets), and Activities (calls and meetings). This gives your entire team a 360-degree view of the Acme relationship.
Why the Account is the gravitational center of every Salesforce org
Open any Salesforce org and the Account is everywhere. It's the parent record that Opportunities roll up to, the entity that Cases reference, the organization that Contacts work for, the company an Activity is tracked against. Even highly customized orgs almost always keep Accounts as the structural backbone - every other major object hangs off of it directly or indirectly.
The reason this gravitational role matters is that decisions about Accounts ripple through everything. Your Account hierarchy decides how forecast roll-ups behave; your Account ownership decides who sees what; your Account merge decisions can reshape years of history. Treat Account as the schema's load-bearing wall: change it deliberately, document the change, and validate the impact before anything bigger depends on the new structure.
How to create Account
Accounts are the company records that anchor most of the CRM graph — Contacts, Opportunities, Cases, and Activities all roll up to them. Creating one cleanly upfront saves hours of cleanup later.
- Open the Accounts tab
From the App Launcher (the 9-dot grid in the top-left), search for "Accounts" and open it. You can also navigate directly via the Sales or Service app navigation.
- Click New
The New button sits in the top-right of the list view. If you don't see it, your profile or permission set is missing Create on Account — ask your admin.
- Choose a record type if prompted
Orgs with multiple record types (e.g., Business Account vs. Person Account) show a record-type picker first. Pick the one that matches who you're tracking.
- Fill the Account Name
Account Name is the only platform-required field for Business Accounts. Use the legal entity name where possible — duplicates here cause reporting headaches downstream.
- Add context fields your org expects
Industry, Type, Website, Billing Address, Owner — none are platform-required, but most orgs require them via page layout, validation rules, or matching rules. Fill what's marked with a red bar.
- Save
Click Save (or Save & New to keep going). Duplicate-rule alerts fire here — confirm you're not creating a twin of an existing record before overriding.
Account Name. The only platform-required field on a Business Account. Person Accounts use LastName instead.
If your org has Person Accounts enabled and you pick that record type, LastName replaces Name as the required field. FirstName is optional.
- Person Accounts must be enabled by Salesforce Support and cannot be disabled once turned on — opt in only after a careful data-model review.
- Account Name is not unique by default. Most orgs add a duplicate rule or a validation rule on (Name + BillingCity) to stop near-duplicates at the door.
- Owner defaults to the creating user unless an assignment rule or default-owner setting fires. Re-check the Owner before saving for a teammate.
How organizations use Account
Account hierarchy carefully designed during initial setup; forecast roll-ups and territory rules work because the structure is right.
Account merge decisions made deliberately; preserving history matters for years of customer relationship data.
Trust & references
Straight from the source - Salesforce's reference material on Account.
- AccountsSalesforce Help
Hands-on resources to go deeper on Account.
Test your knowledge
Q1. What happens when Account data is not maintained properly in Salesforce?
Q2. Who would typically configure or interact with Account?
Q3. What best describes the purpose of Account in Salesforce?
Discussion
Loading discussion…