Assign a policy by role, department, or individual
Once a policy is published, you decide who it applies to. The platform lets you assign by role, by department, by individual employee, or to all staff at once.
Assign a policy
- Open the policy from the policy library.
- Click Assign (or Repush if it’s an update to a previously assigned policy).
- Choose your targeting method (you can combine multiple methods on the
same assignment):
- All staff. Everyone with a platform account.
- By role. E.g. all managers, all admins.
- By department. E.g. everyone in Operations, Sales, etc.
- By individual employees. Pick specific people.
- Decide if the policy requires acknowledgement (default: yes). If you turn this off, the policy is shared as read-only reference.
- Click to confirm.
The policy now appears in My Policies for everyone you targeted, with an Action required badge if acknowledgement is needed.
How the targeting combines
Targeting is additive: if you select “All managers” plus three individuals who aren’t managers, all four groups are targeted. The platform doesn’t remove people who match more than one criterion, so combining is safe.
If someone matches a target you’ve assigned, they see the policy. Only admin-only HR policies should ever be visible just to admins.
Visibility on the policy detail page
When you open a policy you’ve assigned, the assignment shows in coloured pills:
- Purple pills for roles
- Pink pills for departments
- Cyan pill showing the count of individuals
- “All staff” pill if you’ve targeted everyone
This makes it easy to see at a glance who the policy currently goes to.
Re-assigning later
If your team grows and new people should also see the policy, click Repush to re-run the assignment. Existing acknowledgers aren’t asked to acknowledge again, only the people newly in scope.
If you change the targeting (e.g. swap “All managers” for “All Operations”), the platform follows the new targeting on the next push. People who were on the old list but aren’t on the new one keep their acknowledgement record (it’s not deleted), they just no longer see the policy as required.