Business System · Blazor

OperationsFlow

Operational records, corrective actions, documents, risk, training, reporting and data-quality workflows in one business-facing system.

Open repository ^Read case study ->

Role / responsibility

End-to-end business workflow design and .NET/Blazor implementation.

Operational records, corrective actions, documents, risk, training, reporting and data-quality workflows in one business-facing system.

Verified proof surfaces

Operational workflow coverage
Reporting and evidence surfaces
Business-system information architecture

Repository readme / adapted

OperationsFlow

SOURCEREADME.mdAdapted for portfolio readability; claims remain source-derived.

> **Current status:** Week 4 Microsoft 365 pilot implementation is complete. OperationsFlow now has local SQL-backed authentication, Microsoft OAuth2 sign-in, local-vs-Microsoft sign-in status, local SQL roles/permissions, SharePoint-backed evidence storage through Microsoft Graph, SharePoint metadata writeback, document upload/delete lifecycle, current-user activity logging, reporting, data quality checks, and reviewer-ready documentation.

OperationsFlow is **production pilot-ready for a single-tenant Microsoft 365 environment**. It is not being presented as a fully hardened enterprise SaaS platform; it is a working portfolio/pilot system that proves the core business workflow, identity, storage, evidence, reporting, and permission model.

Project Purpose

OperationsFlow is a practical internal business workflow system built to prove that scattered operational work can be captured, reviewed, prioritised, evidenced, and reported from one place.

It is designed around real workplace patterns:

work orders and operational requests
corrective actions and source-linked follow-up work
document intake and document processing
controlled document review
training compliance follow-up
risk register follow-up
document/evidence attachments
management reports
data quality checks
activity traceability
role-based workflow access
Microsoft 365 / SharePoint evidence storage

What This Project Demonstrates

.NET 8 / Blazor application development.
Entity Framework Core persistence.
SQLite/local development support and SQL Server/LocalDB production-foundation support.
Local SQL-backed authentication and seeded demo accounts.
Microsoft OAuth2 sign-in for tenant accounts.
Microsoft account to local OperationsFlow user mapping through `ExternalLoginLinks`.
Local SQL roles and permissions as the application authorization source.
Enforced page/action permissions for workflow actions, evidence uploads/deletes, exports, settings, and user management.
Shared UI components and consolidated styling.
Workflow modules connected through reports, reminders, workload, activity history, and data quality.
File storage abstraction with local and SharePoint providers.
SharePoint evidence upload through Microsoft Graph.

Current Project Metrics

Local SQL-backed authentication: implemented.
Microsoft OAuth2 sign-in: implemented.
Local vs Microsoft-linked status display: implemented.
Local roles/permissions: implemented.
ReadOnly permission enforcement: implemented and tested.
Admin workflow actions: implemented and tested.
SharePoint file/evidence storage: implemented.
SharePoint metadata writeback: implemented.
SharePoint delete lifecycle: implemented.
Record attachment panels: implemented.
Document Library: implemented.
Data Quality missing-evidence checks: implemented.

Walkthrough Video

A 5-minute silent walkthrough video is available here:

OperationsFlow — Microsoft 365 Pilot Walkthrough

The video demonstrates the main Week 4 review path: local and Microsoft sign-in, Microsoft-linked Admin status, Microsoft 365 connection testing, SharePoint evidence upload, metadata writeback, document lifecycle handling, activity logging, and ReadOnly permission enforcement.

Screenshot Preview

The screenshots below show the strongest Week 4 review path: sign-in, Microsoft 365 connection, role mapping, SharePoint metadata, Document Library provider, and ReadOnly permission enforcement.

6. ReadOnly permissions

More screenshots are available in `Docs/Screenshots`, ordered by review relevance.

Authentication

OperationsFlow supports local SQL login and Microsoft OAuth2 login. Microsoft sign-in proves tenant identity; OperationsFlow then maps the Microsoft identity to a local user and loads local roles/permissions.

Dashboard

Shows operational status, workflow counts, recent activity, and sign-in/authentication status.

Work Orders

Tracks operational work by site, department, owner, priority, status, due date, file count, details page, activity history, and attachments.

Corrective Actions

Tracks corrective/improvement actions from incidents, audits, inspections, risks, training gaps, document reviews, and compliance follow-ups.