Review tab role checks from territory membership
Key Takeaway
On the Activity Plan Review tab, each plan's role check reads only active territory membership. Active membership in the plan's own territory makes a user an Employee, and active membership in its direct parent territory makes them a Manager. Membership in both or in neither blocks the user.
The Activity Plan Review tab in Life Sciences Cloud decides, for each plan, whether the current user acts as an Employee (Sales Rep) or a Manager. The decision comes only from the user's active Enterprise Territory Management (ETM) membership, so the way you assign users to territories decides who can review each plan. The tab blocks a user who qualifies as both roles or as neither.
How the tab assigns a role
When a user opens the Activity Plan Review tab, the tab checks that user against each plan's territory. The check runs separately for each plan, so the result depends on each plan's territory and is not fixed once for the user.
Only active ETM membership counts toward the check. Active membership means a UserTerritory2Association record with IsActive = true, so an inactive association does not give a user the Employee or Manager role.
The territory check produces only two roles: Employee and Manager. The outcome for each plan depends on the user's active membership in two territories, the plan's own territory and its direct parent territory:
If the user is an active member of the plan's territory but not of its direct parent...
The user is an Employee (Sales Rep) for that plan.
If the plan's territory has a parent territory and the user is an active member of that direct parent but not of the plan's territory...
The user is a Manager for that plan.
If the user is an active member of both the plan's territory and its direct parent...
The tab intentionally blocks the user with the error "Employee is Manager on this territory".
If the user is an active member of neither the plan's territory nor its direct parent...
The tab blocks the user with the error "Neither Employee nor Manager".
The Manager check looks only at the direct parent territory. Membership in a territory higher up the hierarchy does not make a user a Manager for the plan. A user who is an active member only of a higher territory is an active member of neither territory the check reads, so the tab blocks them as neither Employee nor Manager. If the plan's territory has no parent territory, no user can qualify as Manager for that plan.
An org has three territories in a line: National at the top, Northeast Region below it, and Boston below that. Priya is an active member of Boston, Marco is an active member of Northeast Region, and Helen is an active member of National only. On a plan for Boston, Priya is an Employee because Boston is the plan's own territory. Marco is a Manager because Northeast Region is the direct parent of Boston. Helen sees "Neither Employee nor Manager" because National is two levels above Boston, not its direct parent. Now each of them opens a plan for Northeast Region. Marco is an Employee because Northeast Region is that plan's own territory. Helen is a Manager because National is the direct parent of Northeast Region. Priya is an active member of neither Northeast Region nor National, so the tab blocks her on that plan.