Filters not allowing custom Association Labels to evaluate strictly with Primary Company

Primary company association type

    • Each contact can have multiple associated companies, but only one association can be marked as the Primary company. Other companies are “non‑primary” and may be unlabeled or have custom labels.
    • This “Primary” status is a special association type – it’s not exposed as just another custom label.
  1. Custom association labels (e.g., “Resigned Employee”)

    • Custom labels sit on associations between objects (e.g., contact ↔ company) and can be used in lists and workflows as you’re doing.

In the list/segment builder, when you add a company-based filter in a contact list:

  • You choose an associated object, e.g. Filtering on → Company
  • Then you see a control like: Contact is associated to: Any company / Primary company / Company with label
  • Once you pick one of those, the nested “where … associated companies match” conditions (e.g. Company Domain Name is known) are evaluated only against the companies in that bucket (primary or a specific label).

Right now, there is no UI option to say:

“Only consider the Resigned Employee label on the same company that is also the Primary company.”

There should be a way to get around this.

:100: @KyleJepson, can you help get this to the right product manager? We’d love to know if this is in their radar. This made us realize that marking “Resigned employees” is not that simple.

I think the bigger issue here is that you’re trying to represent one relationship state using two different association concepts.

If “Resigned Employee at the primary company” actually drives workflows or reporting, I wouldn’t rely on every filter being able to reconstruct that relationship corectly

I’d probably materialize that state somewhere explicit instead — for example a contact property that’s updated when the primary company or the relevant association label changes.

Then your operational logic can use that property, while the associations remain the source of truth

The one thing to watch is keeping it in sync when the primary company changes. Otherwise you just move the ambiguity from the filter into stale data.