GeezerVison

Summary

This PR adds a new document-protection sample (based on the getting-started sample) that demonstrates user-based document restrictions and approval workflows with the Syncfusion® JavaScript (ES6) DOCX Editor (Document Editor). It loads the shared Adventure Works Cycles SFDT (data-document-protection.json), which already holds the user-based editable ranges for Nancy's price values, and applies each user's document protection on the fly when a user is selected from the dropdown.

Changes

• Page and heading: The page renders the Document Editor container with the heading "User based restrict editing and approval workflow in JavaScript DOCX Editor".
• Document loading: The Adventure Works SFDT is loaded from src/resources/data/data-document-protection.json (base64 SFDT zip, unzipped client-side with ZipArchive from @syncfusion/ej2-compression — no extra packages).
• User dropdown (top of the page): Lists the five users and binds the Document Editor's currentUser to the user's email. A permission banner shows the signed-in user's role.
• Per-user restrictions:
  • Nancy ([email protected]) – ReadOnly protection with the editable ranges already embedded in the SFDT, so she can edit only the price values.
  • Andrew ([email protected]) – RevisionsOnly protection, so all his edits are tracked as revisions; the beforeAcceptRejectChanges event cancels his accept/reject actions, so he cannot approve changes.
  • Steven ([email protected]) – CommentsOnly protection, so he can insert comments only and cannot edit the content.
  • Michael ([email protected]) – no protection, full editing access; he reviews and accepts Andrew's revisions (approval workflow).
  • Laura ([email protected]) – ReadOnly protection plus isReadOnly = true; she can only read and export the document using the custom Export as DOCX / Export as PDF buttons (the PDF export uses the online service Export action).
• Permissions table (right side): Displays each user, their email and their effective permissions.
• README: Includes the introduction, how the sample works, project structure, how to run the sample, and the common Resources, Support and Feedback, License and About Syncfusion sections.

Testing

• npm run build completes successfully (TypeScript strict mode passes with tsc --noEmit).
• Verified with a headless browser:
  • Nancy: 3 editable ranges detected; typing outside the ranges is blocked; editing a price value inside her editable range succeeds.
  • Andrew: typing creates a revision (revisions.length = 1); revisions.acceptAll() is cancelled while he is signed in.
  • Michael: no protection; revisions.acceptAll() approves Andrew's revision (revisions.length becomes 0); free typing works.
  • Steven: comments can be inserted (comment count increases) while content edits are blocked.
  • Laura: document is read-only; saveAsBlob('Docx') returns a valid DOCX blob; both export buttons are present.
  • Switching users correctly stops the previous protection and enforces the new user's protection (verified protection types ReadOnly, RevisionsOnly, CommentsOnly, NoProtection).

Notes for reviewers

• The sample reuses the getting-started build setup (webpack, gulp, protractor) without adding any new packages; @syncfusion/ej2-compression was already a dependency of @syncfusion/ej2-documenteditor.
• The online demo service URL (https://document.syncfusion.com/web-services/docx-editor/api/documenteditor/) is used only for the demo, as in the base sample.

_{📍 Bold Create session · 👤 Requested by @suriyaprakasamr · 🤖 Bold Create Agent}