---
schema_version: "1"
id: bd3b29e4eee231a16a5f91ea3b8914bbd9a3f3a8d8b74f722c5855520f1fae29
title: Considerations for Using Account Teams
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/accountteam_def.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.accountteam_def.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f3f336e7772161bf55a17513f49a874a0854597dc80bd21f12c7858404ed1006
description: Review considerations for working with account teams. Learn about account team members and access levels and what happens to team members when an account owner changes.
products:
  - Sales Cloud
release: "264"
---
# Considerations for Using Account Teams

Review considerations for working with account teams. Learn about account team members and access levels and what happens to team members when an account owner changes.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience and Salesforce Classic</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

## Access to Accounts and Related Records

- These access methods determine users' access levels for accounts and related records.
    - Profiles
    - Org-wide Defaults (OWD)
    - Role Hierarchy
    - Sharing Rules
    - Manual Sharing
    - Account Team Member Record
- Your Salesforce admin sets org-wide default access to accounts and related records.
- Team member access must be equal to or less restrictive than the org-wide default. You can grant team members more access than the default, but not less.
- Only the account owner or someone higher than them in the direct role hierarchy chain can:
    - Grant team members more access than the org-wide default
    - Add team members who don't have Read or Read/Write access

## Access to Child Records and Fields

- You can't grant team members greater access to child records than you have yourself. For example, if you have Read access to child records on an account, you can’t give a team member Read/Write access. Ask your Salesforce admin to grant the needed access.
- The fields available when a user adds a team member are based on the user’s level of access to the account.

## When Account and Opportunity OWD Is Private

Accounts and opportunities have linked access levels.

- If you grant team members access to an opportunity, Salesforce gives Read access to the related account, even if the OWD is private.
- If you remove a team member’s access to an individual account, Salesforce removes them from all related opportunity teams.

## Viewing Account Access Levels

You can view account team member access levels from two different locations.

- The Team Member Access action on an Account record. This view shows the highest access level that the user has across all access methods.
- The individual account team member (ATM) record. This view shows only the access level assigned when the ATM record was created.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_core-264-0-0-production-enus/3c339c40-ca6c-49ba-9c6e-684be7a55f80/images/icon_example.png)

Example Shelly adds Marcus to her account team with Read Only on Opportunities. But a sharing rule also gives Marcus’s whole sales group Read/Write on Opportunities. The Team Member Access action shows Read/Write, the highest access Marcus has from any source. The ATM record shows Read Only, the access set on that record.

## Account Owner Changes

Sharing rules grant access to individuals or to groups (public groups, queues, roles). That distinction matters for team member retention during ownership changes. If a user with group-based access adds account team members, those team members are removed when the account owner changes, even if you’ve selected **Keep account team**.

To keep team members when ownership changes, one of these types of users must add the team members.

- A Salesforce admin
- A user with Modify All Data permission
- The account owner
- A user higher than the account owner in the owner’s direct role hierarchy chain (not a parallel branch)

## Portal Users

You can’t add high volume portal users to teams.

#### See Also

- [Working with Teams on Your Accounts](https://help.salesforce.com/s/articleView?id=sales.accountteam_add.htm&release=264.0.0&type=5 "If your Salesforce admin has enabled account teams, the Account Team related list appears on each account. You can add, edit, or remove team members.")
- [_Knowledge Article_: Difference Between Account Team Member Access and Team Member Access View in Salesforce](https://help.salesforce.com/s/articleView?id=002183041&type=1&language=en_US)