The problem
Client document exchange and deliverable status tend to spread across email threads and shared drives, which makes access hard to control and status hard to answer without asking someone.
The approach
I specified a portal architecture with role based access control as a first class concern rather than a later addition: a defined role model, per-role permissions on documents and deliverables, self-hosted object storage for files, and a relational store for the access model and audit trail. The specification covers the data model, the permission boundaries, the storage design, and the deployment shape.
Tools
What it enables
- Defines a permission model before any client data is stored.
- Documents the storage and audit design so the build can be evaluated before it starts.
My role
I wrote the architecture specification. This work has not been built or launched, and is published here as a design document.