To configure this feature: 

1. Ensure Configuring Account Plans is complete.
2. Grant users permission to the following objects:

   Object	Object Permission	Object Type	Fields	Field Permission
   account_team_member__v	CRED	n/a	role__v access__v team_member__v account_plan__v	Edit
   plan_tactic__v OR account_tactic__v OR action_item__v	CRED	n/a	share_with__v	Edit

3. Grant end users permission to objects in the account_plan_object_hierarchy__v Veeva Setting. (Optional)
4. Set the account_plan_sharing__v Veeva Setting to 1. https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Events/VirtualEvents/RecordingVirtualEvent.htm

   This feature does not support profile-specific Veeva Settings. The value of the Vault-level setting applies to all users regardless of any configured profile-specific settings.

5. Ensure there is a hierarchy defined in the account_plan_object_hierarchy__v Veeva Setting. For more information, see Configuring Account Plans.

   Custom objects are not supported at the second level of the hierarchy with this feature. The second level of the hierarchy, directly beneath the account plan, must be one of the following objects:

   • plan_tactic__v
   • account_tactic__v
   • action_item__v

   Custom objects can be used after the second level of the hierarchy. Sharing is only granted to custom objects when a Vault CRM object is updated. It is recommended to use only Vault CRM objects when using this feature.

6. Select Enable Custom Sharing Rules and Use action security to control sharing settings for all objects in the account_plan_object_hierarchy__v Veeva Setting, including Account Plan.

   The Account Team Member and Key Stakeholder objects are publicly shared with all users by default. If this is not changed, users who have visibility to an account plan can see all account team members and key stakeholders associated with the plan. This feature does not cover sharing account team member and key stakeholder records. Organizations can use matching or custom sharing rules to make those objects private.

7. Remove Execute permission on the Sharing Settings action for all objects in the account_plan_object_hierarchy__v on all permission sets where Create, Edit, or Delete permissions are given to end users.
8. Enable View permission on the Sharing Settings action for all objects with lifecycles if lifecycles have been enabled on account plan hierarchy objects.

9. Select the Enable Enhanced Sync check box on the VMOCs for all objects in the account_plan_object_hierarchy__v Veeva Setting. For information on enhanced sync, see Using Enhanced Sync.

If needed, add or update the values in the role__v picklist on the account_team_member__v object.

KAM users can add users to an account plan as an account team member and control their access via the access__v and role__v field on the Account Team Member object.

Team members have read or write access to the account plan and account plan data according to configured permissions, sharing rules, and object hierarchy. For data related to objects after the account plan in the hierarchy, sharing is based on the share_with__v value for a given record and the sharing settings are applied to hierarchy records downward from the record.

For example, consider the following hierarchy:

account plan -> plan tactic -> account tactic -> action item

In this hierarchy, the KAM populates the share_with__v field on a plan tactic record with Sales, which matches the role__v field on the end user's Account Team Member record. The end user now has access to the plan tactic shared with her role, as well as all account tactics related to the plan tactic, and all action items related to the account tactics. The user's ability to read and edit all of the records shared with her role is driven by the access__v field on her Account Team Member record.