Account Team
An Account Team is a defined group of Users who collaborate on a single Account in Salesforce.
Definition
An Account Team is a defined group of Users who collaborate on a single Account in Salesforce. Each team member has a role (Account Manager, Executive Sponsor, Channel Sales Manager, Lifecycle Manager, Pre-Sales Engineer, Sales Manager, Sales Rep, or any custom role your org adds) and a set of access levels on the Account and the related Opportunities, Contacts, and Cases. Account Teams give selling organizations a way to model who actually works a deal beyond the single Account Owner field, and they give the platform a way to share visibility automatically rather than through manual sharing buttons.
The point of an Account Team is to stop the most common sharing-rule workaround in Salesforce. Without teams, granting visibility on an Account to anyone other than the Owner requires either expanding the Role Hierarchy, building Account-specific sharing rules, or hitting the manual Share button on every record. Each of those has costs. Role-Hierarchy changes affect every Account in the org. Sharing rules require criteria that you have to maintain. Manual sharing breaks the moment ownership changes. Account Teams sit in the middle: they grant access record-by-record but in a structured way that survives Owner transfers and is easy to report on. For enterprise sales orgs with named-account books, Account Teams plus a clear role taxonomy beats the alternative of dumping everyone into the manual sharing button.
How Account Teams actually work in production sales orgs
Access levels per role
Account Team Member access levels decide what the team can do with the Account and its children. Each team-member row carries four access levels: Account Access (Read Only or Read/Write), Contact Access, Opportunity Access, and Case Access. The default access levels can be configured per role in Setup, so a Pre-Sales Engineer might get Read Only on Account and Read/Write on Opportunity while an Executive Sponsor gets Read Only on all of them. The structure mirrors how real selling teams work: not every team member needs to edit every related record, but most need to see them. Configuring the default access per role once at setup time saves the team manual access tweaking on every deal forever.
Default Account Teams
Default Account Teams live on each User record. Setup > Users > select a user > Default Account Team > add team members. Once configured, the User's default team auto-applies whenever they create an Account or take ownership of one, so the team builds itself as the rep does normal work. The User can also pre-configure whether the default team applies to existing Accounts they own at the moment of Default-Team update, which is one of the few places in Salesforce where a setup change retroactively touches existing records. Default Account Teams are the single highest-impact Account Team configuration most orgs miss, because they live on the User record rather than the Account record and rarely make it into onboarding documentation.
Account Team vs Opportunity Team
Account Team is not the same thing as Opportunity Team, and confusing the two is one of the more common Salesforce admin mistakes. Account Team membership applies to a single Account record and its children. Opportunity Team membership applies to a single Opportunity. They share the same role taxonomy if you choose to align them, but membership is separate: adding a User to an Account Team does not add them to the Opportunity Team of every child Opportunity, and vice versa. Most large sales orgs configure both teams with overlapping membership and configure their forecast model to read off Opportunity Team for credit-split purposes. Account Team is the relationship layer; Opportunity Team is the deal-credit layer.
Team Member Roles
Team-member roles in Salesforce ship with seven defaults, and almost every org customizes them. The defaults (Account Manager, Channel Sales Manager, Executive Sponsor, Lifecycle Manager, Pre-Sales Engineer, Sales Manager, Sales Representative) are sensible starting points, but they rarely match how a specific sales organization actually describes its roles. Customizing the role picklist is fast (Setup > Account Teams > Team Roles) and the values feed into reports for "Deals with a Pre-Sales Engineer attached" or "Accounts without an Executive Sponsor" segmentation. Resist adding more than ten roles; every role you add is another dimension on the team-membership report and another value reps have to pick from at create time.
Member capacity limit
Account Team capacity caps out at five members per Account in the default configuration. Salesforce Support can raise the cap to twenty-five if your enterprise selling motion requires it, but the request requires justification and is not retroactive (existing Accounts at five members stay at five until somebody adds the sixth). Orgs that need more than twenty-five team members per Account are typically modeling the wrong layer; consider Public Groups, Role-Hierarchy adjustments, or Account-Hierarchy parent-child structures instead of stretching Account Team to model an entire sales region.
Mass assignment through the API
Mass-assigning Account Teams through the UI is slow and one-Account-at-a-time. The AccountTeamMember API object accepts bulk inserts through Data Loader, Workbench, or any Apex script with the right permissions. For territory realignments (the quarterly exercise where one rep's named accounts get reassigned to another rep), bulk team updates through the API are the only practical path. Build the team-realignment process into your territory-management workflow before you need it; building it during a Q4 territory shuffle is how teams end up with broken sharing across hundreds of accounts.
Reporting on Account Teams
Reporting on Account Teams uses a specific report type called Accounts with Account Teams. The default report type joins Account, AccountTeamMember, and User, which means a single Account with five team members shows up five times in the report. That denormalization is correct for "list all team memberships" reports but can mislead anyone running "count of Accounts with a Sales Manager attached." Use the COUNT_DISTINCT(Account.Id) function in the formula column when you need an actual Account count. Standard Account list views do not surface team-member columns; build a dedicated list view filter on AccountTeamMember if reps need to find their team accounts faster.
How to set up Account Teams
Setting up Account Teams in a new Salesforce org takes about thirty minutes. The cost of skipping it is paid every quarter forever, in the form of reps fighting the manual sharing button.
- Enable Account Teams
Setup > Feature Settings > Sales > Account Teams > enable. The setting is org-wide, applies to all Accounts, and cannot be easily reversed if Account Team membership data has been created.
- Customize Team Roles
Setup > Account Teams > Team Roles. Edit the default role picklist values to match what your sales org actually calls each role. Keep the count under ten and align with Opportunity Team Roles if you have them.
- Configure default access per role
Setup > Account Teams > Default Access. Decide which roles get Read Only versus Read/Write on Account, Contact, Opportunity, and Case. This is the single most-skipped step in Account Team setup and the source of "the team can edit deals they should not" support tickets.
- Set Default Account Teams on key Users
Setup > Users > select a User > Default Account Team > Add Team Members. Configure for sales managers and rep leads first; their default teams auto-apply on Account create and ownership change.
- Test the team on a sandbox Account
Create an Account, confirm the default team applies, check that the access levels match expectations, and verify the team shows up in Account list views and reports.
- Roll out to the broader sales org
With the default access dialed in and the team roles aligned, train sales managers on Default Account Team configuration. The rollout often takes the form of a one-pager and a thirty-minute office hour rather than a full training session.
Configure these in Setup before sales reps start populating teams. Default Read/Write on every object is the most permissive (and most-skipped) setup; tighten according to who should actually edit what.
- Default Team applies retroactively to existing Accounts only when the User checks the relevant box at Default Team update time. Without that checkbox, only new Accounts the User creates or takes ownership of get the team.
- Account Team caps at five members per Account by default. Salesforce Support can raise this to twenty-five but the request requires justification and existing Accounts do not auto-expand.
- Account Team is not the same as Opportunity Team. Adding a User to one does not add them to the other. Build both relationships explicitly if your sales motion needs them.
- Mass-assigning teams through the UI is slow. Use the AccountTeamMember API through Data Loader or Apex for territory realignments and bulk updates.
Trust & references
Cross-checked against the following references.
- Account TeamsSalesforce Help
- Set Up Account TeamsSalesforce Help
Straight from the source - Salesforce's reference material on Account Team.
- AccountTeamMember (Object Reference)Salesforce Developers
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 best describes the purpose of Account Team in Salesforce?
Q2. Who would typically configure or interact with Account Team?
Q3. Which Salesforce Cloud is Account Team most closely associated with?
Discussion
Loading discussion…