Why Only 'Private' Appears When Setting Opportunity or Case Access for a Salesforce Account Team Member

Root Cause: Role-Based Access Restriction

Salesforce Roles determine the access Users get to Cases and Opportunities, regardless of who owns those records. The access level is specified on the Role Edit page.

To check the Role setting: navigate to your User, click on the name of the Role, and select Edit.

The list of initial access level options when creating a new Account Team Member is determined by the User's Role setting:

• If the Role setting is restrictive (for example: "Users in this role cannot access opportunities that they do not own that are associated with accounts that they do own"), only Private appears.
• If the Role setting is less restrictive, additional options such as Read Only or Read/Write appear.
  
  

How to Fix: Edit the Role Settings

To make additional access levels available when adding Account Team Members, edit the Role and select a less restrictive Opportunity or Case access option. After updating the Role, the new access level options appear when adding Account Team Members.

Understanding Modify All Data and Its Impact

If you attempt to change the Opportunity access level to Read Only without adjusting the Role, you receive an Insufficient Privileges error.

The only way to bypass this error without changing the Role is for the User to have Modify All Data or Modify All Records for the object. Note that Modify All Records effectively gives the User full access similar to a System Administrator, overriding all Role restrictions and Organization Wide Defaults (OWDs).