Account Plan Sharing

  • iPad
  • Browser

Administrators can now configure automatic sharing of Account Plans and related data to Account Team Members. This ensures the appropriate users have the correct visibility to their Account Plans.

For example, a KAM creates a new Account Plan and adds Sarah Jones as an Account Team Member with the role of Sales. When Sarah accesses her Account Plan Dashboard, the new account plan displays. She now has access to the plan and all the related data that is shared with his role so she can make decisions about the account.

Configuring Account Plan Sharing

To enable this feature: 

  1. Grant users Read and Create permission to the following objects: 
  • Account_Team_Member_vod
  • Account_Plan_vod
  1. Grant users edit permission to the following fields on the Account_Team_Member_vod object.
  • Role_vod
  • Access_vod
  • Account_Plan_vod
  • Team_Member_vod
  • Mobile_Id_vod (if creating records on iPad)

  1. Set the Account Plan Sharing Veeva Setting to 1.

    Account Plan Sharing does not support profile-specific Veeva Settings. The value of the org-level setting applies to all users regardless of any profile-specific settings.

  2. Add the following fields on the Account_Team_Member_vod object to the appropriate page layout:
    • Access_vod
    • Role_vod
    • Account_Plan_vod
    • Team_Member_vod
  3. Grant users edit permission to the Share_With_vod field on the object in the second layer of the Account Plan Object Hierarchy, and remove the field from all layouts except the second level of the hierarchy. This step is optional.

    When sharing is configured in this manner, the second level in the hierarchy (after Account Plan) must be an out-of-the-box object, for example, a Plan Tactic.

  4. Set the Organization-Wide Sharing Setting to Private on objects defined in the Account Plan Object Hierarchy.
  5. Deselect the Grant Access Using Hierarchies Sharing Setting on objects defined in the Account Plan Object Hierarchy. 

    Share Table entry types User, Role, and Territory are supported. Sharing by Public Group, Role, Subordinates, and Territory and Subordinates is not supported offline. This feature uses record-based sharing.

    The object hierarchy is related to the Account Plan Object Hierarchy setting at all times, which could be the original fixed hierarchy (Account Plan > Plan Tactic > Account Tactic > Call Objective) if that is what is used by the organization.

  6. Activate Enhanced Sync on the VMOCs of objects defined in the Account Plan Object Hierarchy.

    Ensure any Master-Detail relationships on all objects in the Account Plan Object Hierarchy are changed to lookups.

  7. Create an Apex Sharing Reason with the Reason Label and Reason Name set to Veeva_Account_Plan_Sharing_vod on objects defined in the Account Plan Object Hierarchy.

    This indicates a record is being shared by the Account Plan Sharing feature.

  8. Create a VMOC record according to the following table: 
Type Object Name Device
Top Level Share: Account Plan(Account_Plan_vod__Share)

iPad_vod
Top Level Share: Plan Tactic(Plan_Tactic_vod__Share) iPad_vod
Top Level Share: Account Tactic(Account_Tactic_vod__Share)

iPad_vod
Top Level Share: Call Objective(Call_Objective_vod__Share) or Action Item(Action_Item_vod__Share) iPad_vod

Using Account Plan Sharing

Key Account Managers can now add users to an Account Plan as an Account Team Member and control their access via the Access_vod and Role_vod 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. Data for objects after Account Plan in the hierarchy is shared based on the sharing settings for a given record, not the object, and the sharing settings are applied 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_vod field on a Plan Tactic record with "Sales" which matches the Role_vod field on Sarah Jones's Account Team Member record. Sarah Jones 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. Sarah's ability to read and edit all of the records shared with her role is driven by the Access_vod field on her Account Team Member record.