Loading

Edit Access of Account Team Members Differs Between Lightning Experience and Salesforce Classic

Дата публикации: May 24, 2026
Описание

Issue: Account Team Member Access Options Differ Between Lightning and Classic

When editing an Account Team Member's access in Lightning Experience, users may notice that the available access options differ from those shown in Salesforce Classic. For example, in Classic a user may see the option to grant Read/Write access to an Account, while in Lightning they only see the option to grant Read Only access.
Consider the following example scenario:

  • An org's OWD for Account is set to Private.
  • The org has two roles: CEO and CTO.
  • The CTO role reports to the CEO role.
  • A user with the CTO role creates an Account record.
  • A user with the CEO role creates a child Contact for the Account.
  • The CEO clicks the New button within the Account Teams related list.
  • At this point, they are only presented with the option to grant Read Only access to the Account.

Similarly, users may see an option to grant greater access in Lightning than in Classic. If they try to add the Account Team Member with greater access, they receive the following error:

"insufficient access rights on cross-reference id"
Решение

Why Does This Happen?

This is a known gap in the Salesforce Lightning Experience user interface for Account Teams. The available access level options displayed when adding an Account Team Member in Lightning may not accurately reflect the actual sharing rules and role hierarchy of your org. This can result in either too few or too many access options being displayed.

Workaround

To select from the correct list of available access levels, add Account Team Members using Salesforce Classic, where the accurate access options are rendered based on your org's sharing model and role hierarchy.

Дополнительные ресурсы

Manage Your Account Teams

Номер статьи базы знаний

000384145

 
Загрузка
Salesforce Help | Article