Integrated Administrative Platform

Engineering problem

Administrative work spread across separate tools makes it difficult to follow a person's history. The platform connects eight Arabic RTL specialist apps: first-time requests, renewal follow-up, decision records, cancelled licences, officer nominations, custody records, company administration and document storage.

My responsibilities

During my military service, I developed administrative applications and integrated them through a shared General administration layer. The work brought together frontend and backend development, application-specific workflows, shared roles and permissions, and unified search.

Requirements & constraints

The shared layer applies role, app and geographic access permissions, with supported approvals and activity history. One person search gathers matching records and their source apps into a combined history within the user's access permissions. Public screenshots use fictional demonstration records only; institution identifiers, operational data and deployment details are not disclosed.

Technical approach

The backend uses Node.js and Express; the frontend uses vanilla HTML, CSS and JavaScript, not React. Data is held in CSV and JSON stores with selected SQLite stores, rather than a relational SQL backend across every app. Supporting tools include ExcelJS, PDF.js, Multer and esbuild.

Supported modules provide attachments, PDF viewing, document versions, folders, archive and recovery. Excel imports map columns and preview new or duplicate rows for review before confirmation. Optional local OCR and document cleanup depend on configured binaries and models.

Implementation & outcome

The result brings specialist register workflows into one shared environment while preserving each app's fields and processes. Users can review a person's available history without repeating the search in every app. The attached overview shows only fictional demonstration records; no usage figures or quantified performance claims are presented.