Some policies contain sensitive information, and you may not want every view to be tracked or recorded. The Policy Hub allows you to make policy views anonymous. When you enable this option, users who are not required to attest to a policy can view it without generating a training record. This means administrators cannot report on who has viewed that policy.
This feature is especially helpful for sensitive policies, such as maternity or paternity leave, where visibility may need to be more private.
This guide explains what anonymous views mean, when to use them, and how to enable this feature.
What Anonymous Views Mean
When you enable anonymous views:
Users who are not required to attest can view the policy without their view being tracked.
No training record is created for those users.
Administrators will not be able to report on who has viewed the policy.
Sensitive information remains protected because individual view activity is not captured.
If a user is required to attest, their attestation will always be recorded. Anonymous views do not apply in those cases.
When You Can Enable Anonymous Views
You can enable anonymous views at two key points in the policy workflow, depending on how your organisation manages policy approvals:
During assignment (if the policy is being assigned without attestation).
When publishing (if you are using the approval workflow).
The following articles provide step-by-step instructions on enabling this option within each workflow:
Assigning a Policy without an Attestation
Publishing a Policy using the Approval Workflow
How the Feature Works
You can enable anonymous views at either of the following stages:
1. When assigning a policy without attestation
If you are assigning a policy that does not require users to attest, you can enable anonymous views during the assignment process. This ensures that when users access the policy, no view tracking occurs.
2. When publishing a policy through an approval workflow
If your organisation uses the approval workflow, you can activate the anonymous option during publication. This is useful for policies still under review or for policies that will not require attestation.
Notes and Limitations
Note:
If a policy has already been assigned and viewed, enabling anonymous views does not apply retrospectively. Any views recorded before the option was enabled will remain reportable.
If you later disable the anonymous view option, views will only become reportable from that point onward. Prior anonymous views will remain anonymous and cannot be identified.
If a policy requires attestation, this feature has no effect. User attestations will always be recorded.
Conclusion
You now understand how and when to make policy views anonymous. This feature helps you protect user privacy and manage sensitive policies more appropriately. If you need step-by-step instructions, follow the related articles below: