You are here:
Considerations for Customizing Account Teams
If you customize account teams, review considerations related to custom fields, team member information, and validation rule, flow, and Apex trigger support.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Custom Fields and Picklists
- Custom fields and picklists aren't visible in Salesforce Classic.
- You can create up to 100 custom fields for an account team.
- When editing team members, users see custom fields, even if you don’t add the fields to the Add Account Team Members multiline page layout.
- If you delete a custom field, filters based on the custom field are also deleted. The results of assignment or escalation rules that rely on the custom field’s data can change.
- If you include a default value for a custom field, the field appears blank to Lightning Experience users while they’re adding account team members. If users don’t enter a value, the default value appears on the record after they save.
- Mass Reassign Account Teams doesn’t support custom picklists.
Team Member Information
- You can’t create a lookup from an object, such as an account, to an account team member.
- The Account Team related list is sorted by Team Member Name. The sort order can’t be customized, even if you specify the sort order in the Account Team Member page layout. A user can sort the related list by any other column, but when the page is refreshed, sorting reverts to the Team Member Name column.
- If you set the organization-wide default for contacts to Controlled by Parent, users can’t see or edit the Contact Access field.
- Only users with the Modify All Data profile permission can grant account team members higher access levels than the access levels of the account owner. In Lightning Experience, the running user’s permissions determine the available access level picklist values. In Salesforce Classic, an exception prevents users without the Modify All Data profile permission from saving higher access levels.
- When accounts are merged, account team members are deleted if they were added by a user who did not have sharing access on the account record.
- A deleted account team member record isn’t moved to the Recycle Bin. It can’t be recovered unless the record was cascade-deleted when deleting a related account. For more information, see AccountTeamMember in the Object Reference.
- Account team member records don’t support overriding the behavior of standard buttons—like Edit or Delete—with Visualforce pages.
Validation Rules, Flows, and Apex Trigger Support
- Validation rules, flows, and Apex triggers are applied when Lightning Experience users add their default team to an account using the Add action on the related list. However, they’re not applied when Lightning Experience users select the personal settings option to add their default team to accounts automatically.
- Validation rules and Apex triggers are bypassed when Salesforce Classic users add default account teams via any method.
- When an account team member is removed during an account ownership change, Apex triggers are bypassed.
Did this article solve your issue?
Let us know so we can improve!
