Jeff began working in the Salesforce ecosystem in 2004, and he has helped a multifariousness of organizations transform their businesses.

I'll acknowledge information technology – before the Salesforce Wintertime '20 Release – Account Teams was not my favorite feature.  Information technology had as well many limitations, such as the inability to add custom fields for account squad members, or to apply automation such as Workflows, Procedure Architect, Validations, or Noon triggers.

But all this has changed.  Account Teams received a major upgrade—and "Account Team Member" is now a first-class object! Although this upgrade was highlighted in the Wintertime 'twenty Admin Maintenance Exam, some Admins may have missed it because this exam was waived due to Covid-19.

Salesforce Accounts Teams

What is an Account Team?

  • An Business relationship Team is simply a group of Users who work on an account together.

What makes Business relationship Teams special?

  • They let for Record-Level Admission Sharing, Reporting, and Process Automation.
  • Account Teams identify who is working on an account, past Team Roles, and the team members are displayed in Related Lists (on the Account Particular Folio).

Notes:

  • An Business relationship Squad cannot own an account
  • Business relationship Owners (or Admins) grant record-level access to account team members for the Account object, and Related Opportunities, Contacts, and/or Cases. (Read, Read/Write, or Private access; Not Create or Delete)
  • Account Team Members' record admission rolls up the role hierarchy (like standard sharing rules)
  • Account Team Members nevertheless need Object-level access to view/edit records
  • 'Account Team' is the Plural Label of the Object 'Business relationship Team Fellow member'

All-time Practices

When to utilise Account Teams

This is an optional feature, so determine if your Org has a demand before enabling.  Beneath are reasons to consider using Account Teams:

  • If multiple Users in your Org need access to select groups of accounts.
  • If your organization would like to written report on Accounts and their related Business relationship Team Members and Team Roles (and/or view the business relationship team members in a related list).
  • If your system is approaching your criteria-based sharing rules limits (50 on the Account object), or other sharing limits.
  • If Account Owners need to grant transmission "i-off" record admission to individuals (similar to manual sharing in Archetype). This tin exist done by using the [Add together Team Members].

Default Business relationship Teams

What is a 'Default' Account Team? A Default Business relationship Team is a predefined team that the Account Owner can gear up, which can then exist assigned to an Owner's accounts, when applicable.

Notes:

  • A User tin can simply have one default business relationship squad
  • Default Business relationship Team can be entered by each User (nether My Settings > Avant-garde User Details)
  • Using Default Account Teams is optional, and may not fit your Org'south use case

To add users to the Default Business relationship Team get to My Settings > Advanced User Details > Select [ADD] button

Implementation & Bulk Updates

Data Loader Option:

  • One of my favorite things most the Business relationship Teams upgrade is the ability to do the initial implementation and ongoing bulk changes to Account Team Members using Information Loader (both adding and removing members).
  • For Implementation: yous'll need the post-obit fields for the dataload: AccountID, UserID (of the Account Team Member), TeamMemberRole (picklist value), AccountAccessLevel (Read or Edit), ContactAccessLevel (None, Read, or Edit), OpportunityAccessLevel (None, Read, or Edit), and CaseAccessLevel (None, Read, or Edit).

Process Builder Option:

  • You could too automate Account Team Creation with the Process Builder, for case, whenever in that location is a New Account (or an Account meets some criteria).

Final Tips

    • Each Org only gets ane 'Team Role' picklist, so cull the labels wisely.
    • Account Teams work in combination with Sharing Rules and Org-Broad Defaults (OWD) and other sharing. They can only add access, not reduce access.
    • You lot can use Process Builder/Flows to populate custom fields on the Account Squad Member object from the User Record (such equally Electronic mail, Telephone).
    • Y'all could add custom fields for "Start Engagement" and "Stop Date" for the Account Team Member object for reporting.
    • Keep in mind that each Account Team Member has a Unique Id (for each divide business relationship).  These IDs can exist used for bulk updates.
    • Account Teams could exist rolled-out for a portion of the Org, if desired, as Account Teams are only displayed on Folio Layouts with the "Business relationship Team" related list added.
    • You can Add together "Custom Buttons" to the Business relationship Team related list (such every bit an [Account Hierarchy] button).
    • The Account Team Fellow member object is also bachelor for Workflows. Meet below.