Dantian Policy Management & Acknowledgements

By Jason Chong

0+ active installationsVersion 1.0.1

Publish staff policies, track who read which version, and export audit-ready proof. Self-hosted: no SaaS, no subscription.

Description

Did everyone read the new policy? Which version did they acknowledge? Can you prove it to an auditor?

Dantian Policy Management turns WordPress into a self-hosted policy management system. Publish your staff policies, procedures and SOPs, have each person read and acknowledge them (a “read and sign” policy acknowledgment), and export proof of who read which version, in what role, and when — with a digital fingerprint showing the text has not changed since. It all runs on infrastructure you already own — no vendor cloud, no subscription, no data leaving your building.

Documentation · Pro add-on · Support forum

Who it’s for

  • Healthcare, aged care and disability providers — clinical and NDIS policies that every staff member must confirm they have read.
  • Schools, RTOs and training organisations — staff handbooks, child-safety policies and evidence for accreditation.
  • HR and operations teams — the employee handbook, code of conduct and onboarding sign-off, kept current in one place.
  • Any organisation facing audits — evidence that policies were published, read and reviewed, for ISO, SOC 2, HIPAA or GDPR programmes.

Core features

  • Policy acknowledgement tracking — staff confirm each policy they must read; acknowledgements expire on your schedule, reminders go out automatically, and a new version asks people to re-acknowledge.
  • Version control and approval — every version is snapshotted, compared side by side, and can be restored. Optionally, changes to a published document wait until its owner (or an approver) approves them, from an emailed link with no login needed.
  • Role-based visibility, gated by default — staff outside a document’s audience cannot find, search, or open it.
  • Tamper-evident audit trail — every acknowledgement stores a SHA-256 fingerprint of the exact text that was read.
  • Compliance dashboard and attestation export — compliance by role, who is overdue or expiring, and a checksummed CSV or PDF report to hand your auditor.
  • Import your existing policies — upload a ZIP of Word, PDF, plain-text or Markdown files and get a draft document for each one.
  • Optional extras — comprehension quizzes, acknowledgement campaigns, page gating until policies are read, and staff edit suggestions.
  • Regulatory frameworks — optional, off by default (Settings → Features → Enable Regulatory Frameworks): map documents to the standards you follow, with CSV import and export.

Knowledge base & search

The same plugin publishes your documents to staff through a role-gated knowledge base: a tabbed hub, instant search, filterable listings, category browsing, a documentation portal, and FAQs with feedback, each placed with a shortcode such as [dpma_hub] or [dpma_kb]. Restricted documents never appear in search or listings for people outside their audience.

  • Related documents — link related policies on any document; readers see them on the page and as Appendix A of the PDF, filtered to what each reader may see.

Privacy by design

No telemetry, no “phone home”, no vendor cloud. The Free plugin’s own code makes no external network requests. The one exception is a check to this site’s own uploads address that the private upload folder is not publicly readable. (Third-party media an administrator chooses to embed in FAQ answers — for example a YouTube or Loom video — is loaded by the visitor’s browser as normal, restricted by the dpma_faq_allowed_iframe_hosts allowlist.)

Pro add-on (separate plugin)

For audit-bound and growing organisations, Dantian Policy Management Pro adds:

  • Accreditation-readiness matrices and curated framework libraries — ISO 27001, ISO 9001, SOC 2, HIPAA, GDPR, NIST CSF, PCI DSS, NHS DSPT, NDIS and more
  • Sealed SHA-256 evidence packs
  • Multi-stage approvals, escalation of expired acknowledgements, and scheduled manager digests
  • Opt-in AI authoring with a built-in confidentiality gate (your own OpenAI or Anthropic key)
  • Signed acknowledgement webhooks and five additional PDF template designs

The Free plugin works completely on its own; Pro is never required.

Third Party Services

Embedded Content in FAQ Answers and Documents

An FAQ answer or a document may embed a video, document, form, presentation or audio player from an allowed service — by default YouTube, Vimeo, Google Docs, Google Drive, Google Calendar, Microsoft Forms, Microsoft Sway, Microsoft Office Online, Termageddon, Loom, Canva, SlideShare, Spotify, SoundCloud. Site code can change the allowed services with the dpma_faq_allowed_iframe_hosts filter. When a visitor opens that answer or document, their browser loads the embedded content from that service, which receives the visitor’s IP address and browser details under its own privacy policy.

  • YouTube: privacy https://policies.google.com/privacy · terms https://www.youtube.com/t/terms
  • Vimeo: privacy https://vimeo.com/privacy · terms https://vimeo.com/terms
  • Google Docs: privacy https://policies.google.com/privacy · terms https://policies.google.com/terms
  • Google Drive: privacy https://policies.google.com/privacy · terms https://policies.google.com/terms
  • Google Calendar: privacy https://policies.google.com/privacy · terms https://policies.google.com/terms
  • Microsoft Forms: privacy https://privacy.microsoft.com/privacystatement · terms https://www.microsoft.com/servicesagreement
  • Microsoft Sway: privacy https://privacy.microsoft.com/privacystatement · terms https://www.microsoft.com/servicesagreement
  • Microsoft Office Online: privacy https://privacy.microsoft.com/privacystatement · terms https://www.microsoft.com/servicesagreement
  • Termageddon: privacy https://termageddon.com/privacy-policy/ · terms https://termageddon.com/terms-conditions/
  • Loom: privacy https://www.atlassian.com/legal/privacy-policy · terms https://www.atlassian.com/legal/atlassian-customer-agreement
  • Canva: privacy https://www.canva.com/policies/privacy-policy/ · terms https://www.canva.com/policies/terms-of-use/
  • SlideShare: privacy https://www.slideshare.net/privacy · terms https://www.slideshare.net/terms
  • Spotify: privacy https://www.spotify.com/legal/privacy-policy/ · terms https://www.spotify.com/legal/end-user-agreement/
  • SoundCloud: privacy https://soundcloud.com/pages/privacy · terms https://soundcloud.com/terms-of-use

Remote Content in PDFs

PDF generation does not fetch remote images or fonts. Site code can turn remote fetching on with the dpma_dompdf_options filter; if it does, the server requests those files from the sites hosting them when a PDF is built, which gives those sites the server’s IP address and the address of each file requested.

Bundled Libraries

This plugin bundles the following open-source libraries. No external network requests are made by the libraries themselves; they run locally inside the plugin.

  • Dompdf (https://dompdf.github.io/) 3.1.6 — LGPL-2.1. Server-side HTML/CSS-to-PDF generation for document, attestation, and report exports.
    • dompdf/php-font-lib 1.0.2 — LGPL-2.1-or-later.
    • dompdf/php-svg-lib 1.0.2 — LGPL-3.0-or-later.
    • masterminds/html5 2.12.0 — MIT.
    • sabberworm/php-css-parser 9.5.0 — MIT.
    • DejaVu Sans fonts (Dompdf’s Unicode font, vendor-prefixed/dompdf/dompdf/lib/fonts/) — DejaVu Fonts License (Bitstream Vera and Arev terms; free, GPL-compatible); full text in licenses/DejaVu-Fonts-LICENSE.txt.
  • Parsedown (https://parsedown.org/) 1.8.0 — MIT. Markdown-to-HTML conversion used during bulk document import.
  • PdfParser (https://github.com/smalot/pdfparser) 2.13.1 — LGPL-3.0. Pure-PHP text extraction from uploaded PDF files during bulk document import.

Two dependencies are LGPL-3.0-family (php-svg-lib and PdfParser itself), not GPL-2.0-compatible on their own — GPLv2-only code cannot legally combine with LGPL-3.0 code. This plugin is licensed GPL-2.0-or-later, so the distributed combination resolves under the GPL-3.0 terms that grant permits, making it GPL-compatible; it would not be compatible under a strict GPL-2.0-only grant. Full license texts are shipped inside the respective vendor-prefixed/ subdirectories.

Privacy

This plugin stores personal data relating to knowledge-base and policy governance activity. Site administrators are responsible for disclosing this processing to their users where required (GDPR, HIPAA, etc.). The full list of what is stored, why, and how long each item is kept with the default settings is the plugin’s suggested privacy-policy text under Settings → Privacy → Policy Guide, generated from the same personal-data registry the export and erasure tools use. The Privacy & Data Management page of the user guide covers it in more depth.

What it stores:
* In its own database tables: Document acknowledgements, Edit suggestions, FAQ and document feedback, PDF downloads, Document view history, Search queries, Document version snapshots, Governance event log, Event log index, Repeat-view throttle.
* On user profiles: Bookmarks, Saved searches, Reminder email preference, Dismissed notices, Notices after an action (on the user profile), Comprehension quiz attempts.
* In post meta and options: Suggestion being applied (kept on the document), Applying a suggestion (kept on the document), Search suggestion list, Version history, Changes awaiting approval, Scheduled versions, Approval decisions, Kept change text, Owner review sign-offs, Audience lists, Document owner assignments, Reminder history, Compliance reminder history, Queued reminders, Scheduled reminders, Email sender address, Deleted accounts.
* Short-lived data: Generated export files, Cached PDFs, Background export and import jobs, Rate limiting, Cached document lists, Notices after an action (short-lived copy), File imports.
* Cookies: View throttle cookie.
* Client-side storage: Browser search cache.

Whether a person’s identity, an IP address or a download is recorded is controlled by these settings under Settings → Access & Privacy:

  • Record IP Address with Acknowledgements (Document acknowledgements): off by default
  • Store FAQ Feedback IP Address (FAQ and document feedback): off by default
  • Track PDF Downloads (PDF downloads): off by default
  • Track View User Identity (Document view history): off by default
  • Track Search User Identity (Search queries): off by default

Content from other websites:
Embedded content, Remote content in PDFs. Each is described under Third Party Services above.

Data shared with third parties:
Apart from the content from other websites listed above — which a visitor’s browser loads from the service hosting it, and which the PDF generator fetches only if site code turns that on — this plugin alone shares no data with third parties.

WordPress Privacy API integration:
The plugin registers a personal data exporter and a personal data eraser for the kinds of data that an export or erasure request can reach; the lists below name the kinds each request does not reach. Administrators can invoke these from Tools → Export Personal Data / Tools → Erase Personal Data. What an export request leaves out:

  • Not included in an export: Suggestion Being Applied (Kept on the Document), Applying a Suggestion (Kept on the Document), Search Suggestion List, Event Log Index, Repeat-View Throttle, Dismissed Notices, Notices After an Action (On the User Profile), Queued Reminders, Scheduled Reminders, Email Sender Address, Generated Export Files, Cached PDFs, Rate-Limit Counters, Cached Document Lists, Notices After an Action (Short-Lived Copy), Document File Imports in Progress, Browser Search Cache, View Throttle Cookie — an export request does not include these; the suggested privacy-policy text says what each holds and how long it is kept.

Acknowledgement records are anonymised on erasure (user ID set to 0, IP removed) rather than deleted, so the compliance audit trail survives: the document, version, date, the role the person held, how it was given, any quiz answers and score, reading time and reach, and the expiry date are kept. What an erasure request does to each kind of data:

  • Anonymised (the person’s identity is removed and the record is kept for the audit trail): Document Acknowledgements, Version Snapshots, Event Log, Document Version History, Changes Awaiting Approval, Scheduled Versions, Approval Decisions, Kept Change Text, Owner Review Sign-offs.
  • Deleted: Suggestion Being Applied (Kept on the Document), Applying a Suggestion (Kept on the Document), Document Edit Suggestions, FAQ and Document Feedback, PDF Download History, Document View History, Search History, Event Log Index, Bookmarked Documents, Saved Searches, Reminder Email Preference, Dismissed Notices, Notices After an Action (On the User Profile), Comprehension Quiz Attempts, Acknowledgement Reminder History, Compliance Reminder History, Queued Reminders, Scheduled Reminders, Generated Export Files, Background Export and Import Jobs, Document File Imports in Progress, Deleted Account Records.
  • Kept: Audience Lists — Audience-list memberships naming this person were kept: removing them would change who is required to acknowledge a policy. An administrator can remove the person from each list.
  • Kept: Document Owner Assignments — Document owner assignments naming this person were kept: removing them would leave documents with no reviewer or approver. An administrator can reassign them; they are removed when the user account is deleted.
  • Note kept: Document Version History — the person’s identity is removed, but the free-text note written with each record is kept as part of the audit trail.
  • Note kept: Changes Awaiting Approval — the person’s identity is removed, but the free-text note written with each record is kept as part of the audit trail.
  • Note kept: Scheduled Versions — the person’s identity is removed, but the free-text note written with each record is kept as part of the audit trail.
  • Note kept: Owner Review Sign-offs — the person’s identity is removed, but the free-text note written with each record is kept as part of the audit trail.
  • No eraser of its own: Search Suggestion List, Repeat-View Throttle, Email Sender Address, Cached PDFs, Rate-Limit Counters, Cached Document Lists, Notices After an Action (Short-Lived Copy), Browser Search Cache, View Throttle Cookie — no eraser is registered for these; the suggested privacy-policy text says what each holds, how long it is kept and what removes it.

Note: the WordPress exporter and eraser match rows by user account. Deleting an account does not anonymise or delete the person’s records; the plugin records a one-way hash of the deleted account’s email address, so a later request for that address still finds them, and the hash is removed when the erasure completes. Feedback submitted by logged-out visitors (which carries no account) cannot be targeted by an individual erasure request; those rows are cleared by the configurable retention purge instead. Suggested privacy-policy text is registered via wp_add_privacy_policy_content() and appears on Settings → Privacy → Policy Guide for administrators to copy into their site privacy policy.

Retention settings: the retention windows are settings under Settings → Access & Privacy → Analytics & Data Retention; a value of 0 retains indefinitely.

On uninstall: all plugin data is preserved by default — removing the plugin code does not destroy your acknowledgement evidence trail or configuration. Two opt-in toggles under Settings → System Configuration → Uninstall Behaviour, both OFF by default, remove it before you delete the plugin:

  • Remove content & data on uninstall — hard-deletes every Document and FAQ post, the plugin’s taxonomy terms and its own database tables, including the acknowledgement evidence trail and activity logs, and the private upload folder. This cannot be undone. Of the personal data above, it removes: Document Acknowledgements, Suggestion Being Applied (Kept on the Document), Applying a Suggestion (Kept on the Document), Document Edit Suggestions, FAQ and Document Feedback, PDF Download History, Document View History, Search History, Search Suggestion List, Version Snapshots, Event Log, Event Log Index, Repeat-View Throttle, Bookmarked Documents, Saved Searches, Reminder Email Preference, Dismissed Notices, Notices After an Action (On the User Profile), Comprehension Quiz Attempts, Document Version History, Changes Awaiting Approval, Scheduled Versions, Approval Decisions, Kept Change Text, Owner Review Sign-offs, Audience Lists, Document Owner Assignments, Acknowledgement Reminder History, Compliance Reminder History, Queued Reminders, Scheduled Reminders, Cached PDFs, Deleted Account Records.
  • Remove configuration & capabilities on uninstall — deletes all plugin options, transients and scheduled events, and the plugin’s capabilities and role. Of the personal data above, it removes: Search Suggestion List, Document Owner Assignments, Acknowledgement Reminder History, Compliance Reminder History, Queued Reminders, Scheduled Reminders, Email Sender Address, Rate-Limit Counters, Cached Document Lists, Notices After an Action (Short-Lived Copy), Document File Imports in Progress, Deleted Account Records.

Background export and import jobs and their generated files are temporary working data and are always removed on uninstall, whatever the toggles.

Installation

From the WordPress plugin directory

  1. Go to Plugins → Add New in your WordPress admin.
  2. Search for “Dantian Policy Management” and click Install Now.
  3. Click Activate when the install finishes.

Manual install

  1. Download the ZIP from this page.
  2. Upload the unzipped dantian-policy-management folder to /wp-content/plugins/.
  3. Activate the plugin through the Plugins menu in WordPress.

First-day setup (5 minutes)

  1. Dantian Policy Management → Settings → Acknowledgements & Notifications — set your default acknowledgement expiry period (typically 365 days for annual policies) and decide whether read-time capture is on. Comprehension quizzes are added per document, in the document editor.
  2. Dantian Policy Management → Settings → Appearance — set your brand colours. These appear throughout the frontend knowledge base and in exported PDFs. Under Settings → PDF Export you can also add your logo, switch on a cover page, and set a cover boilerplate statement.
  3. Documents → Add New — create your first policy. In the right-hand sidebar, set the audience (which roles can see it), the owner, the review cycle, and the effective date.
  4. Publish — the document goes live for everyone in its audience. If you switch on Settings → Features → Enable Version Approval, later changes to a published document wait for its owner, or for the approver roles when it has no owner, who approve or reject them from an emailed link — no login required.
  5. Add [dpma_hub] to a page — your staff visit that page, see the policies they have to read, and acknowledge them. The Compliance Overview dashboard updates shortly after, and shows when its figures were last refreshed.

Default document types

Activation creates Policy, Procedure, Guide, and Form. Add more under Settings → Content Management → Manage Document Types.

FAQ

How does this compare to dedicated policy management software?

The core loop — controlled publication, version-by-version acknowledgements, role-based access, owner approval workflow, and auditor-ready exports — is what most teams pay thousands of dollars a year for in dedicated SaaS tools. The Free plugin covers that loop entirely, self-hosted, on infrastructure you already own. Areas where enterprise SaaS tools go further: multi-stage approval routing, AI-driven workflow automation, a choice of PDF template designs, and integrations with HR or security-audit systems — most of which are available in the optional Pro add-on.

Can I use it as a knowledge base or documentation plugin?

Yes — and everything below is in the free plugin, with no add-on required. Underneath the governance features is a complete knowledge base:

  • Documentation portal — [dpma_docs] turns any tagged set of documents into a docs site with category landing pages, a sidebar article tree, previous/next navigation, and clean deep-linkable URLs.
  • Instant search — live AJAX search across titles, content, and categories, with saved searches and bookmarks for regular readers.
  • Browsable listings — a tabbed hub, category-grouped knowledge-base layouts, and filterable document lists, each placed with a shortcode.
  • FAQs — accordion FAQ pages with helpful / not-helpful voting, and FAQPage structured data for search engines.
  • Search analytics — see what people search for and which searches return nothing, with one-click links to write the missing article or FAQ.
  • Versioning and PDF — every article keeps a version history with side-by-side diffs and restore, and readers can download a branded PDF.

If you only need a help centre or internal wiki, you can leave acknowledgements switched off and use it as exactly that. When you later need staff to formally confirm they have read a specific version — and to prove it to an auditor — the governance layer is already there.

Can the knowledge base be public, or staff-only?

Either, per item. Mark a document or FAQ as Public and anyone can read it; to let signed-out visitors use the plugin’s search boxes too, enable Settings → Access & Privacy → Public REST API Access (off by default). Leave it Internal and it is limited to the roles you choose. Restricted content is filtered out of search results and listings — not just hidden behind a link — so one site can run a public help centre and a staff-only policy library side by side.

Does it support HIPAA, GDPR, ISO 27001, NHS DSPT, ASQA/NDIS, FERPA, or Joint Commission?

The plugin provides the technical foundations those frameworks typically require — controlled publication, role-based access, acknowledgement evidence, document integrity records, and full audit history — but meeting a specific regulatory standard is always the organisation’s responsibility and depends on your policy content, processes, and the rest of your environment. Because the plugin is self-hosted and never transmits data externally on its own, it fits cleanly into regulated environments where cloud tools are not permitted. Several frameworks explicitly require self-hosting or controlled data residency; this plugin is built to those constraints by default.

Does the plugin “phone home”? Does it transmit any data externally?

No. The Free plugin makes no external network requests during normal operation. The one exception is a check to this site’s own uploads address that the private upload folder is not publicly readable. The Free plugin alone is fully self-contained.

How do you “prove” a user read a specific version of a policy?

Every acknowledgement record stores: the staff member’s user account and role, the document and version they acknowledged, a digital fingerprint of the document text at that version (a SHA-256 hash), the timestamp, and how it was recorded (by the reader, by an administrator on their behalf, or by an owner sign-off). Each record is sealed when it is written with a tamper-evident integrity seal — a keyed checksum (HMAC-SHA256) made with your site’s secret keys, so someone who can edit the database but cannot read wp-config.php cannot forge it — and the attestation export states, for every record, whether it still matches its seal. Changing the site’s secret keys (AUTH_KEY / AUTH_SALT in wp-config.php) makes existing seals read as modified until they are re-sealed. You can also optionally capture how long they spent reading and how much of the content they actually read — switch it on under Settings → Acknowledgements & Notifications and both values are recorded on the acknowledgement and included in the attestation export.

Export the attestation report at any time and you have a checksummed record ready to hand to an auditor. If the policy text is later updated, the fingerprint in the old acknowledgement records still matches the original version — the evidence trail does not silently rewrite itself.

Can I migrate from another tool? Do you have an import option?

The Free plugin includes a built-in file importer: upload a ZIP of Word (.docx), PDF, plain-text, or Markdown files and the plugin creates a draft document from each one. After import you configure audience, visibility, and review cycles inside the plugin. Most teams migrate from an existing policy-management system by exporting their library to PDF/Word and importing via this tool.

What’s the difference between Free and Pro?

Free runs the complete policy acknowledgement loop on its own:

  • Version-controlled documents with role-based visibility, and single-stage version approval (tokenised owner email)
  • Acknowledgement tracking with per-role compliance rates, and read-time and scroll-reach capture on acknowledgements
  • Automatic reminders on a per-risk-tier schedule (by default Critical 30/14/7/1, High 30/7/1, Medium 30/7 and Low 14 days before expiry, with repeat follow-ups for overdue Critical, High and Medium documents; unrated documents use the individual schedule, 30/7/1 by default, and get one follow-up 7 days overdue), all configurable
  • Signed attestation exports (CSV and PDF, carrying your own logo and brand colours with an optional cover page), and a per-user “where am I up to” acknowledgement export
  • The full comprehension-question gate (pools, randomised sampling, configurable pass thresholds, retry limits) and acknowledgement campaigns
  • The document compliance report shortcode, page gating, edit suggestions, bookmarks and saved searches
  • The read-only auditor role and the full browsable knowledge-base hub

Pro is for audit-bound and growing organisations. It adds:

  • Audit readiness — the accreditation readiness matrix, curated framework libraries (ISO 27001, ISO 9001, SOC 2, HIPAA, GDPR, NIST CSF, PCI DSS, NHS DSPT, NDIS and more), sealed evidence packs, and AI-assisted framework audit
  • Operating cadence — escalation of expired acknowledgements to document owners and a compliance lead, multi-stage approval, scheduled manager digests, the per-document compliance dashboard, and the compliance calendar
  • Privacy-gated AI — every governed document is classified before any request leaves your server, so documents you mark Confidential are never sent to a provider and Restricted ones are kept off by default (FAQ, comprehension and summary generation read the document’s own text; framework reference material you upload carries no classification and is sent when you use briefs, so do not upload anything you do not want sent)
  • More output options — webhooks, AI-assisted bulk drafting, and a choice of five additional PDF template designs (Free ships one, and it carries your branding)
  • Stronger evidence — enforced minimum read-time/scroll gates with cross-session reading progress (basic capture is Free), and AI question drafting and review for the comprehension engine (the question gate itself is Free)

Pro is a separate plugin — Free works completely without it. See pricing.

Can auditors access the plugin without write access?

Yes — the plugin ships a dedicated Policy Auditor user role with read-only access to acknowledgement logs, attestation exports, and the compliance dashboard, but no ability to create or modify documents. Assign the role to your external auditor’s WordPress user during the audit window; revoke after.

Can users suggest edits without changing the live document?

Yes. The Edit Suggestions feature (enabled in Settings → Features) lets the roles you select for each document type submit suggested changes to a document. The original stays unchanged; the suggestion goes to a moderation queue where editors or admins can approve, edit-and-approve, or reject. Each accepted suggestion creates a new version; when version approval is on and the document has an owner, that version waits for the owner’s approval before it goes live.

What does my server need?

WordPress 6.7 or later and PHP 8.2 or later, with the PHP mbstring extension — standard on virtually all hosts. If mbstring is missing, the plugin shows an admin notice and stays inactive until your host enables it. PDF export also uses PHP’s DOM and iconv extensions, and PDF text import uses iconv and zlib — all enabled in standard PHP builds.

Does it work with multisite?

Activate it per site. Each site then keeps its own document library, acknowledgement records, and roles.

Network activation is not supported: the plugin’s database tables are created for the site being activated, not for every site on the network, so subsites would run against tables that do not exist. There is also no “share policies across the network” feature. If you need either, drop a question in the support forum.

Can I customise the acknowledgement banner / button text / email templates?

Many user-facing strings are editable. Per document, you set the acknowledgement intro text and the confirmation checkbox text. In Settings you can edit the access-denied screen text, every email subject, and the body of manually sent (individual) reminders. The acknowledge button label and the body of the scheduled reminder emails are fixed text (translatable). For full template control, use the standard WordPress filter pattern — see the user and developer documentation.

Can I use my existing ‘document’ or ‘faq’ post types?

No. The plugin registers its own dpma_document and dpma_faq post types and does not take over post types from a theme or another plugin, so content in those types stays where it is. Their keys can be renamed under Dantian Policy Management → Settings → System Configuration → Post Types & Taxonomies, but not to a key another plugin or theme already uses.

How do acknowledgement expirations work?

Each document has a configurable expiry period (in days). When a user acknowledges, their record is valid for that window. After expiry the user is prompted to re-acknowledge. A new version resets the requirement when its change type is at or above the Re-Acknowledgement Trigger Level (default: major versions only; Settings → Acknowledgements & Notifications). Expired and expiring-soon records appear on the Compliance Overview dashboard.

What happens to acknowledgement records if a user is deleted from WordPress?

Deleting a user account does not anonymise or delete their acknowledgement records. The records keep the deleted account’s user ID, IP address and the rest of the record, so your audit trail survives. When the account is deleted, the plugin keeps a one-way hash of their email address (made with a key unique to your site; the address itself is not stored) with the former user ID, so the Tools → Export Personal Data and Tools → Erase Personal Data tools still find their records when you enter that email address later. If a new account now uses the same address, one request covers both: the new account’s records and the deleted account’s. Completing an erasure request removes that hash. The key that makes the hash is generated by the plugin and kept in its own (non-autoloaded) option, so changing your site’s secret keys (AUTH_SALT / AUTH_KEY) does not affect it. To manage the key yourself, define DPMA_PRIVACY_HASH_KEY in wp-config.php (a long random string, set once): changing or removing it later stops hashes made with it matching, in the same way. An erasure request anonymises acknowledgement records rather than deleting them — the user ID, the IP address and any reason given for acting on someone’s behalf are removed, but the record itself (document, version, timestamp, the role the person held, how it was given, any quiz answers and score, reading time and reach, and the expiry date) stays intact — and the behaviour is documented under Settings → Privacy → Policy Guide. The plugin always anonymises acknowledgement records on erasure; there is no setting or filter to delete them or to keep the user ID instead.

Which shortcodes can I use, and what attributes do they take?

[dpma_hub]

Displays the Document Hub: the visitor’s outstanding acknowledgements, search, document-type tabs, and recent / popular / recently viewed lists.

Attributes:
* show_obligations – Show the visitor’s outstanding-acknowledgement summary (default: true)
* show_search – Show the search bar (default: true)
* show_tabs – Show document-type tabs (default: true)
* show_recent / show_popular / show_recently_viewed – Show those side lists (default: true; Recently Viewed needs Track View User Identity on)
* recent_count / popular_count – Items in those lists (default: 5)
* initial_show – Documents per category box before a “View all N documents” link to the category archive (default: 5; 0 = heading and link only). Boxes for documents with no category list everything, with a “Show N more” button after this many
* doc_types – Order of the type tabs, comma-separated (default: policies,procedures,guides,forms)
* tag – Limit the hub’s search to documents with this tag; tabs and lists are not filtered

[dpma_search]

Displays a standalone search form with results inline.

Attributes:
* placeholder – Search input placeholder text
* tag – Limit results to documents with this tag (comma-separate several to require all of them)

[dpma_documents]

Displays a filterable list of documents.

Attributes:
* type – Filter by document type slug
* category – Filter by category slug
* tag – Filter by document tag slug (comma-separate several to match any of them)
* limit – Number of documents to show (default: 20; at most 500 unless a site raises or lifts that with the dpma_document_list_max filter)
* columns – Grid columns (default: 1, max: 3; a larger value is treated as 3)

[dpma_kb]

Displays documents grouped by category — a browsable knowledge-base layout. Each category appears as a labelled section with its first documents listed beneath it and a “View all N documents” link to the category archive when there are more. Empty categories are hidden automatically.

Attributes:
* type – Restrict to a specific document type slug
* category – Show only this single category slug (default: all categories)
* show_filter – Display a category filter nav at the top: ‘true’ or ‘false’ (default: ‘false’)
* initial_show – Documents per category section before its “View all N documents” link (default: 10; 0 = heading and link only)

Examples:
* [dpma_kb] – All categories with their documents
* [dpma_kb show_filter="true"] – All categories with a clickable category nav at the top
* [dpma_kb type="policy" show_filter="true"] – Only Policy documents, grouped by category
* [dpma_kb category="hr"] – HR category only

[dpma_faqs]

Displays a list of Frequently Asked Questions with search and interactive UI.

Attributes:
* category – Filter by FAQ category slug (e.g., ‘technical’, ‘policy-questions’)
* limit – Maximum number of FAQs to display (default: 200)
* style – Display style: ‘accordion’ (default), ‘list’, or ‘grid’
* show_search – Show search box: ‘true’ or ‘false’ (default: ‘false’)
* search_only – Hide the FAQs until the visitor searches (default: ‘false’)
* orderby – Sort by: ‘title’ (default), ‘date’, ‘views’, or ‘order’ (a sort-order value set in the FAQ’s Source Document panel)
* order – Sort direction: ‘ASC’ or ‘DESC’ (default: ‘ASC’)
* heading_level – Heading level for each question in the list and grid styles (default: 3)

Examples:
* [dpma_faqs] – Show all FAQs in accordion style
* [dpma_faqs category="technical" show_search="true"] – Show technical FAQs with search
* [dpma_faqs style="grid" limit="6" orderby="views"] – Show 6 most viewed FAQs in grid layout

[dpma_faq]

Displays a single FAQ by ID.

Attributes:
* id – FAQ post ID (required)
* heading_level – Heading level for the question (default: 2)

Example:
* [dpma_faq id="123"] – Display FAQ with ID 123

[dpma_docs]

Docs Portal — displays documents with the given tag in a three-column reading layout. Left sidebar: chapter navigation. Centre: document content. Right: table of contents. Includes tag-scoped search, ordered prev/next navigation, and “Was this helpful?” feedback. (This is separate from the Document Hub, [dpma_hub].)

Documents join a portal by carrying its tag, provided their document type is switched on for portals (Show in Docs Portal ([dpma_docs]) under Settings → Content Management → Manage Document Types; by default just Guide, plus documents with no type). Order within a portal is set by the document’s Portal order field; equal values sort alphabetically by title.

Attributes:
* tag (required) — Document tag slug that scopes the portal.
* facet — Comma-separated tag slugs shown as a section bar across the top (e.g. facet="free,pro"); the chosen section carries through every document link.
* show_search — Show a tag-scoped search box on the landing page: ‘true’ or ‘false’ (default: ‘true’)
* title — Optional heading above the portal (default: none)

Examples:
* [dpma_docs tag="user-guide"] — Portal for all documents tagged “user-guide”
* [dpma_docs tag="onboarding" title="Onboarding Guide"] — Portal with custom heading
* [dpma_docs tag="api-reference" show_search="false"] — Portal without search

Note: A document should carry only one portal tag. If a document has multiple portal tags, it joins the first matching portal alphabetically.

[dpma_my_acknowledgements]

Displays the signed-in visitor’s own acknowledgements: what they have acknowledged and what is still waiting for them. A logged-out visitor sees a login prompt.

Attributes:
* show_acknowledged / show_pending – Show the acknowledged and the pending lists (default: true)
* user_id – Show another user’s acknowledgements instead; only for someone allowed to edit that user (default: the signed-in user)
* heading_level – Heading level for the title shown when viewing another user (default: 2)

[dpma_pending_approvals]

Displays the document versions awaiting the signed-in visitor’s approval, with Approve and Reject buttons that also work without JavaScript. It takes no attributes.

[dpma_compliance_progress]

Displays the signed-in visitor’s own compliance status: how many of the documents they must acknowledge they have acknowledged.

Attributes:
* heading_level – Heading level for the section headings (default: 2)

[dpma_compliance_report]

Displays the acknowledgement roster for one document: who has acknowledged it, who has not, and when. Limited to compliance administrators (the dpma_compliance_report_capability filter changes who), and to documents the viewer may open.

Attributes:
* document_id – Document post ID (required)
* roles – Comma-separated role slugs to limit the report to (default: the document’s whole audience)
* limit – Maximum number of people to list (default: 200)

[dpma_user_acknowledgements]

Displays a user picker and the chosen user’s acknowledgements. Limited to administrators who can edit users.

Attributes:
* role / role__in – Limit the picker to one role, or to several (comma-separated)
* show_acknowledged / show_pending – Show the acknowledged and the pending lists (default: true)
* orderby / order – Sort the picker by a user field such as ‘display_name’ (default) and ‘ASC’ (default) or ‘DESC’
* heading_level – Heading level for the user’s name (default: 3; 2 to 6)

[dpma_bookmarks]

Displays the signed-in visitor’s bookmarked documents. A logged-out visitor sees a login prompt (the dpma_saved_items_login_prompt filter can turn that into empty output).

Attributes:
* tag – Show only bookmarks carrying this tag (comma-separate several to require all of them)

[dpma_saved_searches]

Displays the signed-in visitor’s saved searches, each with an apply and a remove button. A logged-out visitor sees a login prompt.

Attributes:
* target – The id of the search box that Apply fills in (default: dpma-search-input)

Does the plugin provide a REST API?

The plugin provides REST API endpoints under the dpma/v1 namespace:

  • GET /dpma/v1/search?q=query – Search documents (requires the q parameter)
  • GET /dpma/v1/documents – List documents
  • GET /dpma/v1/faqs – List FAQs
  • GET /dpma/v1/my-outstanding-acknowledgements – The signed-in user’s documents still awaiting their acknowledgement (signed-in users only)

These are the read routes meant for other code to call. The plugin also registers routes that only its own screens use (approval links, version history, recently viewed, the comprehension quiz, background jobs and Site Health); they are not a public API.

Document types, categories and the plugin’s other taxonomies are available through WordPress’s own REST term routes (wp/v2), which apply the same visibility rules.

By default these endpoints require a logged-in user, so document, search, and FAQ content is never exposed to anonymous visitors. If you run a public knowledge base and want anyone to read documents without signing in, enable Settings → Access & Privacy → Public REST API Access (off by default). Per-document visibility and confidentiality restrictions still apply when it is on, and anonymous requests are rate limited to deter abuse.

Does the plugin store files in my uploads folder? Do I need a web server rule?

The plugin keeps background export files such as attestation PDFs (kept for one day, then deleted), temporary import sandboxes, and the original of each imported PDF whose text could not be read in a private folder beside your web folder, named dantian-policy-management-private- plus a short code. Nothing there has a web address, on any server, and files leave it only through the plugin’s permission checks. The PDF render and font cache stays in wp-content/uploads/dantian-policy-management/; its files have unguessable names and the folder carries deny files for Apache, LiteSpeed (.htaccess) and IIS (web.config).

If no folder outside the web root can be used, the private files stay in that uploads folder too, but only while this server is measured refusing direct requests for it (checked daily). If it is not, exports and imports do not start, nothing personal is written, and Tools → Site Health gives two fixes. Name a folder outside the web root in wp-config.php:

define( 'DPMA_PRIVATE_DIR', '/a/folder/outside/the/web/root' );

Or close the uploads folder with a rule for your web server (Tools → Site Health also gives these, with the server it detects first, for the PDF cache if the folder can be opened by its web address). nginx does not read .htaccess: add this server-block rule and reload nginx. Where nginx sits in front of Apache and serves files itself (Plesk, some cPanel servers), it goes in nginx’s settings too:

location ^~ /wp-content/uploads/dantian-policy-management/ { deny all; return 403; }

The ^~ prefix makes it win over any regex location (such as a static-file caching rule).

OpenLiteSpeed reads only rewrite rules from .htaccess and loads a changed one only after a restart, so the folder’s own deny rule may not take effect there. Add these lines to the .htaccess file in your site’s root folder, above the # BEGIN WordPress line, then restart the web server (a graceful restart is enough):

RewriteEngine On
RewriteRule ^wp-content/uploads/dantian-policy-management/ - [F,L,NC]

Tools → Site Health checks the folder again each time it runs.

On Apache with .htaccess files turned off (AllowOverride None), add a <Directory> block for the folder with Require all denied to the site’s server configuration (Site Health shows it with your server’s path). On IIS, the folder’s web.config closes it once the URL Rewrite module is installed; otherwise, under Request Filtering → URL, deny the sequence /wp-content/uploads/dantian-policy-management/.

On a host with several web servers, a folder beside the web folder may exist on only one of them, so a task can fail or a download can come back “not found”; nothing is exposed, and setting DPMA_PRIVATE_DIR to shared storage fixes it. If you set DPMA_PRIVATE_DIR to a new folder, imported originals move there by themselves within a day and stay downloadable meanwhile, then the old private folder is removed; a task running at that moment may fail and can be started again. If you move a site to a new folder on the same server, its old private folder is left behind for you to delete, because it could belong to another live site.

Screenshots

Changelog

1.0.1

  • Security: SEO plugin sitemaps — the XML sitemaps of Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework and Slim SEO now follow the same visibility rules as WordPress’s own sitemaps. Before, all but Slim SEO listed the address of every restricted document and FAQ to anyone, search engines included, and Slim SEO did so for signed-in visitors. A sitemap is now always built as a signed-out visitor would see it, whoever requests it. The same applies to the HTML sitemaps of Rank Math and SEOPress and to Rank Math’s llms.txt.
  • Security: Private folders on OpenLiteSpeed and IIS — the deny file the plugin writes into its uploads folders now also blocks requests with a rewrite rule, which OpenLiteSpeed reads (it ignores the Apache access rules the file held before), and each folder also gets a web.config that denies them on IIS. Existing folders get the new files on update. Where the server still serves the folder, Tools → Site Health and the readme FAQ give the rule for every server, the one this server reports first: nginx (including nginx in front of Apache, as on Plesk and cPanel), the site-root .htaccess rule for OpenLiteSpeed, a <Directory> rule for Apache with AllowOverride None, and the IIS setting.
  • Security: Cached sitemaps — Rank Math and The SEO Framework cache their sitemaps; the plugin now clears those caches when a document’s visibility or the “hide documents from guests” setting changes, and on the first request after updating or after the SEO plugin is reactivated.
  • Fixed: SEO plugin sitemaps — the document category, type, tag, regulatory framework and FAQ category sitemaps list only terms that a visitor can open, which removes the dead (404) links search engines were being sent to.

1.0.0

Initial release.

  • Acknowledgement lifecycle — per-document acknowledgement requirement with expiry schedules, reminders and overdue follow-ups sent through a background email queue to the people who still owe them, acknowledgement campaigns, re-acknowledgement on a new version at or above the chosen change level, and optional comprehension quizzes. Staff who owe acknowledgements are pointed to them at login.
  • Acknowledgement evidence — every record stores the document version, a SHA-256 fingerprint of its text, how it was given and a keyed integrity seal; reading time and reading reach can be captured as well, and the document’s table of contents marks each section read. The Evidence & Exports screen holds the CSV/PDF attestation export, with a per-record integrity column and an export checksum.
  • Version approval workflow — version snapshots and changelog, rollback, scheduled updates and a pending-approvals queue. One rule decides who may approve: a person named as owner or approver who holds an eligible role (Administrator and Editor by default). With approval on, every change to a published document waits for approval however it is made (the editor, Quick Edit, the REST API, an importer or WP-CLI). Emailed approve and reject links work only for the owner they were sent to and open a confirmation page.
  • Owner review sign-off — document owners record a “reviewed and current” attestation; signing off a policy the owner is bound by records their own acknowledgement.
  • Access control, gated by default — Internal Use, Restricted and Confidential classifications with Target Audience roles and a Default Target Audience setting. A document or FAQ a person may not open does not reveal its title or address anywhere (search, feeds, embeds, sitemaps, archives, related lists, PDFs, exports); password-protected documents show only the password form. Optional Page Gating locks WordPress pages until chosen policies are acknowledged.
  • Knowledge Hub & search — [dpma_hub] tabbed hub, [dpma_search], [dpma_documents] filterable listing, [dpma_kb] knowledge-base layout and FAQs ([dpma_faqs] / [dpma_faq]) with helpful/unhelpful feedback, bookmarks and saved searches. Search logging is off until an administrator turns it on.
  • Docs Portal — [dpma_docs] reading format for guides and help articles: category navigation, content and an auto-generated table of contents, clean URLs and an optional facet section bar.
  • Frontend dashboards via shortcodes — [dpma_my_acknowledgements], [dpma_compliance_report], [dpma_pending_approvals], [dpma_compliance_progress].
  • Document file importer — upload a ZIP of Word (.docx), PDF, plain-text or Markdown files to create a draft document per file in a background job.
  • Branded PDF export — documents and reports carry your logo, brand colours, legal name and regulatory identifier, with an optional cover page; Confidential and Restricted exports record who downloaded them.
  • Privacy — one registry of every kind of personal data drives the WordPress exporter and eraser, uninstall and the suggested privacy-policy text; erasure anonymises acknowledgement records so the audit trail survives; every retention window is a setting; private export and import files live in a folder outside the web root (or in uploads only while the server is measured refusing direct requests), checked by Site Health. Uninstall keeps your data unless you opt in to removing it.
  • Settings and screens — Access & Privacy and Approval & Review settings tabs, a setup wizard, a Compliance Overview dashboard, Site Health checks for audience storage and the upload folder, and administrator-only control of approval, exposure and uninstall settings.
  • Works without JavaScript — acknowledging, search, approvals, FAQ paging and feedback, bookmarks and page-gating rules all have server paths; the front end is built on the WordPress Interactivity API and Script Modules.
  • Accessibility and performance — WCAG 2.2 AA throughout, an opt-in dark mode, forced-colours, print and 320px reflow support; indexed tables, batched access checks and cached dashboard figures.
  • For developers — dpma_-prefixed content types (dpma_document, dpma_faq) and taxonomies, a REST API, filters and actions, and the Dpma\Clock, Dpma\Content_Gate and Dpma\Privacy_Registry classes for extensions. Requires the PHP mbstring extension.