Enterprise Document Management System

1. Platform overview

Role in organizational record management and controlled disclosure

DMS operates as a centralized document management platform for any deploying organization—municipal and city LGUs, provincial offices, national agencies, NGOs, and private companies. Unlike ad-hoc file shares or department-specific drives, DMS maintains a consistent hierarchy, access policy, document metadata, file history, and release channels for operational and compliance use.

Each office maps its real structure into the system: treasury, assessor, civil registry, business permits, engineering, social services, or corporate finance and legal teams each receive scoped folders, permissions, and document types appropriate to their workflows.

Core platform functions

Document Management — upload, classify, version, and manage files with title, author, tags, and document date.
Document Finder — search, filter, download, update permissions, and manage attached files.
Folder Management — organize records within a configurable location hierarchy.
Organizational hierarchy — Branch, Department, Division, and Section model for government and private org charts.
Controlled release — public, private, and confidential access levels with API and file-serving endpoints.
OAuth2 API (Laravel Passport) and listing endpoints for downstream portals and line-of-business systems.

2. System participants

Distinct roles across government and non-government deployments

Records and document administrators

Configure branches, departments, folders, users, and organization-wide document policies.

Department staff

Encode, upload, and maintain documents for their unit—e.g. tax assessments, civil registry certificates, budget reports, permit files, contracts, or internal memos—within assigned locations.

Reviewers and releasing officers

Validate document metadata, adjust access levels, and authorize release to staff, partner systems, or public channels.

Citizens and external requesters

Receive documents published at public access level through integrated portals or approved download links.

API consumers and partner systems

HR platforms, citizen portals, legislative systems, ERP modules, and third-party reporting tools consume document listings and files via OAuth-protected or public API routes per integration contract.

3. Document lifecycle

From intake to tracked storage and authorized release

Intake → Classify → Route to unit → Track & store → Release

Document intake

A staff user or integration creates a document record and uploads one or more files with metadata.

Classification

Document type, tags, and document date are applied for search, reporting, and retention alignment.

Organizational routing

The record is assigned to the correct branch, department, division, section, and folder.

Tracking and custody

File history, permissions, and folder location provide an auditable chain of custody within the organization.

Authorized release

Documents move to the appropriate access level—internal, partner API, or public listing—for approved disclosure.

Retrieval and delivery

Staff and integrated systems retrieve files via Document Finder, API responses, or the file-serving route.

4. Organizational routing

Mapping real offices and departments into DMS structure

DMS uses a four-level location model—Branch, Department, Division, Section—plus Folders under each path. This maps cleanly to LGU line offices and to private organizational charts without custom schema per client.

Example LGU department mapping

Treasury / Finance

Collection reports, OR registers, disbursement vouchers, and revenue summaries.

Assessor / Taxes

Tax declarations, assessment rolls, and real property records.

Civil Registry

Birth, marriage, and death records; certificates and registry books.

Business Permits & Licensing

Permit applications, inspection reports, and renewal documents.

Engineering / Planning

Building plans, infrastructure files, and project documentation.

Health & Social Services

Program records, beneficiary files, and compliance documents.

Example private organization mapping

Finance & Accounting

Invoices, statements, audit workpapers, and policy documents.

Human Resources

Employee files, contracts, and training records (confidential access).

Legal & Compliance

Contracts, regulatory filings, and board resolutions.

Operations

SOPs, vendor documents, and project deliverables shared across teams.

Folder lookup by location (GET /get-folder-by-location) supports dynamic UI flows when staff select branch and department before upload or search.

5. Classification and release framework

Access levels, document types, and controlled disclosure

Access levels

Public (1)

Approved for external listing APIs and citizen-facing portals.

Private (2)

Restricted to authenticated staff within the deploying organization.

Confidential (3)

Highest restriction for sensitive personnel, legal, or fiscal records.

Document types and metadata

Document type codes, tags, and doc_date support filtering by period, category, and subject matter. Deployments configure type enums to match their domain—legislative records, tax documents, registry certificates, permit files, or corporate policies—without changing core platform code.

Release channels

Staff retrieval through Document Finder and permission-controlled downloads.
Partner systems via OAuth-protected GET /api/documents with year, month, type, and tag filters.
Approved public listings via GET /api/getdocuments for integrated portals.
Direct file delivery via GET /storage/{folder_id}/{filename} when configured for external consumption.

6. API and system integrations

Connecting DMS to portals, ERP modules, and partner applications

GET /api/documents — OAuth2 protected (Passport client credentials); filter by year, month, type, tags, doc_date.
GET /api/getdocuments — paginated public listing for approved downstream consumers.
GET /api/getdocuments/{id} — single document retrieval with related location and file metadata.
PUT /api/documents/{document}/permission — authenticated permission updates from admin workflows.
Passport setup: php artisan passport:client --client then POST /oauth/token with client_credentials.

Typical integrations include citizen service portals, legislative information systems, tax and permit front-ends, audit exports, and internal dashboards—each scoped by access level and API contract.

Optional ecosystem documentation: LIS White Paper · CMS White Paper

7. System architecture

Application and data structure

Presentation layer

Blade admin UI for document management, document finder, folder and location administration, and user profiles.

Application layer

Controllers, DocumentService, FileService, StorageResolver, and API layer for external consumption.

Data layer

Documents, files, folders, organizational entities, users, and file history linked by location and access policy.

Branch

Department

Division

Section

Folder

Document / File

File history

API consumers

Storage

Local disk with optional AWS S3 support per deployment—suitable for on-prem LGU hosting or cloud-backed enterprise storage.

8. Security and access controls

Governance, permissions, and integration integrity

Laravel UI authentication for web administration modules.
Laravel Passport for OAuth2 client credentials on protected API routes.
Per-document permission updates via authenticated web API.
Three-tier access model enforced before public API or file-serving exposure.
Department-scoped folders reduce cross-unit data exposure within large organizations.
CSRF protection on web forms; API routes follow token-based access for machine clients.

9. Risk management framework

Operational, security, and disclosure risk controls

Operational risk

Mitigated through folder hierarchy, file history, and centralized search instead of scattered departmental drives.

Access risk

Least-privilege access levels and staff authentication limit exposure of confidential personnel, fiscal, and legal records.

Disclosure risk

Public release requires explicit public access classification; API listings respect deployment policy filters.

Integration risk

OAuth credential rotation, structured API logging, and documented contracts for each consuming system.

10. Operational resilience

Continuity during disruptions

Organizational continuity depends on reliable storage, accurate metadata, and API availability for dependent portals and back-office systems. DMS supports recovery through database backups, storage replication (including optional S3), file history, and manual onsite retrieval when integrations are offline.

Incident response should follow: detect (logs/alerts), classify severity, contain (disable affected API client or release channel), restore storage and database services, reconcile released documents against access policies, and document root cause for governance review.

11. Platform role summary

Document management positioning in one view

DMS, in summary

Unified document management for LGU departments and private organizational units on one platform.
Tracks records from intake through classification, custody, and authorized release.
Maps treasury, taxes, civil registry, permits, and corporate functions into a shared hierarchy model.
Exposes OAuth and listing APIs for portals, ERP modules, and partner systems—not a single vertical only.
White-label ready for government and non-government deployments without per-client code forks.