# Salesforce Opportunity Teams vs Account Teams: Who Sees the Deal and Who Gets the Credit

https://salesbond.app/blog/salesforce-opportunity-teams-vs-account-teams/
Published: 2026-10-16 · Updated: 2026-10-26

In Salesforce an opportunity team is a temporary group of people working one deal, while an account team covers the customer across deals. For a small sales team our rule is short: the owner plus a few named roles on the larger deals, and a weekly check that those roles are actually filled. The rest of this article is about when to add a team at all, which roles to keep, who may add people, and what the manager looks at on Monday morning.

## Opportunity team vs account team, side by side

The Trailhead unit on team selling draws the line in one sentence: an opportunity team is “a temporary group composed of people who help close a deal”, while account team members “can be expected to form a long-term relationship with a customer” ( [Trailhead: Sell as a Team and Split the Credit](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/sell-as-a-team-and-split-the-credit)). Everything else follows from that.

| | Opportunity team | Account team |
| --- | --- | --- |
| Lives on | One opportunity | One account |
| Lifetime | The deal. When it closes, the team has done its job | The relationship, across every deal with that customer |
| Who is on it | People helping close this deal: a second rep, a sales engineer, a partner | People who serve the customer long term: rep, support, a manager |
| Each member gets | A name, a role and a level of access to the opportunity | A role and separate access levels to the account, its opportunities and its cases |
| Default | A default opportunity team can be added to every new opportunity automatically | A default account team can be added to an opportunity in place of an opportunity team |
| Credit | Opportunity splits, entered on the opportunity | The Trailhead unit describes splits only on opportunities |

The opportunity rows and the last row come from the team selling unit; the account team access row is from [Trailhead’s unit on account and contact relationships](https://trailhead.salesforce.com/content/learn/modules/accounts_contacts_lightning_experience/understand-account-and-contact-relationships-lightning).

None of this shows up until your admin turns it on. For opportunity teams the admin enables team selling in Setup, and reps then get an Opportunity Team section on the opportunity where they enter each member’s name, role and access ( [Trailhead](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/sell-as-a-team-and-split-the-credit)). Account teams are a separate switch: in Setup the admin finds Account Teams, enables them, adds the Account Team related list to the account layout and fills in the Team Roles ( [Trailhead: Set Up Account Teams](https://trailhead.salesforce.com/content/learn/projects/protect-your-data-in-salesforce/set-up-account-teams)). The full click path for opportunity teams is in [Salesforce Help: Team Selling](https://help.salesforce.com/s/articleView?language=en_US&id=sales.teamselling.htm&type=5).

What does an account team change for the opportunities on that account? Access, mostly. Each account team member can get their own level of access to the account and separately to its opportunities and cases, so a support agent can see and edit the customer’s cases without anyone touching the owner field. The owner of each opportunity stays who it was. And if you want the account people listed on a particular deal, the team selling unit lets you add the default account team to that opportunity instead of building an opportunity team by hand.

The question that lands in our inbox is never “what is the difference” though. It’s “we have eight reps, do we need either of these”. Most of the time the honest answer is: not on most deals.

## When the owner and a note are enough

Picture a $30,000 deal, one rep, one buyer, a demo next Tuesday. A colleague joins the demo because she knows the industry. Does she need to be on an opportunity team?

No. She needs the rep to write one line in the opportunity: who she is, what she did, when. That is cheaper to create and cheaper to read, and nobody has to maintain it. A team member with a role and no activity is a small lie sitting on the deal. The manager who opens the record three months later will trust the lie before the notes.

We think of the opportunity team as a promise. Adding a person says: this person will keep working this deal, needs to see it, and may need to edit it. If none of that is true the promise is empty, and empty promises in a CRM pile up until nobody reads the team section at all. On a team of five to ten reps the owner field plus a disciplined next step covers most deals, and every name you add casually is a name somebody might argue about at quarter end. If the need is only that a group of colleagues can see the deal, [Salesforce sharing rules for opportunities](https://salesbond.app/blog/salesforce-sharing-rules-opportunities-small-sales-team/) may do it without an opportunity team.

## Three cases where a deal needs a team

On a small sales team we add an opportunity team in three situations and no others.

A sales engineer or solution consultant is on the deal for more than a single call. They will run a proof of concept, answer security questions, build the pricing sheet. They need to open the opportunity without asking, they need to see what the rep promised, and the manager needs to know later how much engineering time the deal consumed. A team row with the role “Sales Engineer” does all three. If your SE handoff is messy, the fix is upstream of the team; we described the handoff rules in [the sales engineer handoff article, written for Pipedrive](https://salesbond.app/blog/sales-engineer-handoff-pipedrive/), and they carry over to Salesforce as they are.

A partner or reseller is in the deal. You want their name on the record in case the deal is contested later.

A second rep is doing real work: a territory change mid-cycle, a senior rep brought in for the negotiation, a new hire shadowing a complex deal with the explicit plan of taking it over. This is the case that produces the quarter-end arguments. Create the team row the day the second rep joins, not after the signature.

![Two-column checklist: three yes/no questions decide whether a deal needs only an owner and a note or an opportunity team.](https://salesbond.app/wp-content/uploads/2026/10/salesforce-opportunity-teams-vs-account-teams-2.png)

Notice who is missing. The manager is not on the list: in most orgs the manager already sees the team’s deals through the role hierarchy, and a manager row only clutters the record (if your sharing is set up differently, check with your admin). The customer success person who takes the account after signature is not on the list either. That’s an account team question.

Each person on an opportunity team needs a Salesforce user, so check the [Salesforce license types for five people](https://salesbond.app/blog/salesforce-license-types-five-person-sales-team/) before you add anyone.

## Roles and access: keep it to three or four

Here is where small teams copy large ones and regret it. Each member carries a role and an access level ( [Trailhead](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/sell-as-a-team-and-split-the-credit)), and the roles come from a list your admin maintains in Setup. In the orgs we see, that list tends to grow well past what a ten-person sales team will ever use. A long list produces three things: reps pick the first value, two reps pick different values for the same job, and the manager’s report groups by a field nobody filled on purpose.

Our rule is three roles, four at most, and each one answers a question the manager will actually ask. “Sales Engineer” answers how much technical time the deal took. “Partner” answers whether the deal came through a channel. “Second Rep” answers who else will claim credit. If you sell with executive sponsors, add “Executive Sponsor” as the fourth and stop. Then ask your admin to trim the list to exactly those values, so the field can’t be filled wrongly.

Access is the second half. In our setups the second rep and the sales engineer get edit access, because they will log calls, attach documents and update the next step, and a partner gets read access unless there is a reason for more. Your reasons may differ. What matters is that you decide once per role and write it down so the person adding the member doesn’t have to think.

Who may add members is the part most teams never decide. Technically, who can add and remove team members depends on your org’s sharing settings and permissions, so ask your admin what yours allow before writing a policy. Our policy on top of that: the rep who owns the deal adds the team, because they know who is on it, and only the manager removes anyone, because removal is where the credit arguments start. A default opportunity team can be added to every new opportunity automatically ( [Trailhead](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/sell-as-a-team-and-split-the-credit)). Use it only for people who really are on every deal, which on a small team is usually nobody; a default team that drops the same three names onto every opportunity teaches everyone to ignore the section.

## What the manager checks on Monday

Two checks, five minutes. Both can be built as opportunity reports; ask your admin for a report type that includes opportunity team members if you don’t see one.

The first is deals above your threshold with no team at all. Pick the amount above which a deal on your team almost always involves a second person. For most teams we work with that is somewhere around the point where a sales engineer gets pulled in. Filter open opportunities above that amount where the team is empty. Each one is a question for the owner, not an accusation: is this really a one-person deal, or did you forget to add Anna? Most weeks the list is two or three deals and the answer is “forgot”. That’s fine. The point is that it gets fixed in week two of the the cycle and not in the week of the signature.

The second is team members with an empty role. A member without a role won’t show up in any grouping, and at quarter end it’s a name that will argue it did more than the record shows. Ask, fill, move on. If the role list has been trimmed to three or four values, this report is usually empty, which is the whole reason to trim it.

Both checks belong in the same Monday routine as the stage and next-step checks. If you already run a weekly pipeline report, add these two as filters rather than new reports. We laid out the whole set in [the weekly Salesforce reports a sales manager actually needs](https://salesbond.app/blog/salesforce-reports-sales-manager-weekly/), and the deeper version, for when something looks wrong, is the [opportunity audit for sales managers](https://salesbond.app/blog/salesforce-opportunity-audit-sales-manager/).

A disclosure, since we have reached the Monday list: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It reads deal data from Salesforce and the other CRMs we support and flags the opportunities that need attention, with the reason, so the manager starts Monday with the exceptions rather than the report builder. The two checks above are the kind of rule it is built for, and you can [check your CRM with SalesBond](https://salesbond.app/) if you would rather not maintain the filters yourself. The filters work on thier own, too. The hard part was never the report. It was deciding the three roles.

## Teams and the forecast: where teams stop and splits begin

An opportunity team does not move a single dollar of credit. A team member is a person who can see and work the deal; the owner still holds the whole amount in the forecast until somebody enters a split. Splits are a separate feature. The owner, or anyone above the owner in the role hierarchy, can add and adjust them; revenue splits can’t go above 100%, while overlay splits can ( [Trailhead](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/sell-as-a-team-and-split-the-credit)). Once the splits exist, each member’s credit rolls into forecasts and into quota and pipeline reports.

So the sequence on a shared deal goes like this. Team row first, on the day the second person joins. Split second, agreed with the manager while the deal is still open. After Closed Won, nothing changes without a note. We wrote up the split rules, the three split types and the quarter-end argument they prevent in [Salesforce opportunity splits: crediting a deal across reps without breaking the forecast](https://salesbond.app/blog/salesforce-opportunity-splits/). Read that one when the question is money. This one is about who is in the room.

## FAQ

**Can an opportunity team replace the owner?**
 No. The owner is one field on the opportunity, and the team sits beside it; team members don’t take the owner’s place in the forecast. If the deal has genuinely changed hands, change the owner, and record the handover as a split if the first rep should keep credit. The harder question is [who owns the account after Closed Won](https://salesbond.app/blog/account-executive-vs-account-manager/), which we answer in the account executive vs account manager comparison.

**Do opportunity teams affect reports?**
 Not by themselves. Adding a member changes who can see and edit the record and gives you names and roles to filter on. It does not change the amount, the stage or the forecast category. Credit in reports moves only when splits are entered, and those roll into forecast, quota and pipeline reports ( [Trailhead](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/sell-as-a-team-and-split-the-credit)).

**If I set up an account team, does it show up on every opportunity for that account?**
 The access does: account team members get whatever opportunity access you gave them on the account. Listing them on a specific deal is a separate step, where you add the default account team to that opportunity instead of an opportunity team ( [Trailhead](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/sell-as-a-team-and-split-the-credit)).

**Should a small team use account teams at all?**
 Usually later than you think. An account team pays off when several people serve one customer across many deals over years, which on a team of eight reps describes a handful of accounts. Start with opportunity teams on the deals that need them, and add account teams for the two or three customers where a renewal, an upsell and a support escalation run in parallel.