How do I target every department of a TempWorks client in a policy?

Last updated: September 25, 2026

Each TempWorks department syncs into Onboarded as its own client with its own client ID. A rule pinned to one client ID only covers one department — here's how to cover them all.

Why one client ID isn't enough

When a TempWorks customer record carries a department, Onboarded names the synced client Customer name - Department name. A customer called Optimize Logistics with three departments arrives as three separate clients:

  • Optimize Logistics - Grand Prairie

  • Optimize Logistics - Fort Worth

  • Optimize Logistics - Irving

Each one gets its own client.id. So a rule reading client.id is one of those IDs assigns forms to placements at that department and quietly skips the other two. The policy looks correct, the test placement matches, and the gap only shows up once a real hire comes through a different department.

There's no department fact in the rule builder. Departments reach your rules through the client name and through a custom attribute that the TempWorks sync populates.

Pick an approach

Match the customer name — covers departments added later

Because every department's client name starts with the customer name, one condition covers the whole customer:

client.name contains Optimize Logistics

This is the approach to reach for when departments get added over time. A new Optimize Logistics - Plano client falls under the policy the moment it syncs, with no edit from you.

Two things to watch. contains is a substring match, so a customer named Optimize Logistics also catches Optimize Logistics Southwest if that's a separate customer in TempWorks. And matching is case-sensitive unless you turn on the Aa toggle on the condition.

List the client IDs — precise, but you maintain it

When you want exactly these departments and nothing else, list their IDs:

client.id is in 4821, 4822, 4823

Use the is in operator, not is, and enter the IDs as a comma-separated list. This is exact — no risk of catching a similarly named customer — but a department added in TempWorks next quarter won't be covered until someone edits the rule.

Target one named department

The TempWorks sync also writes the department name to a custom attribute on the client, so you can single one out:

client.custom_attributes.tempworks_department_name is Grand Prairie

Custom attributes are only offered in the rule builder on account-level policies. If you're building a policy at the global level, you'll see the built-in facts — client.id, client.name — but not client.custom_attributes.*. Build it as an account policy, or use the client name instead.

Confirm it worked

One department matching isn't proof. Test a placement at a department you didn't have in mind when you wrote the rule — usually the newest or smallest one — and confirm the forms assign there too.

If a department comes up empty, check the client's name in Onboarded against what you typed. A trailing space, a different spelling of the customer name in TempWorks, or a capital letter in the wrong place all produce a rule that matches some departments and not others.

Related