How do I add form-level conditions to a policy?

Last updated: November 2, 2026

Add a second-layer rule to a specific form on a policy, so that form is only assigned when extra conditions are met — even though the policy itself matches.

Before you start

  • A policy that's already created with at least one form attached. See 📄 How do I build a policy? if you're not there yet.

  • A clear idea of which form should be conditional and what the condition should be. If every form on the policy needs to attach in every match, you don't need this — leave the Conditions blank.

When to use form-level conditions

A policy's top-level Rules decide whether the policy applies at all. Form-level Conditions are a finer filter inside a matching policy — they decide which specific forms attach.

Reach for form-level conditions when:

  • You want to bundle related onboarding requirements into one policy instead of spreading them across many.

  • Most of the forms in a policy should attach to every match, but one or two should only attach in specific cases.

  • Splitting the work into a second policy would create more overlap than clarity.

If every form on a policy should always attach when the policy matches, leave the Conditions blank. There's no benefit to adding redundant conditions.

Steps

  1. Open the policy from the Policies page.

  2. In the policy's Forms section, click the form you want to make conditional.

    The form expands. A form with no condition shows Add condition; a form with one shows it, with Edit beside it.

  3. Click Add condition, or Edit if the form already has one.

    The Edit condition dialog opens, with the form's name in its title and a rule builder underneath.

  4. Build the rule using the rule builder. Set a fact, operator, and value — exactly the same shape as a policy-level rule.

    • For more than one condition, use the And / Or group toggle to combine them.

    • See 📄 Rule operators for the full list of operators and what each one does.

  5. Click Save.

    The dialog closes, and the form's Conditions now show the rule you set.

Form-level conditions only apply going forward. Placements that already exist when you change a condition won't pick up the change automatically.

Verify

Create two test placements:

  • One that matches the policy's top-level Rules and the form's Conditions. The conditional form should be assigned, alongside the policy's other forms.

  • One that matches the policy's top-level Rules but not the form's Conditions. The conditional form should be skipped; the rest of the policy's forms should still attach.

If the conditional form attaches when it shouldn't (or vice versa), check:

  • The policy itself is enabled. Form-level conditions don't matter if the parent policy isn't firing.

  • The condition value matches what's stored on the placement exactly — case included. Forklift Driver won't match forklift driver.

  • The fact path is correct for your account. Most placement-level data lives under placement.custom_attributes.*, not as top-level placement fields.

Related