The user needs to be in 1 of the 2 branches listed. We’re using groups based on our (country-based) branches to define geographical regions, and it wouldn’t work otherwise. In the branch condition you should also see this phrase “Users will be included into the group according to the branch they belong to”, which indicates that users only need to be part of 1 of the branches that are added as critera.

If you’re not using the group for any automation yet, you can also easily test it since those conditions can always be edited and the platform adds/removes users instantly.

The way you have it now where the set mist have all conditions satisfied, the user would have to belong to both branches to belong to the group. You can create a set for each branch and change your rules to “user must satisfy at least one set but leave your set to, all conditions must be satisfied. This creates a “OR” relationship between the sets.

We have it configured like this and it works perfectly fine:

I wouldn’t create an additional set for each branch. If you want to add a split, I’d rather add another condition within the set and switch the set to “at least condition must be satisfied”. But technically it’s not necessary. We have all 3 branches in one set and it works. Every user on our platform is part of 1 single branch and the group would be empty if the user had to belong to all 3 branches. The “all conditions must be satisfied” refers to the different “lines” you have within the set, Each line is a condition. The different branches within the condition are not conditions themselves.