Bestseller
HR & People
Org Chart Pro
The modern org chart straight from Microsoft Entra ID — always current, zero maintenance.
€1,290
Documents
NewPolicy Acknowledgement ProSharePoint web part for Microsoft 365
Read policy PDFs in the web part, require acknowledgement per policy, and track exact revisions.
policy-acknowledgement.sppkg · v1.2.0
Demo
SPFx ≥ 1.23.2SharePoint Online
Overview
Policy Acknowledgement Pro lets responsible teams publish policy PDFs directly from the Compliance Dashboard. The optional managed PDF workflow is enabled in both web parts. Each policy can then be set individually as informational or as requiring an explicit read-and-acknowledged attestation.
Employees open the verified SharePoint PDF inside the web part. The exact statement unlocks only after the final rendered page and the actual end of the scroll region are reached. The record binds the policy revision, SharePoint file ID, version, ETag and SHA-256 fingerprint to SharePoint Created By and Created.
One .sppkg contains the employee experience and the Compliance Dashboard. Data and PDFs remain in the configured SharePoint lists and document library; PDF.js 4.10.38 is bundled locally with no CDN, external service or telemetry. The scroll evidence is a documented self-attestation, not proof of comprehension or legal consent. Ordinary SharePoint administrators can still change or delete list records and files. The product remains in pre-launch until clean-tenant validation passes.
This is a ready-made SPFx web part for SharePoint Online. What SPFx web parts are · Install the .sppkg · All web parts · Tenant licensing and updates
Features
- New in 1.2: works above 5,000 acknowledgements (indexed queries), counts real people only, detects Microsoft 365 groups in audiences, reads due dates as the site's calendar day and keeps the confirm button reachable on phones. Audiences are picked from the site's SharePoint groups; setup recommendations (indexes, protection against edits by others, library settings) are repaired in one click.
- Optional managed PDF workflow enabled in both web parts through settings
- Create policies with their PDFs or republish to a new revision-specific file in the dashboard
- Switch acknowledgement on or off separately for every policy
- In-app PDF reader with locally bundled PDF.js 4.10.38 and no CDN
- Attestation unlocks only after the final rendered page and actual scroll end
- Acknowledgement bound to revision, file ID, version, ETag and SHA-256
- Informational policies remain outside deadlines and compliance KPIs
- Employee search, categories, due, overdue and current-version status
- Compliance Dashboard with UTF-8 CSV export
- SharePoint REST only; no Graph/API approvals, external services or telemetry
Compatibility
| Version | 1.2.0 |
|---|---|
| Last updated | Sep 24, 2026 |
| SPFx version | ≥ 1.23.2 |
| SharePoint Online | Yes |
| Microsoft Teams | No |
| SharePoint on-premises | No |
FAQ
How is the managed PDF workflow enabled?
Enable “Managed PDF workflow” in the settings of both web parts and use the same list and library names in each. Dashboard setup adds missing fields and creates the PDF library when needed.
Can acknowledgement be required separately for every policy?
Yes. Responsible teams choose whether each policy requires acknowledgement or is published for information only. Informational policies create no deadline, outstanding status or compliance KPI.
What is stored with an acknowledgement?
The record stores policy key and version, revision ID, SharePoint file ID, file version, ETag, SHA-256, reached-document-end evidence, explicit selection and wording version. SharePoint Created By and Created provide the actor and server time.
Does scrolling prove that the policy was understood?
No. The gate documents that the final rendered page and the end of the scroll region were reached and that the statement was selected explicitly. It does not prove attention, comprehension or legal consent.
Where are PDFs and evidence stored?
PDFs stay in the configured SharePoint document library, while policies and acknowledgements stay in two SharePoint lists. PDF.js is included in the package; there is no CDN or external processing. Each PDF is limited to 25 MB and 250 pages.
Which permissions are required?
Employees need Read on policies and the library plus Add Items and appropriate own-item read access on acknowledgements. Publishers need edit rights, while setup additionally needs Manage Lists. No separate Graph or API approval is required.
€1,000
