Policy error: !community_a community referenced (in term not_communitya) but not defined I've also had problems with commuity_a && comunity_b, is this functionality not implemented? Has anyone figured out a way to match a term based on two (or more) communities all existing, or a community not existing? Thanks. --Phil Rosenthal ISPrime, Inc.