GovernDocs PRO adds several advanced features designed for organisations that need stronger policy governance, version tracking and supporting documentation. These features help maintain a clear history of policy updates and allow additional files to be attached to policies when needed.
Upgrading to PRO unlocks tools that make it easier to manage policy lifecycles, track changes, and maintain supporting material alongside the main policy document.
Supporting Docs
Supporting documents allow you to attach additional files related to a policy. These may include appendices, templates, forms, guidelines or reference materials that help explain or support the policy.
Each supporting document can be uploaded and managed alongside the policy, keeping all related material organised in one place.
Audit Log
The audit log records key changes made to a policy over time. This includes updates to the policy status and changes to the attached policy file.
Each entry records who made the change and when it occurred, providing a clear history of policy activity for governance and accountability.
Custom Statuses
Add your own custom statuses to Policies.
You can add whatever statuses you require and these then become available throughout the policies sections.
User Access
The PRO plugin adds new shortcode attributes that allow you to allow only certain roles, or block certain roles from viewing the Policy on the front end.
The shortcode attributes allow you to customise the link/button as well as the text that is displayed to the user.
The example shortcode below allows access to this policy for users with the role of ‘customer’ or ‘subscriber’. The inverse of allowed_roles is blocked_roles, which can be used to block access to any role.
[governdocs id="1118"
allowed_roles="customer,subscriber"
blocked_button_text="Request Access" blocked_button_url="https://example.com/request-access" blocked_button_new_tab="1"
blocked_button_class="button button-primary" blocked_description="This document is not available for your account type."]You can also use guest, logged_out, or not_logged_in inside blocked_roles to show the fallback output to visitors who are not signed in.
