Product message alignment and exclusion by territory
Key Takeaway
To keep a product message away from specific lowest-level territories, deselect the message on those territories in "Product Alignment". The parent territory and its other child territories keep the message. The product itself stays available, because deselecting removes only that message.
Product messages are the key points that field users share with healthcare providers, such as a drug's safety, efficacy, dosage limits, or side effects. In Life Sciences Cloud, an admin assigns these messages to the territories that are already aligned with the product. The admin can also remove a message from specific territories, so field users can quickly deliver the right key messages in their territory.
Product-territory alignment comes first
Message alignment builds on product-territory alignment. You assign product messages to the territories that are aligned with a product, so the product-territory alignment comes first.
Product-territory alignment is resolved in three ways: explicit (direct) alignment, inheritance from a parent territory, and explicit exclusion. Users in a territory see only the products that are not excluded.
| Product alignment type | Meaning |
|---|---|
| Inclusion | The territory is directly aligned, even if its parent is not. |
| Inclusion (Inherited) | The territory is aligned through its parent. |
| Territory and Subordinates Inclusion | The territory and its child territories are aligned. |
| Territory Exclusion | The territory is excluded even though its parent is aligned. |
A territory that is not aligned gets no Product Territory Availability record.
By default, product-territory alignments are inherited downstream, from a parent territory to its child territories. The "Parent Territory Product Alignment" admin setting works in the opposite direction. The setting extends product alignments upward to all parent territories. Changes to this setting are not applied retroactively to existing Product Territory Availability records.