Example Ruleset for Sales Regions

Build an advanced ruleset that combines geographic regions and departments using multiple rules with AND/OR logic.

Overview

This example demonstrates how to build a group that has members from different departments and regions using multiple rules. This is a common pattern for cross-functional groups like “EMEA Sales and Global Marketing.”

This is an example of ({this} and {that}) or {that} — combining AND conditions within a rule with OR logic across rules.

Building the Ruleset

Rule 1: EMEA Sales

We start with a Rule and create a Condition for division {equals} sales, just like we did for a single condition rule.

In the same rule, we add a second condition for region {equals} emea.

When evaluating a rule, all conditions must be true for each user. So only users who are both in the Sales division and in the EMEA region will match this rule.

Rule 2: Global Marketing

Let’s add a second rule. This rule has a single condition where division {equals} marketing. We are not adding any additional conditions to this rule, so any user in Marketing regardless of region (aka global) would be added to the group.

Refining with Region Values

If your organization has a specific attribute value for region that designates a user as global, then you could add a region {equals} global condition to not include users that have any other region values (ex. amer, emea, apac).

Rule 3: Global Sales Leadership (Optional)

If you have that global region attribute and wanted to include your global users (ex. sales leadership) in addition to the emea users, you could add a third rule with two conditions for division {equals} sales and region {equals} global.

Summary

Rule	Condition 1	Condition 2	Users Matched
Rule 1	division {equals} sales	region {equals} emea	EMEA Sales team
Rule 2	division {equals} marketing	—	All Marketing (global)
Rule 3	division {equals} sales	region {equals} global	Sales leadership

Key Concepts

• AND logic within a rule: All conditions in a single rule must be true for a user to match.
• OR logic across rules: A user only needs to match one rule in the ruleset to be included.
• No deny rules: There is no “except” or “deny” rule. If a user qualifies for any rule, they are included.
• Use staged rules to preview users before activating each rule.