Now users with Partner Community and Customer Community Plus licenses can view the records of other external users within their account hierarchy. External account hierarchies take the complexity out of sharing data with external users.
Role Hierarchy can be set using “Number of partner roles” under Community Settings.
Note: Maximum Number of partner roles can be set to 3. Executive, Manager and Worker roles.
With External Account Hierarchy, this will change. Check the difference below
Without External Account Hierarchy:
Worker reports to Manager.
Manager reports to Executive.
Executive reports to Account Owner(Internal User) role.
With External Account Hierarchy:
EAH records are required.
Worker reports to Manager.
Manager reports to Executive.
Executive reports to
1. To account owner(internal user) role if the account doesn’t have parent account(EAH Record).
2. To Parent account’s(EAH Record) highest role(Executive if 3 roles are set in Community Settings, Manager if 2 and Worker if 1).
Manager reports to Executive.
Executive reports to
1. To account owner(internal user) role if the account doesn’t have parent account(EAH Record).
2. To Parent account’s(EAH Record) highest role(Executive if 3 roles are set in Community Settings, Manager if 2 and Worker if 1).
External Account Hierarchy Entity:
Entity to store the hierarchies. Fields are
a. Account
b. Parent – Parent EAH records(self reference to EAH entity)
c. IsActive
d. IsAccessible
e. Hierarchy Type – Partner or Customer
Entity to store the hierarchies. Fields are
a. Account
b. Parent – Parent EAH records(self reference to EAH entity)
c. IsActive
d. IsAccessible
e. Hierarchy Type – Partner or Customer
Note:
1. Account merge is blocked for accounts participating EAHs.
2. Person Account is not supported.
1. Account merge is blocked for accounts participating EAHs.
2. Person Account is not supported.
3. If IsActive is false, then re-parenting won’t happen. Nodes below the Inactive node will also don’t do the re-parenting.
4. An Account cannot actively participate in multiple active EAHs of same Hierarchy Type.
4. An Account cannot actively participate in multiple active EAHs of same Hierarchy Type.
IsAccessibleParent field in External Account Hierarchy
If false, it breaks the chain from current node to parent node. If Account A node is parent and B node is child and IsAccessibleParent is set to false in B node, then node A won’t get access to Account B.
Default is true.
If records are not visible to the users, check the below
1. Check whether all the nodes are active.
2. Check whether IsAccessibleParent is true.
3. Check Role Reparenting status.
4. Check whether the confirmation email is received.
1. Check whether all the nodes are active.
2. Check whether IsAccessibleParent is true.
3. Check Role Reparenting status.
4. Check whether the confirmation email is received.
Check the below link for more information
https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_networks_external_account_hierarchy_beta.htm
https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_networks_external_account_hierarchy_beta.htm
