Parent Account
A Parent Account is the account record that sits directly above another account in a Salesforce account hierarchy.
Definition
A Parent Account is the account record that sits directly above another account in a Salesforce account hierarchy. The link is created by the Parent Account field, a self-lookup on the Account object that points one account at another account as its parent. Salesforce uses this single field to model corporate structures, where subsidiaries, divisions, or branch locations roll up to a parent company.
The relationship can stack many levels deep, so a regional office can have a country headquarters as its parent, which in turn has a global holding company above it. Each account still has its own contacts, opportunities, and cases. The Parent Account field simply records how the accounts connect, which the View Account Hierarchy action then renders as a tree.
How the Parent Account field shapes an account hierarchy
The self-lookup that makes hierarchies possible
The Parent Account field is a lookup that points from the Account object back to the Account object. That self-referencing design is what lets one account name another account as its parent without any custom configuration. You set it on the child record, not the parent, by editing the subsidiary account and choosing an existing account in the Parent Account field. You can type the parent name to match an existing record, or use the lookup icon to search for it, and the lookup dialog even lets you create a new parent account on the spot if one does not exist yet. Because the field lives on every account, the structure is flexible. Any account can be a parent, a child, or both at once when it sits in the middle of a chain. There is no separate hierarchy object to install and no junction record to maintain. The corporate tree you see in Salesforce is just the sum of all the Parent Account values across your account records, read from the bottom up.
Viewing the hierarchy and what it shows
Once parents are assigned, the View Account Hierarchy action on any account opens the tree view. In Lightning Experience the page displays up to 2,000 accounts, sorted by name, so you can see the parent at the top and child accounts nested beneath it. Salesforce Classic uses a different limit and shows up to 500 child accounts under a given account. The hierarchy view always reflects the Parent Account field, nothing more, so an account only appears in the tree if it has a parent set or has children pointing to it. To inspect a different branch, open the hierarchy from a different account, since the view is anchored on whichever record you started from. By default the columns match the Recently Viewed Accounts list view. Admins can customize which fields appear as columns, which is handy for surfacing owner, industry, or annual revenue right inside the tree. Customizing those columns adds an Org_Account_Hierarchy item to the Accounts list view menu, and deleting that item resets the columns back to the defaults.
Why sales teams build account hierarchies
Large customers rarely buy as a single legal entity. A retailer might purchase through dozens of store locations, each set up as its own account, while procurement decisions happen at corporate headquarters. Without a parent-child structure, every one of those accounts looks independent, and the true size of the relationship stays hidden. Setting the Parent Account field ties them together. A sales rep working one subsidiary can open the hierarchy and immediately see the rest of the corporate family, including which colleagues own the sibling accounts. Account executives use this to coordinate on enterprise deals so two reps are not pitching the same customer in isolation. It also supports cleaner territory and ownership decisions, because you can see whether a single account team should cover the whole tree. The hierarchy turns a scattered list of records into a map of one buying organization, which is the difference between reporting on a store and reporting on the chain that owns it.
Rolling up data across the tree
A common expectation is that revenue or open opportunities will automatically total up the hierarchy from children to the parent. The Parent Account field by itself does not do that. Roll-up summary fields, which can sum or count child records, only work across a master-detail relationship, and the account-to-account link is a lookup, not master-detail. So out of the box, a parent account does not show the combined pipeline of all its subsidiaries on a single field. Teams get rolled-up numbers in other ways. Reports can group opportunities or accounts by the parent account, giving a total for the corporate family without storing it on the record. Some orgs use Flow, Apex triggers, or scheduled jobs to walk the hierarchy and write summary values onto the parent. Others adopt AppExchange roll-up tools built for exactly this gap. The key point for an admin is to set expectations early. The hierarchy shows relationships and structure, but aggregated metrics on the parent require a deliberate reporting or automation approach.
Limits and behaviors to plan around
Several constraints matter when you design with parent accounts. Person accounts are not supported for the Parent Account field or the View Account Hierarchy action, so a business-to-consumer org built on person accounts cannot use this standard hierarchy for those records. You also cannot view account hierarchies in the Salesforce mobile app, which affects field sellers who work primarily on phones. Salesforce does not prevent you from creating a long, deep chain, but very large trees become hard to read and slower to load, and the 2,000 account display ceiling in Lightning means an enormous structure may not render in full. There is no native enforcement that a child can have only one parent in the broader sense, because the field is a single lookup, so each account points to exactly one parent at a time. If a customer needs many-to-many account relationships, such as partner or shareholder links rather than a strict org chart, the Account Hierarchy field alone is not the right tool, and a related-account model is a better fit.
When the standard hierarchy is not enough
The Parent Account field gives you one clean tree per account, which fits most ownership structures. Some businesses need richer relationships than a single parent can express. An account might be both a customer and a reseller of another account, or a holding company might have ownership stakes that do not map to a simple parent line. For these cases Salesforce offers the Account Relationship object, available in API version 45.0 and later, which represents a relationship of a given type between two accounts and supports many-to-many connections. Financial Services Cloud and other industry clouds extend this further with their own account-to-account relationship models and group structures. The practical guidance is to start with the built-in Parent Account field, because it is free, instant, and well understood. Reach for a custom or industry relationship model only when the org chart genuinely branches in ways a single parent cannot capture. Mixing the two thoughtfully, a clean parent tree for legal structure plus a relationship object for everything else, keeps reporting sane and the data model honest.
Set up a parent-child account hierarchy
You build an account hierarchy by setting the Parent Account field on the child records, then viewing the result with the View Account Hierarchy action. No package or special feature toggle is required, since the field exists on the standard Account object.
- Open the child account
Go to the account that should sit below another account, for example a branch or subsidiary. Click Edit, or edit the Parent Account field inline from the record page.
- Set the Parent Account field
Type the parent company name to match an existing account, or click the lookup icon to search. From the lookup you can also create a new parent account if the record does not exist yet. Save the record.
- View the hierarchy
From any account in the tree, open the action menu and choose View Account Hierarchy. The tree shows the parent at the top with child accounts nested beneath, anchored on the account you opened it from.
- Customize the columns (optional)
From the hierarchy view, add fields such as Owner, Industry, or Annual Revenue as columns so key data shows inside the tree. This adds an Org_Account_Hierarchy item to the Accounts list view menu.
The self-lookup on Account that names another account as the parent. Set it on the child, not the parent.
The standard action that renders the tree; it reads only from the Parent Account field.
The fields displayed in the tree, defaulting to the Recently Viewed Accounts list view until you customize them.
- Person accounts cannot use the Parent Account field or the View Account Hierarchy action.
- Account hierarchies are not viewable in the Salesforce mobile app.
- Lightning Experience shows up to 2,000 accounts in the tree; Salesforce Classic shows up to 500 child accounts.
- The field is a lookup, so roll-up summary fields cannot total child revenue onto the parent automatically.
Prefer this walkthrough as its own page? How to Parent Account in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Parent Account.
- Considerations for Using Account HierarchySalesforce
- AccountRelationship Object ReferenceSalesforce
Hands-on resources to go deeper on Parent Account.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does a Parent Account model in a Salesforce account hierarchy?
Q2. What reporting benefit does the Parent Account hierarchy provide for sales leadership?
Q3. How are subsidiaries arranged relative to a Parent Account in a multi-level hierarchy?
Discussion
Loading discussion…