Project case study
SEGCD Document Management System
Stable proof of concept for workflow-based document management
ASP.NET CorePostgreSQLEF CoreDockerJWT
Summary
Quick overview
Stable proof of concept built in roughly one month for a client demo still under discussion, covering authentication, authorization, audit logs, reporting, document flows, and admin operations.
Professional or private work. Details are summarized without exposing internal code, client data, or proprietary implementation details. Screenshots or private demo can be shared on request when available.
Workflow
Document routing and auditability
01
Submit
02
Review
03
Approve / Reject
04
Route forward
05
Audit & report
Problem
What needed to be solved
A backend-focused PoC/demo for client discussions, built around managing requests, documents, users, roles, permissions, departments, workflows, and audit history.
Implementation
What I worked on
Designed and implemented the core backend functionality around document lifecycle, workflow actions, role-based access, reporting, and administration.
Technical decisions
Responsibilities, systems, and engineering trade-offs
- JWT authentication and refresh token flow
- Role-based permissions and protected operations
- Workflow transitions for approve, reject, complete, send forward, and send back actions
- Audit logging and reporting-oriented data structures
- Dockerized ASP.NET Core and PostgreSQL setup
Result
Result and value
Reached a stable PoC stage quickly, with the main workflow, authorization, traceability, and admin-control ideas implemented clearly enough to support client-facing discussion and validation.
What I learned
Practical takeaway
Workflow systems need clear permissions, audit history, and predictable task routing before UI polish matters.