Reference
The core standard fields on Account, Contact, Opportunity, Lead, and Case — the ones every Salesforce org ships with — each with its type and what it's actually for, in plain language.
Then the part no reference can give you: every field, standard and custom, in your own org.
Every Salesforce org starts with the same set of standard fields — they're built in, identical everywhere, and can't be deleted. This page is a plain-language reference for the core ones, so "what does Opportunity.ForecastCategoryName actually do" is a lookup, not a guess.
What makes your org yours is everything layered on top: the custom fields (the __c ones) three admins added over five years, the standard fields you repurposed, the ones nobody uses anymore. A generic reference can't describe those — because they only exist in your org.
So use the table below for the standard fields, and connect your org for the rest.
A representative cross-section of the standard fields on the five objects most orgs live in. Types are as you'd see them in Setup.
| Field | Type | Description |
|---|---|---|
| AccountAccount | ||
| Name | Text | The name of the account — the company or organization. |
| Type | Picklist | The kind of account, such as customer, partner, competitor, or prospect. |
| Industry | Picklist | The industry the account operates in. |
| AnnualRevenue | Currency | The account's estimated annual revenue. |
| NumberOfEmployees | Number | The number of employees at the account. |
| Website | URL | The account's website URL. |
| Phone | Phone | The account's primary phone number. |
| BillingAddress | Address (compound) | The account's billing address — a compound field over BillingStreet, BillingCity, BillingState, BillingPostalCode, and BillingCountry. |
| OwnerId | Lookup (User) | The user who owns the account. |
| ParentId | Lookup (Account) | The parent account in the account hierarchy. |
| Rating | Picklist | The account's prospect rating, typically Hot, Warm, or Cold. |
| AccountSource | Picklist | How the account record was originated. |
| ContactContact | ||
| Name | Name (compound) | The contact's full name — a compound over Salutation, FirstName, and LastName. |
| AccountId | Lookup (Account) | The account this contact belongs to. |
| The contact's email address. | ||
| Phone | Phone | The contact's primary phone number. |
| MobilePhone | Phone | The contact's mobile phone number. |
| Title | Text | The contact's job title. |
| Department | Text | The department the contact works in. |
| MailingAddress | Address (compound) | The contact's mailing address — a compound over the MailingStreet/City/State/PostalCode/Country fields. |
| ReportsToId | Lookup (Contact) | The contact this person reports to. |
| LeadSource | Picklist | How the contact was originated. |
| OwnerId | Lookup (User) | The user who owns the contact. |
| OpportunityOpportunity | ||
| Name | Text | The name or title of the opportunity (deal). |
| AccountId | Lookup (Account) | The account the opportunity is associated with. |
| Amount | Currency | The estimated total sale amount for the opportunity. |
| CloseDate | Date | The date the opportunity is expected to close, or did close. |
| StageName | Picklist | The current sales stage of the opportunity in the pipeline. |
| Probability | Percent | The likelihood (percent) the opportunity will be won — usually derived from the stage. |
| Type | Picklist | The type of opportunity, such as new business or existing business. |
| LeadSource | Picklist | The source that originated the opportunity. |
| ForecastCategoryName | Picklist | The forecast category the opportunity rolls up to (pipeline, best case, commit, closed). |
| NextStep | Text | The next action planned to move the opportunity forward. |
| IsClosed | Checkbox (read-only) | Whether the opportunity is closed (won or lost). System-maintained from the stage. |
| IsWon | Checkbox (read-only) | Whether the opportunity was won. System-maintained from the stage. |
| OwnerId | Lookup (User) | The user who owns the opportunity. |
| LeadLead | ||
| Name | Name (compound) | The lead's full name — a compound over Salutation, FirstName, and LastName. |
| Company | Text | The company the lead is associated with. |
| Status | Picklist | The lead's status in the qualification process. |
| LeadSource | Picklist | How the lead was originated. |
| The lead's email address. | ||
| Phone | Phone | The lead's phone number. |
| Title | Text | The lead's job title. |
| Industry | Picklist | The lead's industry. |
| Rating | Picklist | The lead's rating, typically Hot, Warm, or Cold. |
| IsConverted | Checkbox (read-only) | Whether the lead has been converted. Set by Salesforce during lead conversion. |
| ConvertedAccountId | Lookup (read-only) | The account created or matched when the lead was converted. |
| OwnerId | Lookup (User or Queue) | The owner of the lead — a user or a queue. |
| CaseCase | ||
| CaseNumber | Auto Number (read-only) | The unique, auto-generated case number. |
| Subject | Text | A short summary of the case. |
| Status | Picklist | The case's status in its lifecycle. |
| Priority | Picklist | The case's priority. |
| Origin | Picklist | The channel the case came in through — email, web, phone, and so on. |
| Type | Picklist | The type of case. |
| Reason | Picklist | The reason the case was created. |
| ContactId | Lookup (Contact) | The contact associated with the case. |
| AccountId | Lookup (Account) | The account associated with the case. |
| IsClosed | Checkbox (read-only) | Whether the case is closed. System-maintained from the status. |
| IsEscalated | Checkbox | Whether the case has been escalated. |
| OwnerId | Lookup (User or Queue) | The owner of the case — a user or a queue. |
These are standard fields, present in every org. Your org layers its own custom fields on top — connect it to see every one, described.
The table above is the standard fields. SchemaForce inventories your whole org — every object, every field, including the custom __c fields no reference could know about — and gives each one a plain-language purpose. Standard fields come pre-described from a curated library; your custom fields get an AI-written description you can review and, on Pro, push back to Salesforce.
A standard object can carry dozens of fields your org never populates. Turn on usage scanning and SchemaForce shows the population of each field — the share of records where it holds a value, counted in aggregate, never by reading a record — so you can tell a load-bearing field from a vestigial one.
SchemaForce maps field-level security across every profile, permission set, and permission-set group, so "who can read this field" is a lookup instead of an afternoon of clicking — which matters most for the standard fields that hold the sensitive data.
Standard fields are the fields Salesforce ships with every org — they are identical across all orgs and cannot be deleted. Some are common to most objects (Name, OwnerId, CreatedDate, LastModifiedDate); others are specific to an object, like Opportunity.Amount or Case.Priority. The custom fields your org adds (the ones ending in __c) are layered on top of these.
A standard field is built in by Salesforce and the same in every org; a custom field is one your org created, has an API name ending in __c, and is unique to your org. Standard fields generally cannot be deleted (and some are read-only or system-maintained), while custom fields are entirely under your control.
In Setup, open Object Manager, choose the object, and look at Fields & Relationships — that lists both standard and custom fields. To see every field across every object at once, with a plain-language description of each, SchemaForce inventories your whole org and lets you search it.
Standard fields can't be deleted. You can relabel many of them and hide them from page layouts, but the API name stays. Several standard fields are read-only or system-maintained (for example Opportunity.IsWon, Case.CaseNumber, Lead.IsConverted), so they can't be edited directly at all.
Connect SchemaForce and get a described map of every field — standard and custom — with usage and who can see what. Free for a single org. It reads your schema, never your records.