## What Removes the policy **management** surface from the editor's right rail — the Policies list above Tools, the open-policy detail takeover, and the collapsed-rail policy icons — along with the whole UI tree only they used: the setup wizard and its tool-config steps (PII / redact / watermark), the detail panel, delete modal, selection store, enforcement-queue status chip, activity/stats derivation, the catalog hook, their i18n keys, dead types, and the admin-gate spec that tested the wizard flow. **Enforcement is untouched.** Auto-run on upload, the viewer blocking overlay, exit-point blocking, file badges, and export-time enforcement all stay. `usePoliciesEnabled` moves to its own module (core stub / proprietary / desktop shadow with the SaaS-connection check) since it still gates mounting the headless `PolicyAutoRunController` from the rail. ## Why Policies are configured in the admin portal now (`src/portal/views/Policies.tsx`). Keeping a second management UI in the editor rail meant two surfaces to maintain for one feature; the editor only needs to *enforce*. ## Notes for review - The rail UI lived in the shared `core` `RightSidebar`, so this removes it from every build flavour at once; the deleted `PoliciesSidebar` module existed at the core (stub) / proprietary / desktop alias layers and all three are gone. - Every deleted module was verified to have zero remaining importers; near-misses that stay: `enforcementQueue` (used by export enforcement), `poll` (test-imported), `usePolicies` (used by auto-run). - Net −3,900 lines. ## Testing - `task frontend:check` green: typecheck, ESLint + dpdm, Prettier, all 1,196 tests. - All build-variant typechecks pass (core / proprietary / saas / desktop).
Stirling PDF - The Open-Source PDF Platform
Stirling PDF is a powerful, open-source PDF editing platform. Run it as a personal desktop app, in the browser, or deploy it on your own servers with a private API. Edit, sign, redact, convert, and automate PDFs without sending documents to external services.
Key Capabilities
- Everywhere you work - Desktop client, browser UI, and self-hosted server with a private API.
- 50+ PDF tools - Edit, merge, split, sign, redact, convert, OCR, compress, and more.
- Automation & workflows - No-code pipelines direct in UI with APIs to process millions of PDFs.
- Enterprise‑grade - SSO, auditing, and flexible on‑prem deployments.
- Developer platform - REST APIs available for nearly all tools to integrate into your existing systems.
- Global UI - Interface available in 40+ languages.
For a full feature list, see the docs: https://docs.stirlingpdf.com
Quick Start
docker run -p 8080:8080 docker.stirlingpdf.com/stirlingtools/stirling-pdf
Then open: http://localhost:8080
For full installation options (including desktop and Kubernetes), see our Documentation Guide.
Resources
Support
- Community: Discord
- Bug Reports: GitHub Issues
Contributing
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
This project uses Task as a unified command runner for all build, dev, and test commands. Run task dev to get started running the editor, run task to see the most common commands, or see the Developer Guide for full details.
For adding translations, see the Translation Guide.
License
Stirling PDF is open-core. See LICENSE for details.

