Frequently Asked Questions
Is there a Pro version?
Yes. The Free plugin runs the complete policy acknowledgement loop on its own. The Pro add-on is a separate plugin for audit-bound and growing organisations. It adds:
- An accreditation readiness matrix and curated regulatory framework libraries (such as ISO 27001, HIPAA, GDPR, NHS DSPT and NDIS), with AI-assisted framework audits
- Sealed evidence packs for auditors
- Multi-stage approval chains
- Scheduled manager digest emails, a compliance calendar, and per-document reminder cadence
- An extended compliance dashboard
- Minimum reading-time and reading-reach requirements before acknowledgement, with reading progress saved across sessions
- Opt-in AI assistance (FAQ, summary and comprehension-question generation, document interlinking, AI-assisted bulk drafting) using your own OpenAI or Anthropic key — documents marked Confidential are never sent
- Signed outbound acknowledgement webhooks
- Additional PDF template designs
Pro requires the Free plugin to be installed and active. Learn more about Pro.
Does this work on any WordPress site?
Yes — the plugin works on any standard WordPress installation (shared hosting, VPS, managed WordPress). It does not require WooCommerce, Elementor, or any other plugin. The only requirements are WordPress 6.7+ and PHP 8.2+.
Is data sent to any third-party service?
The Free plugin makes no external network requests. All documents, acknowledgements, and staff data remain on your server. The Pro add-on can optionally send acknowledgement webhooks to an HTTPS address you specify, and can call AI providers (OpenAI or Anthropic) with your own API key for AI features — both are off by default and fully opt-in. Pro also contacts the vendor’s licensing server to activate your licence and deliver updates.
Can I use the plugin with existing custom post types?
Yes. The plugin detects existing document or faq post types when it is activated and adds its features to them rather than registering duplicates. You can change which post types and taxonomies it uses under Policy Management → Settings → System Configuration → Post Types & Taxonomies.
Can staff see the acknowledgement history for other users?
No. Staff can only see their own acknowledgements, on the My Acknowledgements page (the Please log in to view your acknowledgements. Log in
What happens to acknowledgement records when the plugin is deactivated or deleted?
Records are stored in the plugin’s own database tables. They persist through deactivation and reactivation.
Deleting (uninstalling) the plugin also keeps your data by default — only the plugin code is removed, and everything is picked up again if you reinstall. Your records are only deleted if you first switch on Remove content & data on uninstall under Settings → System Configuration → Uninstall Behaviour. If you do plan a full removal, export your attestation records first.
Is WCAG 2.2 AA compliance supported?
Yes. The plugin’s front-end and admin screens are built to WCAG 2.2 AA, including keyboard navigation for interactive elements, screen reader support, text alternatives for analytics charts, and contrast-safe colours.
Can I use this for public-facing policies (logged-out visitors)?
Yes. Each document has a Confidentiality setting. Set it to Public to let logged-out visitors read the document and download it as a PDF. All other confidentiality levels require the visitor to log in.
The plugin’s search, and the document and FAQ data it loads in the background, require a logged-in user by default. To let logged-out visitors search Public content, switch on Allow anonymous access under Settings → Search → Public REST API Access.
What about WordPress multisite?
Activate the plugin on each site individually — network activation is not supported. Each site then has its own document library, acknowledgement records, and settings. There is no built-in cross-network sharing; if you need a shared library, manage it on one site and link to that site’s Document Hub page from the others.
How do I give an external auditor read-only access?
Create a WordPress user account and set their role to Policy Auditor. This role can view the Compliance Overview and Analytics dashboards, acknowledgement records, and every document with its version history, and can generate attestation exports — but cannot edit anything or change settings. Delete the account or change its role when the audit is over.