How do I choose who must read a policy?
The Audience tab decides who is required to acknowledge a policy.
How it works
Each row is one rule: a Target Type (All Employees, Department, Location, Employee Type, or a specific Employee) plus, for anything other than All Employees, a target picker. Rules combine with OR — an employee is in the audience if they match any row. (Employee Type is currently entered as a numeric ID rather than a friendly picker.)
The count shown ("employees currently in audience") is live — it reflects today's department/location/employee assignments, resolved when you load or save the tab. It is not the same thing as a past version's frozen publish-time audience (see §7).
The fail-safe rule you must know
Zero audience rows means the policy applies to nobody — never "everybody." If you want a policy to cover the whole company, you must add an explicit All Employees rule; there is no implicit default. Because of this:
- Publishing is blocked if the audience is empty, or if the current rules resolve to zero active employees.
- Removing the last rule from an already-published policy is blocked, so a live policy can never accidentally end up with nobody responsible for it.
Saving
All rows save together in one action (Save Audience) — there's no moment where the old rules are gone but the new ones aren't in place yet.
What audience edits affect — and don't
Editing the audience after a policy is published only changes who is targeted going forward (the live "pending" population). It never rewrites what a past published version's snapshot says historically applied — that snapshot is fixed at publish time and is the evidence record. If you retarget a policy from "Operations only" to "All Employees" after v2 was published to Operations, v2's history still correctly shows only the Operations employees who were covered at the time.
If an audience rule points at a department, location, or employee that's since been deleted, that rule is silently ignored when resolving who's covered — it doesn't error, but it also isn't currently flagged in the UI, so it's worth reviewing your audience rules occasionally if your org structure changes.