Teams running ERPNext usually manage documents through the built-in File DocType and the attach/attach_image fields hanging off records. That is fine for a scanned invoice on a Purchase Invoice, but it breaks down the moment you need a real document library: there is no folder hierarchy your users can navigate, no version history when someone re-uploads a revised contract, no way to grant "read-only to Finance, edit to Legal" on a specific folder, and no full-text search inside the PDFs and scanned images themselves. ERPNext File permissions are coarse, sharing a document with an outside auditor means emailing the file, and once a filename is reused you have quietly lost the prior revision. This is where ERPNext native runs out of road for organizations that treat documents as controlled records.

ECOSIRE builds ERPNext DMS Pro as a proper Frappe app (its own module, DocTypes, and hooks.py) installed onto your bench, not a bolt-on outside the framework. We model documents and folders as first-class DocTypes with a parent/child tree so users get a familiar folder structure, and every upload becomes an immutable version pinned to a Document Version child table rather than overwriting the previous file. Access control is enforced with Frappe's native permission engine — role profiles, User Permissions, and document-level share — extended with folder-inheritance logic in server-side permission_query_conditions and has_permission hooks so a permission set on a parent folder cascades to everything beneath it. Nothing bypasses the framework's own security model, which keeps your audit trail and role-based reporting intact.

Full-text and OCR search is where the app earns its keep. On upload, a doc_event on the Document DocType enqueues a background job (via frappe.enqueue / scheduler events) that extracts text from native PDFs and runs OCR over scanned images and image-only PDFs, then indexes the extracted content so users can search inside document bodies — not just filenames and tags. Secure external sharing is handled through signed, expiring links backed by a whitelisted method and a token DocType, so you can send an auditor or client a time-limited, permission-checked URL without creating an ERPNext user account or attaching the raw file to an email. Everything is reachable over the Frappe REST API and whitelisted methods, so your other systems and portals can push, fetch, and search documents programmatically.

Because this is build-to-order, we scope the exact folder taxonomy, roles, retention rules, OCR languages, and integrations to your operation before writing code — we do not ship a generic download. After a short scoping call we confirm the specification, build the app against Frappe/ERPNext v15 or v16, and run it on a staging site for UAT before touching production. Typical delivery is one working week from confirmed scope, depending on how many custom DocTypes, sharing rules, and integrations you need. You receive the installable source, a git repository handover, technical and user documentation, a training session, and a post-go-live support window — so your team owns and can extend the app long after we install it.